Master data change initiated by NB (responsible) — View MSB
Process flow from the perspective of the MSB
Process steps
2 Change from the NB to MSB
LF NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
Response per decision tree
44115,44124,44176→ E_3010 · Check change from the NB
Response to change from the NB to the LF
MSB NBZ10Z17Z18G_0016 Not bila. rel. change from the NB44115Check identifiers
- 44113 — Non-bal.rel. change from NB · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic
- Read market location
APERAK checks
44113→Z1044113→Z1744113→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
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 NB44113Check 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 · AS4
Response per decision tree
44115→ E_3021 · 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
Process information
Trigger
Runs beforehand: Billing data for balancing group settlement, Start of replacement supply / default supply, Case 1: LF assignment for EEG market location without DV obligation or KWKG market location without DV obligation, Case 2: LF assignment for EEG market location with DV obligation, Case 3: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped without tranches, Case 4: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped with tranches, Start of supply, End of supply from NB to LF, Creation, Transmission of the calculation formula — these processes name the one shown here in their result.
First message
NB sends “Response to change from NB to the LF” (step 3). From here on, it is the turn of the party involved on this page.
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.
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.