Contract termination of metering point operation — MSBA view
Process flow from the perspective of the MSB (MSBA)
Process steps
Contract termination
MSBA MSBNG_0051_G_0052 Check contract termination MSB4404044041Check identifiers
- 44039 — Contract termination MSB · AS4
Flow
Message from MSBN · AS4
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
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
Load data for the check
- Read metering location
GET /getMeterLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic
- Read metering location
Decision tree
44039→G_0051_G_0052— Check contract termination MSB
Trigger follow-up process
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response to contract termination
MSBA MSBN44039Check identifiers
Flow
Triggered by incoming message
- 44039 — Contract termination MSB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read energy supply contract
GET /getEnergySupplyContractBasic - Read metering location
GET /getMeterLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic - Read meter
GET /getCounterBasic
- Read energy supply contract
Message to MSBN · AS4
Response per decision tree
44041,44040→E_2000
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
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 MSBN — the receiving MSB · 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.
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.
For these decision trees of the process there is no source in this format version:
E_2000