Exchange of the supplier clearing list between NB and LF (incl. subscription) — NB 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 A) 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 A). 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 A) that has been sent. An LF-CL is created for every LF-SZR (category A) and can also be requested separately.
Process flow from the perspective of the NB
Process steps
Request for the LF-CL
NB LFCheck identifiers
- 17202 — Req. supplier clearing list · AS4
Flow
Message from LF · 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
Transmission of the LF-CL
NB LFCheck identifiers
- 55065 — Supplier clearing list · AS4
Flow
Message to LF · 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
Response message on the LF-CL
NB LFZ10Z16Z17Z18Check identifiers
- 55066 — Correction list for supplier clearing list · AS4
Flow
Message from LF · AS4
APERAK checks
55066→Z1055066→Z1655066→Z1755066→Z18
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_0047 | Reconcile market locations with LF-CL |
| E_0049 | Reconcile market locations with LF-CL |
Process information
Wording of the consolidated version, profile ch. 7.5.1, pp. 85–86.
Preconditions
For a single request:
- The LF has the LF-SZR (category A) from the NB.
- The LF knows the MaBiS-ZP of the LF-SZR (category A). In the case of a subscription:
- The LF knows the MaBiS-ZP of the LF-SZR (category A).
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
LF sends “Request for the LF-CL” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The LF has the requested supplier clearing list (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 LF — LF
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
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.