Cancellation of the interruption and restoration of grid connection use at the instruction of LF — View MSB
Process flow from the perspective of the MSB
Process steps
1 Cancellation
LF NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 39000 — Cancellation of disconnection/reconnection order · AS4
2 Response to cancellation
NB LF
This step runs between other market partners and is not relevant for this view.
Check identifiers
Response per decision tree
19128,19129→ E_1006 · NB · Check cancellation (Based on electricity EBD: E_0468_Check cancellation)
Forwarding of the cancellation
MSB NBORDCHG39001Check identifiers
- 39001 — Forwarding of the cancellation · AS4
Flow
Message from NB · AS4
APERAK checks
39001→ORDCHG39001— Request category?
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
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 the other parties involved
| 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.