Cancellation of values from MSB of the metering location — View MSB-MALO
The MSB of the market location transmits a cancellation for values already transmitted to the parties that previously received the values to be cancelled. The MSB of the metering location transmits a cancellation for values already transmitted to the MSB of the market location.
Process flow from the perspective of the MSB (MSB-MALO)
Process steps
Cancellation
MSB (corresponds to MSB at the market location object) MSB (corresponds to MSB at the metering location object)Z33Check identifiers
- 13006 — Meter reading value cancellation · AS4
Flow
Message from MSB (corresponds to MSB at the metering location object) · AS4
APERAK checks
13006→Z33
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. 2.8.1, p. 55.
Preconditions
- Values were transmitted previously.
- The values subject to complaint are relevant for cancellation.
Results
For values relevant to cancellation, the values can be transmitted again.
Trigger
- Check result from the complaint provides for cancellation or
- a value transmitted to the market by mistake has to be cancelled.
First message
MSB (corresponds to MSB on the metering location object) sends “Cancellation” (step 1). From here on, the party involved on this side is the one to act.
Objective
Cancellation of transmitted values at all parties involved.
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-MELO — MSB at the metering location object · market role 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.
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