Transmission of validation notification for the monthly curtailed energy transfer time series (AAÜZ) — ANB view
The BKV (of the LF) has checked the AAÜZ against its data and communicated its check result to the BIKO. The BIKO has forwarded it to the NB.
Process flow from the perspective of the NB (ANB)
Process steps
Forwarding of the validation notification monthly AAÜZ
NB (ANB) BIKOCheck identifiers
- 21003 — Status message · AS4
Flow
Message from BIKO · AS4
Response per decision tree
21003→ E_0098 · BKV · Check monthly AAÜZ
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0098 | Check monthly AAÜZ |
| E_0074 | Check validation notification AAÜZ |
Process information
Wording of the consolidated version, profile ch. 17.3.3.4.1, p. 260.
Preconditions
- The BKV (of the LF) has received a version of the AAÜZ.
- The BKV (of the LF) has received the data basis from the supplier.
Results
- On receipt of a negative validation notification, the NB transmits a corrected AAÜZ where applicable.
- The BIKO can form the data status and transmit it to the BKV (of the LF) and NB.
First message
BIKO sends “Forwarding of the validation notification for the monthly AAÜZ” (step 3). From here on, it is the turn of the party involved on this page.
Objective
The NB knows the expectation (need for correction or acceptance) of the BKV (of the LF) for the AAÜZ of the time period under consideration. With the exchange of the validation notification, all market participants involved learn the check result of the BKV (of the LF).
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 BIKO — BIKO
- View BKV-LF — balance responsible party of the supplier · market role BKV
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: 3
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.
Applies to: 3