Transmission of validation notification for the balancing area aggregate time series to ÜNB — BIKO view
The NB checks an available version of the BG-SZR (category B) and transmits the corresponding validation notification to the BIKO. In doing so, the NB can indicate to the ÜNB by means of a negative validation notification, even beyond the end of the clearing deadline of the BKA (without KBKA), that it considers the data used for the BKA (without KBKA) to be in need of correction and therefore expects the transmission of corrected data for the KBKA. A positive validation notification from the NB for a version of the BG-SZR (category B) that is received by the BIKO after the clearing deadline of the BKA (without KBKA) has expired is passed on to the ÜNB and the data status is set to “billing data KBKA”. A negative validation notification from the NB for a version of the BG-SZR (category B) that is received by the BIKO after the clearing deadline of the BKA (without KBKA) has expired is passed on to the ÜNB but does not cause any change to the existing data status. The BIKO forwards the validation notification to the ÜNB, provided it is not rejected because the clearing deadline of the KBKA has been exceeded.
Process flow from the perspective of the BIKO
Process steps
Validation notification BG-SZR (category B)
BIKO NBCheck identifiers
- 21005 — Status message · AS4
Flow
Message from NB · AS4
Response per decision tree
21005→ E_0062 · NB · Check BG-SZR (category B)
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Refusal of the validation notification BG-SZR (category B)
BIKO NBCheck identifiers
- 21004 — Status message · AS4
Flow
Message to NB · AS4
Response per decision tree
21004→ E_0019 · BIKO · Check validation notification
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Forwarding of validation notification BG-SZR (category B)
BIKO ÜNBCheck identifiers
- 21003 — Status message · AS4
Flow
Message to ÜNB · AS4
Response per decision tree
21003→ E_0062 · NB · Check BG-SZR (category B)
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Decision trees of this process
| EBD | Name |
|---|---|
| E_0019 | Check validation notification |
| E_0062 | Check BG-SZR (category B) |
Process information
Wording of the consolidated version, profile ch. 9.8.1, pp. 114–115.
Preconditions
- The ÜNB has formed the BG-SZR (category B) and transmitted it successfully to the BIKO.
- The BIKO has forwarded the BG-SZR (category B) along the chain to the NB.
Results
- On receipt of a negative validation notification, the ÜNB transmits a corrected BG-SZR (category B) where applicable.
- The BIKO can form the data status and transmit it to the NB and ÜNB.
First message
NB sends “Validation notification BG-SZR (category B)” (step 1). From here on, the party involved on this page has the next move.
Objective
- The NB has checked the BG-SZR (category B) against its data and has transmitted its check result to the BIKO.
- The BIKO has forwarded this to the ÜNB.
- The ÜNB knows the expectation (need for correction or acceptance) of the NB for the BG-SZR (category B) of the time period under consideration.
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.
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 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
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.