Transmission of validation notification for the balancing group aggregated time series from BKV to BIKO and ÜNB — BIKO view
The BKV checks an available version of the BK-SZR (category B) and transmits the corresponding validation notification to the BIKO. By means of a negative validation notification, the BKV can indicate to the ÜNB, 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 of the BKV for a version of the BK-SZR (category B) that is received from 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 of the BKV for a version of the BK-SZR (category B) that is received from the BIKO after the clearing deadline of the BKA (without KBKA) has expired is passed on to the ÜNB but does not change 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 BK-SZR (category B)
BIKO BKVCheck identifiers
- 21005 — Status message · AS4
Flow
Message from BKV · AS4
Response per decision tree
21005→ E_0064 · BKV · Check BK_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 BK-SZR (category B)
BIKO BKVCheck identifiers
- 21004 — Status message · AS4
Flow
Message to BKV · AS4
Response per decision tree
21004→ E_0025 · 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 BK-SZR (category B)
BIKO ÜNBCheck identifiers
- 21003 — Status message · AS4
Flow
Message to ÜNB · AS4
Response per decision tree
21003→ E_0064 · BKV · Check BK_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_0025 | Check validation notification |
| E_0064 | Check BK_SZR (category B) |
Process information
Wording of the consolidated version, profile ch. 11.10.1, pp. 158–159.
Preconditions
The ÜNB has formed the BK-SZR (category B) and successfully transmitted it to the BIKO. The BIKO has forwarded the BK-SZR (category B) along the chain to the BKV.
Results
- On receipt of a negative validation notification, the ÜNB transmits a corrected BK-SZR (category B) where applicable.
- The BIKO can form the data status and transmit it to the BKV and ÜNB.
First message
BKV sends “Validation notification BK-SZR (category B)” (step 1). From here on, it is the turn of the party involved on this page.
Objective
- The BKV has checked the BK-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 BKV for the BK-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.