Master data change initiated by LF (responsible) — View LF
Process flow from the perspective of the LF
Process steps
Change from the LF
LF NBFlow
Prozessauslöser
START_VERSAND_SDAEThe backend triggers this step with this event.
Message to NB · 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
2 Change from LF (forwarding to MSB)
NB MSB
This step runs between other market partners and is not relevant for this view.
Transmission AS4
Response to change from the LF
LF NBZ33Flow
Message from NB · AS4
Response per decision tree
44111,44121→ E_3011 · Check change from the LF
APERAK checks
44111,44121→Z33— APERAK check: Is referenced message known ?
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
4 Response to change from the LF
MSB NB
This step runs between other market partners and is not relevant for this view.
Transmission AS4
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
The party involved on this page is itself the sender of: „Change from the LF“ to NB (step 1).
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.