Transmission of the supplier aggregated time series from ÜNB to LF — ÜNB view
The ÜNB delivers the currently valid aggregation level to the LF, for the balancing month, for each activated MaBiS-ZP the LF-SZR (category B). The LF checks the LF-SZR (category B) and can, if 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 B)
ÜNB LFCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message to LF · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Transmission of validation notification
ÜNB LFCheck identifiers
- 21000 — Status message · AS4
Flow
Message from LF · AS4
Response per decision tree
21000→ E_0041 · LF · Check supplier aggregated time series (category B)
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Decision trees of this process
| EBD | Name |
|---|---|
| E_0041 | Check supplier aggregated time series (category B) |
Process information
Wording of the consolidated version, profile ch. 8.4.1, p. 94.
Preconditions
The ÜNB has activated the MaBiS-ZP for the LF-SZR (category B) at 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 B)“ to LF (step 1).
Objective
The LF has the LF-SZR (category B) from the ÜNB. In addition, the ÜNB may have a check result from the LF on the LF-SZR (category B) 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 this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button.