Metering location change from LF to MSB — LF view
Process flow from the perspective of the LF
Process steps
Request for a quotation for the metering location change
LF MSB (corresponds to MSB at the metering location object)Check identifiers
- 35005 — Request for quotation for technical change · AS4
Flow
Message to MSB (corresponds to MSB at the metering location object) · 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
Quotation or rejection of the request
LF MSB (corresponds to MSB at the metering location object)Z33Check identifiers
Flow
Message from MSB (corresponds to MSB at the metering location object) · AS4
Response per decision tree
21033→ E_0281 · MSB · Check request
APERAK checks
15005,21033→Z33— APERAK check: Is referenced message known ?
Write endpoint
21033→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Write endpoint
15005→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Order placement
LF MSB (corresponds to MSB at the metering location object)Check identifiers
- 17011 — Order placement quotation change of technology · AS4
Flow
Message to MSB (corresponds to MSB at the metering location object) · 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 to order placement
LF MSB (corresponds to MSB at the metering location object)Z33Check identifiers
Flow
Message from MSB (corresponds to MSB at the metering location object) · AS4
Response per decision tree
19005,19006→ E_0283 · MSB · Check order placement
APERAK checks
19005,19006→Z33— APERAK check: Is referenced message known ?
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
Failure of the change
LF MSB (corresponds to MSB at the metering location object)Z10Z17Z18Check identifiers
- 21025 — Status message · AS4
Flow
Message from MSB (corresponds to MSB at the metering location object) · AS4
Response per decision tree
21025→ E_0286 · MSB · Carry out metering location change
APERAK checks
21025→Z10— APERAK check: Is location known ?21025→Z1721025→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_0281 | Check request |
| E_0283 | Check order placement |
| E_0286 | Carry out metering location change |
Process information
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 source provides no use case profile for this process — objective, precondition and result are not recorded there.
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 numbers are those of the source; where one is missing, it is missing there.
Step sequence reconstructed
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.
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.
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.