Exchange of the supplier clearing list between ÜNB and LF (incl. subscription) — LF view
The LF requests or, where required, subscribes to the LF-CL from the ÜNB. The ÜNB sends the requested LF-CL to the LF. The LF has the option of plausibility-checking the LF-SZR (category B) against the data of the LF-CL. The LF can give a response message to the LF-CL received from the ÜNB. This response message is made electronically in standardised form by means of a correction list for the LF-CL. Further steps for clarification take place via other communication channels. A LF can request the LF-CL immediately after receiving the LF-SZR (category B). Alternatively, the LF can apply for the list to be sent regularly (subscription). An LF-CL can be requested for every version of an LF-SZR (category B) that has been sent. An LF-CL is created for every ZRT and can also be requested separately.
Process flow from the perspective of the LF
Process steps
Request for the LF-CL
LF ÜNBCheck identifiers
- 17202 — Req. supplier clearing list · AS4
Flow
Message to ÜNB · 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
Transmission of the LF-CL
LF ÜNBCheck identifiers
- 55065 — Supplier clearing list · AS4
Flow
Message from ÜNB · AS4
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
Response message on the LF-CL
LF ÜNBCheck identifiers
- 55066 — Correction list for supplier clearing list · AS4
Flow
Message to ÜNB · 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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0004 | Reconcile market locations with LF-CL |
| E_0014 | Reconcile market locations with LF-CL |
Process information
Wording of the consolidated version, profile ch. 8.5.1, pp. 96–97.
Preconditions
For a single request:
- The LF has the LF-SZR (category B) from the ÜNB.
- The LF knows the MaBiS-ZP of the LF-SZR (category B). In the case of a subscription:
- The LF knows the MaBiS-ZP of the LF-SZR (category B).
Further requirements
If a subscription is requested again while a subscription already exists, from the point in time of receipt the recipient of the subscription refers to the new subscription in all LF-CL resulting from it.
First message
The party involved on this page sends this itself: “Request for the LF-CL” to ÜNB (step 1).
Objective
The LF has the requested LF-CL. If the LF-CL has been subscribed to by the LF, the LF is registered with the ÜNB as a subscriber of the LF-CL. Where applicable, the ÜNB has the response message of the LF on the LF-CL that was sent.
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 source does not yet name the event that triggers these steps.
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.