Request for the supplier substitute energy clearing list, one-off or via a subscription — ANB view
The LF requests or, where required, subscribes to the LF-AACL from the NB.
Process flow from the perspective of the NB (ANB)
Process steps
Request for the supplier substitute energy clearing list, one-off or by subscription
NB (ANB) LFCheck identifiers
- 17210 — Request for supplier substitute energy 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
Process information
Wording of the consolidated version, profile ch. 17.3.2.5.1, p. 243.
Preconditions
For a single request:
- The LF has the LF-AASZR from the NB.
- The LF knows the MaBiS-ZP of the LF-AASZR. In the case of a subscription: the LF knows the MaBiS-ZP of the LF-AASZR.
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-AACL resulting from it.
First message
LF sends “Request for the supplier substitute energy clearing list, one-off or by subscription” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The NB can start the process “Transmission of the LF-AASZR” (once or as a subscription).
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
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