Request for master data change from the NB to LF (responsible) — LF view
Process flow from the perspective of the LF
Process steps
Request to LF from the NB
LF NBZ10Z17Z18G_0039 Rejection of the requestG_0038 Response to requestG_0040 Response to request44138Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
44150,44137→Z10— APERAK check: Is location known ?44150,44137→Z1744150,44137→Z18
Write endpoint
44137→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Write endpoint
44150→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Decision tree
44150→G_0039— Rejection of the request44150→G_0038— Response to request44137→G_0040— Response to request
Trigger follow-up process
- 44138 — Response to request
After processing, the MACO APP starts this follow-up process itself.
Response to request to LF from NB
LF NB44137Check identifiers
Flow
Triggered by incoming message
- 44137 — Not bal.-rel. request to LF
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to NB · AS4
Response per decision tree
44151,44152,44138→ E_3028 · Check request to LF from NB
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
3 Change from LF, if applicable (forwarding from NB to MSB)
NB MSB
This step runs between other market partners and is not relevant for this view.
Transmission AS4
4 Response to change from the LF
MSB NB
This step runs between other market partners and is not relevant for this view.
Transmission AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_3028 | Check request to LF from NB |
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.
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 process begins for the own role with their message, so the transaction is created.
Applies to: 1
For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body.