Master data change initiated by NB (responsible) — View NB
Process flow from the perspective of the NB
Process steps
Change from the NB to the LF
NB LFCheck identifiers
Flow
Prozessauslöser
START_VERSAND_SDAEThe backend triggers this step with this event.
Message to LF · AS4
Write endpoint
44112,44175·marktlokationsId != null→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
Write endpoint
44112,44175·messlokationsId != null→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
Write endpoint
44123→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
Change from the NB to MSB
NB LFZ33Check identifiers
Flow
Message from LF · AS4
Response per decision tree
44115,44124,44176→ E_3010 · Check change from the NB
APERAK checks
44115,44124,44176→Z33
Write endpoint
44115,44176·marktlokationsId != null→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Write endpoint
44115,44176·messlokationsId != null→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Write endpoint
44124→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Response to change from the NB to the LF
NB MSBSTART_ANFRAGE_STAMMDATENAENDERUNG_GASSTART_VERSAND_SDAECheck identifiers
- 44113 — Non-bal.rel. change from NB · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
Message to MSB · AS4
Write endpoint
marktlokationsId != null→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
Write endpoint
messlokationsId != null→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
Response to change from the NB to MSB
NB MSBZ33Check identifiers
- 44115 — Response to change from NB · AS4
Flow
Message from MSB · AS4
Response per decision tree
44115→ E_3021 · Check change from the NB
APERAK checks
44115→Z33
Write endpoint
marktlokationsId != null→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Write endpoint
messlokationsId != null→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
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
The party involved on this page is itself the sender of: „Change from the NB to the LF“ to LF (step 1).
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.