Request for master data change from the MSB to NB (responsible) — MSB view
Process flow from the perspective of the MSB
Process steps
Request to NB from MSB
MSB NBCheck identifiers
- 44140 — Not bal.-rel. request to NB · AS4
Flow
Prozessauslöser
START_BESTELLUNG_SDAE_GASThe backend triggers this step with this event.
Message to NB · 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 request to NB from MSB
MSB NBZ33Check identifiers
- 44142 — Response to request · AS4
Flow
Message from NB · AS4
Response per decision tree
44142→ E_3026 · Check request for master data change
APERAK checks
44142→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_3026 | Check request for master data change |
| E_3027 | 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.
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.