Transmission of price sheet MSB to LF — LF view
The MSB transmits its electronic price sheet to the LF if the LF does not have the electronic price sheet or if at least one price component of the price sheet has changed.
Process flow from the perspective of the LF
Process steps
Price sheet
LF MSBZ33Check identifiers
- 27002 — Price sheets for MSB services · AS4
Flow
Message from MSB · AS4
APERAK checks
27002→Z33— APERAK check: Is referenced message known ?
Write endpoint
kategorie = A→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Write endpoint
kategorie = B→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Process information
Wording of the consolidated version, profile ch. 3.6.2.3.1, p. 67.
Preconditions
- The EDIFACT communication between MSB and LF has been established.
- The LF does not have the current or updated price sheet of the MSB.
Results
The billing of the metering point operation can be created.
Error case
Result in the error case
In the error cases, the price sheet is transmitted again.
Error cases
- Price sheet contains an error
- Price sheet was not transmitted in the current version
- Price sheet was not transmitted in full Price sheet does not begin at 00:00 of a calendar day.
First message
MSB sends “Price sheet” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The LF has the electronic price sheet of the MSB.
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 MSB — MSB
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.