Master data change initiated by MSB (responsible) — View NB
Process flow from the perspective of the NB
Process steps
Change from the MSB
NB MSBZ10G_0026 Response to change from the MSB44117441194416044161Check identifiers
Flow
Message from MSB · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
44116,44159→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
44116,44159→G_0026— Response to change from the MSB
Trigger follow-up process
- 44117 — Change from MSB with dependencies
- 44119 — Response to change from MSB
- 44160 — Change from MSB without dependencies
- 44161 — Response to change
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Change from the MSB (forwarding to LF)
NB LF4411644159Check identifiers
Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages. In addition, the backend can trigger this step with an event — the next item.
Prozessauslöser
START_ANFRAGE_STAMMDATENAENDERUNG_GASThe backend triggers this step with this event.
Message to LF · AS4
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
Response to change from the MSB
NB MSB4411644159Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Message to MSB · AS4
Response per decision tree
44119,44161→ E_3012 · Check change from the MSB
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
Response to change from the MSB
NB LFZ33Flow
Message from LF · AS4
Response per decision tree
44119,44161→ E_3023 · Check change from the MSB
APERAK checks
44119,44161→Z33
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
Decision trees of this process
| EBD | Name |
|---|---|
| E_3012 | Check change from the MSB |
| E_3023 | Check change from the MSB |
Process information
Trigger
Runs beforehand: Termination of a configuration from MSB, Order placement for the termination of a configuration from LF to MSB, Order placement for the termination of a configuration from NB to MSB, Order placement for the termination of a configuration from the further MSB to MSB, Order placement for a configuration from LF to MSB, Order placement for a configuration from NB to MSB, Setup of the configurations on the basis of an assignment of a LF to a market location or tranche — these processes name the one shown here in their result.
First message
MSB sends “Change from MSB” (step 1). 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.