Request for and transmission of the clearing list for the grid operator delta time series between BIKO and NB — NB view
The NB can request and receive the clearing list for an NB-DZR only for its own BG.
Process flow from the perspective of the NB
Process steps
Request clearing list NB-DZR
NB BIKOCheck identifiers
- 17205 — Req. clearing list DZR · AS4
Flow
Message to BIKO · AS4
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Error message request not correct
NB BIKOFlow
Message from BIKO
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
Transmission of clearing list NB-DZR
NB BIKOZ33Check identifiers
- 55069 — Clearing list DZR · AS4
Flow
Message from BIKO · AS4
APERAK checks
55069→Z33
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
Process information
Wording of the consolidated version, profile ch. 13.12.1, p. 203.
Preconditions
- The BIKO has activated a MaBiS-ZP for the NB-DZR.
- The BIKO has sent a version of an NB-DZR.
- The NB needs to view the clearing list in order to check the NB-DZR.
Further requirements
The clearing list is created and sent on request only (no subscription). For the BKA, the exchanged and billing-relevant NB DZR is authoritative, not the detailed data contained in the clearing list. Changes of data status are not carried forward within a clearing list.
First message
The party involved on this page sends this itself: “Request clearing list NB-DZR” to BIKO (step 1).
Objective
The NB has received the clearing list for an NB-DZR and can thus trace the NB-DZR or trigger a clearing.
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
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.
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.