Request for master data change from the LF to NB (responsible) — BER view
Process flow from the perspective of the MSB (BER)
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
Change from NB to MSB, if applicable
MSB (authorised party) NB (responsible party)Z10G_0016 Not bila. rel. change from the NB44115Check identifiers
- 44113 — Non-bal.rel. change from NB · AS4
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
44113→Z10
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
44113→G_0016— Not bila. rel. change from the NB
Trigger follow-up process
- 44115 — Response to change from NB
After processing, the MACO APP starts this follow-up process itself.
Response to change from the NB to MSB
MSB (authorised party) NB (responsible party)44113Check identifiers
- 44115 — Response to change from NB · AS4
Flow
Triggered by incoming message
- 44113 — Non-bal.rel. change from NB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to NB (responsible party) · AS4
Response per decision tree
44115→ E_3024 · 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
5 Change from NB to further LF, if applicable
NB (responsible party) LF (further LF as authorised party)
6 Response to change from the NB to further LF
LF (further LF as authorised party) NB (responsible party)
Decision trees of this process
| EBD | Name |
|---|---|
| E_3024 | Check change from the NB |
| E_3013 | Check request for master data change |
| E_3025 | 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 WLF — a further supplier as authorised party · market role LF
- View NBV — responsible grid operator · market role 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.