Business data request from the LF to the NB — LF view
Process flow from the perspective of the LF
Process steps
Business data request
LF NBSTART_ANFRAGE_MESSWERTESTART_ANFRAGE_STAMMDATEN_MALOSTART_GESCHAEFTSDATENANFRAGECheck identifiers
Flow
Process trigger
The backend triggers this step with one of these events.
Message to NB · AS4
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Response
LF NBZ33MSCONSZ10Z18Z27Check identifiers
Flow
Message from NB · AS4
Response per decision tree
19101,19102→ E_3003 · Check business data request for master data
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read meter
GET /getCounterBasic
- Read market location
APERAK checks
19101,19102,13009→Z33— APERAK check: Is referenced message known ?13008,13002→MSCONS13009→Z10— APERAK check: Is location known ?13009→Z1813009→Z27
Write endpoint
13008,13009,13002→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Write endpoint
44035,19101,19102→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Decision trees of this process
| EBD | Name |
|---|---|
| E_3003 | Check business data request for master data |
Process information
Other views of the process
The same process through the eyes of the other parties involved: the same steps, each read from their point of view.
- View NB — NB
Notes on this page
The source provides no use case profile for this process — objective, precondition and result are not recorded there.
The steps are the possible messages of this process, not a sequence — the source lists neither conditions nor alternatives. The small box on the step names the own view on the left: with ← it receives, with → it sends. Collapsed steps run between other market partners.
Step sequence reconstructed
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.
The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists.
Applies to: 2