Excess/shortfall quantity settlement between NB and LF — LF view
Process flow from the perspective of the LF
Process steps
Balanced quantity
LF NBZ10Z27Z18Z33Check identifiers
- 13014 — Market-location-specific balanced quantity electricity/gas (MMMA) · AS4
Flow
Message from NB · AS4
APERAK checks
13014→Z10— APERAK check: Is location known ?13014→Z2713014→Z1813014→Z33— APERAK check: Is referenced message known ?
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
MMM invoice
LF NBZ24Z25Z26Flow
Message from NB · AS4
APERAK checks
31005,31006→Z2431005,31006→Z2531005,31006→Z26
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
Response
LF NBFlow
Prozessauslöser
START_VERSAND_ANTWORT_NNAThe backend triggers this step with this event.
Message to NB · AS4
Response per decision tree
33002→ E_0801 · Check excess/shortfall quantity invoice
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
Remittance advice
LF NBCheck identifiers
- 33001 — Confirmation · AS4
Flow
Prozessauslöser
START_VERSAND_ANTWORT_NNAThe 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
Cancellation
LF NBZ33Check identifiers
- 31004 — Cancellation invoice · AS4
Flow
Message from NB · AS4
APERAK checks
31004→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
Response
LF NBFlow
Prozessauslöser
START_VERSAND_ANTWORT_NNAThe backend triggers this step with this event.
Message to NB · AS4
Response per decision tree
33002→ E_0804 · LF · Check whether a response to the cancellation is required (Based on electricity EBD: E_0506_Check whether a response to the cancellation is required)
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_0801 | Check excess/shortfall quantity invoice |
| E_0804 | Check whether a response to the cancellation is required (Based on electricity EBD: E_0506_Check whether a response to the cancellation is required) |
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.
- View NB — NB
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. The numbers are those of the source; where one is missing, it is missing there.
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 process begins for the own role with their message, so the transaction is created.
Applies to: 1
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: 2
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.