Exchange of the delta time series carry-over list from ÜNB to NB — NB view
The NB receives the DZÜ list from the ÜNB.
Process flow from the perspective of the NB
Process steps
Transmission of the DZÜ list
NB ÜNBZ10Z16Z17Z18Check identifiers
- 55223 — DZÜ list · AS4
Flow
Message from ÜNB · AS4
APERAK checks
55223→Z1055223→Z1655223→Z1755223→Z18
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
Process information
Wording of the consolidated version, profile ch. 12.4.1, p. 170.
Preconditions
- The ÜNB has determined a DZÜ.
- The NB knows the MaBiS-ZP of the DZÜ.
Results
- The NB can check the plausibility of the DZÜ list on the basis of its data.
First message
ÜNB sends “Transmission of the DZÜ list” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The NB has the DZÜ list from the Ü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.
- View ÜNB — ÜNB · market role UENB
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: 1
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: 1