Request for and transmission of the clearing list for the transmission system operator (TSO) delta time series between BIKO and ÜNB — ÜNB view
The ÜNB can request and receive the clearing list for a ÜNB-DZR only for its RZ.
Process flow from the perspective of the ÜNB
Process steps
Request clearing list ÜNB-DZR
ÜNB BIKOCheck identifiers
- 17208 — Request for clearing list ÜNB-DZR · AS4
Flow
Message to BIKO · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Transmission of clearing list ÜNB-DZR
ÜNB BIKOCheck identifiers
- 55069 — Clearing list DZR · AS4
Flow
Message from BIKO · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Process information
Wording of the consolidated version, profile ch. 13.13.1, p. 205.
Preconditions
- The BIKO has activated a MaBiS-ZP for the ÜNB-DZR.
- The BIKO has sent a version of a Ü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 a ÜNB-DZR and can thus trace the ÜNB-DZR or initiate 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 numbers are those of the source; where one is missing, it is missing there.
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: 3
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.