Cancellation of the interruption and restoration of grid connection use at the instruction of LF — View LF
Process flow from the perspective of the LF
Process steps
Cancellation
LF NBSTART_STORNO_AUFTRAGSTART_STORNO_SE_AUFTRAGCheck identifiers
- 39000 — Cancellation of disconnection/reconnection order · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
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
Response to cancellation
LF NBZ33Check identifiers
Flow
Message from NB · AS4
Response per decision tree
19128,19129→ E_1006 · NB · Check cancellation (Based on electricity EBD: E_0468_Check cancellation)
APERAK checks
19128,19129→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
3 Forwarding of the cancellation
NB MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 39001 — Forwarding of the cancellation · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_1006 | Check cancellation (Based on electricity EBD: E_0468_Check cancellation) |
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.
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.