# Contract termination of metering point operation — MSBN view ## Process flow from the perspective of the MSB (MSBN) \nSystem diagram: Kündigung Messstellenbetrieb — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSBN\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_KUENDIGUNG_MSB\n\nAPI\n\n1. Kündigung\n\n\nMSBA\n\nAS4\n44039\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort auf Kündigung\n\n\nMSBA\n\nAS4\n44041, 44040\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Kündigung Messstellenbetrieb — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSBN\n\n\nMSBA\n\n\nSTART_KUENDIGUNG_MSB\nTrigger event\n\n1. Kündigung\nAS4 · PI 44039\n\nUpdate transaction\nUpdate process data\n\n2. Antwort auf Kündigung\nAS4 · PI 44041, 44040 · E_2000\nE_2000 — Kündigung Messstellenbetrieb\n\nUpdate transaction\nUpdate process data\n"} titel="MSBN" /> ## Process steps ### Contract termination
**Check identifiers** - [44039](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44039) — Contract termination MSB · AS4
**Flow**
  1. **Prozessauslöser** [`START_KUENDIGUNG_MSB`](/en/api/202610/ausloeser-msb/start-kuendigung-msb) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"pruefidentifikator\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_KUENDIGUNG_MSB\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **MSBA** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response to contract termination
**Check identifiers** - [44041](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44041) — Rejection of contract termination MSB · AS4 - [44040](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44040) — Confirmation of contract termination MSB · AS4
**Flow**
  1. Message from **MSBA** · AS4
    **Response per decision tree** - `44041`, `44040` → [E_2000](/en/referenz/202610/ebd/E_2000) · Contract termination of metering point operation
  2. **APERAK checks** - `44041`, `44040` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_2000](/referenz/202610/ebd/E_2000) | Contract termination of metering point operation |
## Process information
  1. ### First message The party involved on this page is itself the sender of: „Contract termination“ to **MSBA** (step 1).
## 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](/en/prozessdoku/202610/MSB--MSBA/awh-wim-gas-2-0-kundigung-messstellenbetrieb) — the transferring MSB · market role MSB *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.* :::caution{title="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](#schritt-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. Applies to: [1](#schritt-1), [2](#schritt-2)