Request for master data change from the LF to NB (responsible) — WLF view
Process flow from the perspective of the LF (WLF)
Process steps
2 Response to request to NB from LF
NB (responsible party) LF (authorised party)
This step runs between other market partners and is not relevant for this view.
Check identifiers
Response per decision tree
44142,44157,44181,44182→ E_3013 · Check request for master data change
3 Change from NB to MSB, if applicable
NB (responsible party) MSB (authorised party)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 44113 — Non-bal.rel. change from NB · AS4
Change from NB to further LF, if applicable
LF (further LF as authorised party) NB (responsible party)Z10Z17Z18G_0019 Response to change from the NBG_0016 Response to change from the NB4411544124Check identifiers
Flow
Message from NB (responsible party) · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic
- Read market location
APERAK checks
44123,44112→Z10— APERAK check: Is location known ?44123,44112→Z1744123,44112→Z18
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Decision tree
44123→G_0019— Response to change from the NB44112→G_0016— Response to change from the NB
Trigger follow-up process
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response to change from the NB to further LF
LF (further LF as authorised party) NB (responsible party)4411244123Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Message to NB (responsible party) · AS4
Response per decision tree
44124,44115→ E_3025 · Check change from the 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
Decision trees of this process
| EBD | Name |
|---|---|
| E_3025 | Check change from the NB |
| E_3013 | Check request for master data change |
| E_3024 | Check change from the 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.
- View BER — the authorised party in this process step · market role LF
- View NBV — responsible grid operator · market role NB
- View BER — the authorised party in this process step · market role MSB
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.
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.
Applies to: 6