Master data change initiated by MSB (responsible) — View LF
Process flow from the perspective of the LF
Process steps
Change from the MSB (forwarding to LF)
LF NBZ10Z17Z18G_0027 Response to change from the MSBG_0030 Response to change from the MSB4411944161Check identifiers
Flow
Message from NB · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
44117,44160→Z10— APERAK check: Is location known ?44117,44160→Z1744117,44160→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
44117→G_0027— Response to change from the MSB44160→G_0030— Response to change from the MSB
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 change from the MSB
LF NB4411744160Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Message to NB · AS4
Response per decision tree
44119,44161→ E_3023 · Check change from the 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
Decision trees of this process
| EBD | Name |
|---|---|
| E_3023 | Check change from the MSB |
| E_3012 | Check change from the MSB |
Process information
Trigger
Runs beforehand: Termination of a configuration from MSB, Order placement for the termination of a configuration from LF to MSB, Order placement for the termination of a configuration from NB to MSB, Order placement for the termination of a configuration from the further MSB to MSB, Order placement for a configuration from LF to MSB, Order placement for a configuration from NB to MSB, Setup of the configurations on the basis of an assignment of a LF to a market location or tranche — these processes name the one shown here in their result.
First message
NB sends “Change from MSB (forwarding to LF)” (step 2). From here on, the party involved on this page has the next move.
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.