Transmission of validation notification for the balancing group aggregated time series from BKV to BIKO and NB — BKV view
The BKV checks an available version of the BK-SZR (category A) 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 A) 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 A) 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 BKV
Process steps
Validation notification BK-SZR (category A)
BKV BIKOCheck identifiers
- 21005 — Status message · AS4
Flow
Message to BIKO · AS4
Response per decision tree
21005→ E_0063 · BKV · Check BK-SZR (category A)
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Refusal of the validation notification BK-SZR (category A)
BKV BIKOCheck identifiers
- 21004 — Status message · AS4
Flow
Message from BIKO · AS4
Response per decision tree
21004→ E_0021 · BIKO · Check validation notification
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_0021 | Check validation notification |
| E_0063 | Check BK-SZR (category A) |
Process information
Wording of the consolidated version, profile ch. 10.10.1, pp. 135–136.
Preconditions
- The NB has created the BK-SZR (category A) and successfully transmitted it to the BIKO. The BIKO has forwarded the BK-SZR (category A) to the BKV in the chain.
Results
- On receipt of a negative validation notification, the NB transmits a corrected BK-SZR (category A) where applicable.
- The BIKO can form the data status and transmit it to the BKV and NB.
First message
The party involved on this page is itself the sender of: „Validation notification BK-SZR (category A)“ to BIKO (step 1).
Objective
- The BKV has checked the BK-SZR (category A) 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 regarding the BK-SZR (category A) 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 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.