Request for master data change from the LF to MSB (responsible) — BER view
Process flow from the perspective of the MSB (BER)
Process steps
Request to MSB (forwarding)
MSB (authorised party) NB (distributor)Z10Z17Z18G_0043 Response to requestG_0044 Response to request4414944167Check identifiers
Flow
Message from NB (distributor) · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
44165,44147→Z1044165,44147→Z1744165,44147→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
44165→G_0043— Response to request44147→G_0044— Response to request
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 to request to MSB
MSB (authorised party) NB (distributor)4414744165Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Load data for processing
- Read metering location
GET /getMeterLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic - Read meter
GET /getCounterBasic
- Read metering location
Message to NB (distributor) · AS4
Response per decision tree
44167,44149→ E_3016 · Check request to 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
4 Response to request to MSB
NB (distributor) LF (authorised party)
This step runs between other market partners and is not relevant for this view.
Check identifiers
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 NB — NB
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.