End of supply from LF to NB — NB view
Process flow from the perspective of the NB
Process steps
Deregistration
NB LFZ10Z16Z17Z18G_0007_G_0008 End of supply NN from the LF (Gas)4400544006Check identifiers
- 44004 — NN deregistration · AS4
Flow
Message from LF · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
44004→Z1044004→Z1644004→Z1744004→Z18
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
Load data for the check
- Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read market location
Decision tree
44004→G_0007_G_0008— End of supply NN from the LF (Gas)
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.
Response to deregistration
NB LF44004Check identifiers
Flow
Triggered by incoming message
- 44004 — NN deregistration
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read balancing
GET /getAccountingBasic - Read market location
GET /getMarketLocationBasic
- Read balancing
Message to LF · AS4
Response per decision tree
44005,44006→ E_3019 · Check deregistration
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_3019 | Check deregistration |
Process information
Trigger
Runs beforehand: Contract termination — these processes name the one shown here in their result.
First message
LF sends “Deregistration” (Step 1). From here on, the party involved on this page takes its turn.
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.
- View LF — LF
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.