Request for invoice handling of metering point operation via the LF by the LF — MSB-MALO view
The LF has the option of changing the default setting for the invoicing of the metering point operation by order placement, for example following a device replacement to the mME or iMS, following the assignment of a LF, or during ongoing operation. In doing so, the LF implicitly confirms that it is entitled under the supply contract with the AN to demand the billing of the metering charge in its relationship with the MSB of the market location.
Process flow from the perspective of the MSB (MSB-MALO)
Process steps
Request for invoice processing of metering point operation via the LF
MSB (corresponds to MSB at the market location object) LFZ10Z17Z18Check identifiers
- 35002 — Request for invoice processing MSB via LF · AS4
Flow
Message from LF · AS4
APERAK checks
35002→Z1035002→Z1735002→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
Quotation /rejection of request
MSB (corresponds to MSB at the market location object) LF35004Check identifiers
Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to LF · AS4
Response per decision tree
21033→ E_0207 · MSB · Check request
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 quotation
MSB (corresponds to MSB at the market location object) LFZ33Check identifiers
Flow
Message from LF · AS4
Response per decision tree
21032→ E_0208 · LF · Process quotation or rejection of the request
APERAK checks
17005,21032→Z33
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_0207 | Check request |
| E_0208 | Process quotation or rejection of the request |
Process information
Wording of the consolidated version, profile ch. 3.6.3.6.1, p. 74.
Preconditions
- For a market location with one assigned metering location, that metering location must be equipped with a mME or iMS.
- For a market location with at least two assigned metering locations, at least one metering location must be equipped with a mME/a iMS.
- The LF is assigned to the market location of the metering location(s).
- LF is not the payer for the metering point operation.
Results
Order placement: The LF is assigned at the MSB of the market location as the payer for metering point operation.
Error case
Result in the error case
The LF is not assigned as payer of the metering point operation at the MSB of the market location, or, in the case of iMS, the MSB of the market location has already set up the billing of the metering point operation via another LF of a market location affected by the POG determination and the requesting LF is not the payer. The invoicing applies from the confirmation of the quotation, with effect from the requested billing start, for an unlimited period. Any invoicing already confirmed earlier with the same LF that would begin after the billing start thus becomes void.
Error cases
The metering location could not be identified, or the LF has no authorization.
First message
LF sends “Request for invoice processing for metering point operation via the LF” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The LF is the payer of the metering point operation.
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.
Applies to: 2