Exchange of the supplier substitute energy clearing list — NB view
On the basis of the market locations assigned to the LF-AASZR, the NB creates the LF-AACL and sends it to the LF. The LF has the option of plausibility-checking the LF-AASZR against the data of the LF-AACL. An LF-AACL is created for every LF-AASZR and can also be requested separately. Where applicable, the NB has the response message of the LF on the LF-AACL that was sent.
Process flow from the perspective of the NB
Process steps
LF-AACL
NB LFCheck identifiers
- 55201 — LF-AACL · 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-AACL
NB LFZ33Z10Z16Z17Z18Check identifiers
- 55202 — Correction list LF-AACL · AS4
Flow
Message from LF · AS4
APERAK checks
55202→Z3355202→Z1055202→Z1655202→Z1755202→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_0096 | Reconcile market locations with LF-AACL |
| E_0097 | Reconcile market locations with LF-AACL |
Process information
Wording of the consolidated version, profile ch. 17.3.2.6.1, p. 245.
Preconditions
- The LF has the LF-AASZR from the NB.
- The LF knows the MaBiS-ZP of the LF-AASZR.
First message
The party involved on this page is itself the sender of: „LF-AACL“ to LF (step 1).
Objective
The LF has the requested supplier substitute energy clearing list (LF-AACL). If the LF-AACL has been subscribed to, the LF is registered with the NB as a subscriber of the LF-AACL.
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 source does not yet name the event that triggers these steps.
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: 2
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.