Request for master data change from the MSB to NB (responsible) — NB view
Process flow from the perspective of the NB
Process steps
Request to NB from MSB
NB MSBZ10Z16Z17Z18G_0069 Response to request44117Check identifiers
- 44140 — Not bal.-rel. request to NB · AS4
Flow
Message from MSB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic
- Read market location
APERAK checks
44140→Z1044140→Z1644140→Z1744140→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
44140→G_0069— Response to request
Trigger follow-up process
- 44117 — Change from MSB with dependencies
After processing, the MACO APP starts this follow-up process itself.
Response to request to NB from MSB
NB MSB44139Check identifiers
- 44142 — Response to request · AS4
Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read market location
Message to MSB · AS4
Response per decision tree
44142→ E_3026 · Check request for master data change
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
Change from NB to LF, if applicable
NB LF44140Check identifiers
Flow
Triggered by incoming message
- 44140 — Not bal.-rel. request to NB
The MACO APP sends this message itself, as a follow-up process after this incoming message. 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 NB to LF
NB LFZ33Flow
Message from LF · AS4
Response per decision tree
44119,44161→ E_3027 · Check change from the NB
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_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.
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.