Master data change initiated by NB (responsible) — View LF
Process flow from the perspective of the LF
Process steps
Change from the NB to the LF
LF NBZ10Z17Z18G_0016 Response to change from the NBG_0019 Response to change from the NB4411544124Check identifiers
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic
- Read market location
APERAK checks
44112,44123,44175→Z10— APERAK check: Is location known ?44112,44123,44175→Z1744112,44123,44175→Z18
Write endpoint
44112,44123→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Write endpoint
44175→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Decision tree
44112→G_0016— Response to change from the NB44123→G_0019— Response to change from the NB
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.
Change from the NB to MSB
LF NB4411244123Check 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 NB · AS4
Response per decision tree
44115,44124,44176→ E_3010 · Check change from the NB
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
3 Response to change from the NB to the LF
NB MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 44113 — Non-bal.rel. change from NB · AS4
Process information
Trigger
Runs beforehand: Billing data for balancing group settlement, Start of replacement supply / default supply, Case 1: LF assignment for EEG market location without DV obligation or KWKG market location without DV obligation, Case 2: LF assignment for EEG market location with DV obligation, Case 3: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped without tranches, Case 4: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped with tranches, Start of supply, End of supply from NB to LF, Creation, Transmission of the calculation formula — these processes name the one shown here in their result.
First message
NB sends “Change from NB to the LF” (step 1). From here on, it is the turn of the party involved on this page.
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.
The connector table lists no write call for these steps. Derived from the process flow: the process begins for the own role with their message, so the transaction is created.
Applies to: 1
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.
Applies to: 2