Request for master data change from the LF to MSB (responsible) — NB view
Process flow from the perspective of the NB
Process steps
Request to MSB
NB (distributor) LF (authorised party)Z104414744165Check identifiers
Flow
Message from LF (authorised party) · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
44162,44143→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
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.
Request to MSB (forwarding)
NB (distributor) MSB (authorised party)4414344162Check identifiers
Flow
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 (authorised party) · 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 MSB
NB (distributor) MSB (authorised party)Z33Flow
Message from MSB (authorised party) · AS4
Response per decision tree
44167,44149→ E_3016 · Check request to MSB
APERAK checks
44167,44149→Z33
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
Response to request to MSB
NB (distributor) LF (authorised party)Check identifiers
Flow
Message to LF (authorised party) · 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
Change from MSB, if applicable
NB (distributor) LF (further LF as authorised party)441164414044159Check 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 (further LF as authorised party) · 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 (distributor) LF (further LF as authorised party)Z33Flow
Message from LF (further LF as authorised party) · AS4
Response per decision tree
44161,44119→ E_3032 · Check change from the MSB
APERAK checks
44161,44119→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_3016 | Check request to MSB |
| E_3017 | Check response to request to MSB (forwarding) |
| E_3031 | Check forwarding of the request to MSB |
| E_3032 | Check change from the MSB |
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 BER — the authorised party in this process step · market role LF
- View WLF — a further supplier as authorised party · market role LF
- View BER — the authorised party in this process step · market role 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.