Transmission of validation notification for the delta time series carry-over from NB via BIKO to ÜNB — NB view
The DZÜ forwarded by the BIKO is available at the NB. The NB plausibility-checks the DZÜ against the DZÜ list and transmits a validation notification to the BIKO. The BIKO forwards it to the ÜNB, provided it is not rejected. If the NB sends a negative validation notification for a DZÜ, it is obliged to send the ÜNB a DZÜ correction list. This response message is made electronically in standardised form. Further steps towards clarification are taken via other communication channels.
Process flow from the perspective of the NB
Process steps
Validation notification DZÜ
NB BIKOCheck identifiers
- 21005 — Status message · AS4
Flow
Message to BIKO · AS4
Response per decision tree
21005→ E_0065 · NB · Check DZÜ
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
Correction of DZÜ list
NB ÜNBCheck identifiers
- 55224 — Response to DZÜ list · AS4
Flow
Message to ÜNB · AS4
Response per decision tree
55224→ E_0070 · NB · Check DZÜ list
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
Refusal of the validation notification DZÜ
NB BIKOCheck identifiers
- 21004 — Status message · AS4
Flow
Message from BIKO · AS4
Response per decision tree
21004→ E_0030 · BIKO · Check validation notification
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0030 | Check validation notification |
| E_0065 | Check DZÜ |
| E_0070 | Check DZÜ list |
Process information
Wording of the consolidated version, profile ch. 12.6.1, pp. 174–175.
Preconditions
- The ÜNB has formed the DZÜ and transmitted it successfully to the BIKO. The BIKO has forwarded the DZÜ along the chain to the NB.
Results
- If the validation notification is positive, the BIKO can form the data status and transmit it to the NB and ÜNB.
First message
The party involved on this page is itself the sender of: „Validation notification DZÜ“ to BIKO (step 1).
Objective
- The NB has checked the DZÜ 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 NB for the DZÜ of the time period under consideration.
- If NB has sent a negative validation notification for DZÜ, the response message for the DZÜ list is available to ÜNB.
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.
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 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.