Master data change initiated by LF (responsible) — View NB
Process flow from the perspective of the NB
Process steps
Change from the LF
NB LFZ10G_0023 Response to change from the LFG_0025 Response to change from the LF4411144121Flow
Message from LF · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
44109,44120→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
44109→G_0023— Response to change from the LF44120→G_0025— Response to change from the LF
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 LF (forwarding to MSB)
NB MSBTransmission AS4
Flow
Message to MSB · 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 LF
NB LF4410944120Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Message to LF · AS4
Response per decision tree
44111,44121→ E_3011 · Check change from the LF
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 LF
NB MSBTransmission AS4
Flow
Message from MSB · AS4
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_3011 | Check change from the LF |
Process information
Trigger
Runs beforehand: 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, Creation — these processes name the one shown here in their result.
First message
LF sends “Change from 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 own role was already involved in this process, so the transaction already exists.
Applies to: 4
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.