Transmission of the supplier aggregated time series from NB to LF — NB view
For the balancing month, the NB delivers the LF-SZR (category A) to the LF for every activated MaBiS-ZP. The LF checks the LF-SZR (category A) and can, where required, communicate the check result to the NB by means of the validation notification.
Process flow from the perspective of the NB
Process steps
Transmission of LF-SZR (category A)
NB LFCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message to LF · 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
Transmission of validation notification
NB LFCheck identifiers
- 21000 — Status message · AS4
Flow
Message from LF · AS4
Response per decision tree
21000→ E_0007 · LF · Check LF-SZR (category A)
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 this process
| EBD | Name |
|---|---|
| E_0007 | Check LF-SZR (category A) |
Process information
Wording of the consolidated version, profile ch. 7.4.1, p. 83.
Preconditions
The NB has activated the MaBiS-ZP for the LF-SZR (category A) with the LF for the time period under consideration.
First message
The party involved on this page is itself the sender of: „Transmission of LF-SZR (category A)“ to LF (step 1).
Objective
The LF has the LF-SZR (category A) from the NB. In addition, the NB may have a check result from the LF on the LF-SZR (category A) by means of a validation notification.
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 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 source does not yet name the event that triggers these steps.
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.