Transmission of the supplier aggregated time series from NB to LF — LF 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 LF
Process steps
Transmission of LF-SZR (category A)
LF NBMSCONSCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message from NB · AS4
APERAK checks
13003→MSCONS
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
Transmission of validation notification
LF NBCheck identifiers
- 21000 — Status message · AS4
Flow
Message to NB · 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 once the message has been created.
- 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
NB sends “Transmission LF-SZR (category A)” (step 1). From here on, the party involved on this page has the next move.
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 NB — NB
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.
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.