Business data request from the MSB to the NB — NB view
Process flow from the perspective of the NB
Process steps
Business data request
NB MSB (electricity / gas)Z10E_3004 Check business data request for master data1910144060Check identifiers
- 17126 — Request master data metering location (gas) · AS4
Flow
Message from MSB (electricity / gas) · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
17126→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
17126→ E_3004 — Check business data request for master data
Trigger follow-up process
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response
NB MSB (electricity / gas)17126Check identifiers
Flow
Triggered by incoming message
- 17126 — Request master data metering location (gas)
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read metering location
GET /getMeterLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic - Read meter
GET /getCounterBasic
- Read metering location
Message to MSB (electricity / gas) · AS4
Response per decision tree
19101→ E_3004 · NB · Check business data request for master data
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_3004 | Check business data request for master data |
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.
- View MSB — MSB
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.