Contract termination of metering point operation — MSBN view
Process flow from the perspective of the MSB (MSBN)
Process steps
Contract termination
MSBN MSBACheck identifiers
- 44039 — Contract termination MSB · AS4
Flow
Prozessauslöser
START_KUENDIGUNG_MSBThe backend triggers this step with this event.
Message to MSBA · 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 contract termination
MSBN MSBAZ33Check identifiers
Flow
Message from MSBA · AS4
Response per decision tree
44041,44040→ E_2000 · Contract termination of metering point operation
APERAK checks
44041,44040→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_2000 | Contract termination of metering point operation |
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 MSBA — the transferring 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.
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: 2
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.