# End of metering point operation from the MSB to the NB — NB view ## Process flow from the perspective of the NB \nSystem diagram: Ende Messstellenbetrieb vom MSB an NB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Abmeldung\n\nMSBA\n\nAS4\n44051\n\nAPERAK check: Z10, Z16,\nZ17, Z18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n2. Antwort auf Abmeldung\n\n\nMSBA\n\nAS4\n44053, 44052\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n3. Verpflichtungsanfrage\n\n\ngMSB\n\nAS4\n44168\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Antwort auf\nVerpflichtungsanfrage\n\n\ngMSB\n\nAS4\n44169\n\nAPERAK check: Z33, Z10,\nZ16, Z17, Z18\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nTriggered by incoming\nmessage: 55170\n\n\n5. Weiterverpflichtung des\nMSB\n\n\nMSBA\n\nAS4\n17002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n6. Antwort auf\nWeiter-verpflichtung\n\n\nMSBA\n\nAS4\n19003, 19004\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n7. Aufforderung zur\nÜbernahme der Messlokation\ndurch den gMSB\n\n\ngMSB\n\nAS4\n44168\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Ende Messstellenbetrieb vom MSB an NB — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nMSBA\n\n\ngMSB\n\n\n1. Abmeldung\nAS4 · PI 44051\n\nCreate transaction\nCreate process data\n\n2. Antwort auf Abmeldung\nAS4 · PI 44053, 44052 · E_2005\nE_2005 — Abmeldung Messstellenbetrieb prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Verpflichtungsanfrage\nAS4 · PI 44168\n\nUpdate transaction\nUpdate process data\n\n4. Antwort auf Verpflichtungsanfrage\nAS4 · PI 44169 · E_2006\nE_2006 — Weiterverpflichtung prüfen\n\nUpdate transaction\nUpdate process data\n\n5. Weiterverpflichtung des MSB\nAS4 · PI 17002\n\nUpdate transaction\nUpdate process data\n\n6. Antwort auf Weiter-verpflichtung\nAS4 · PI 19003, 19004 · E_2004\nE_2004 — Weiterverpflichtung prüfen\n\nUpdate transaction\nUpdate process data\n\n7. Aufforderung zur Übernahme der Messlokation d…\nAS4 · PI 44168\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Deregistration
**Check identifiers** - [44051](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44051) — End of MSB · AS4
**Flow**
  1. Message from **MSBA** · AS4
  2. **APERAK checks** - `44051` → `Z10` - `44051` → `Z16` - `44051` → `Z17` - `44051` → `Z18`
  3. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-nb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
### Response to deregistration
**Check identifiers** - [44053](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44053) — Rejection of end of MSB · AS4 - [44052](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44052) — Confirmation of end of MSB · AS4
**Flow**
  1. Message to **MSBA** · AS4
    **Response per decision tree** - `44053`, `44052` → [E_2005](/en/referenz/202610/ebd/E_2005) · Check deregistration of metering point operation
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Commitment request
**Check identifiers** - [44168](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44168) — Commitment request / demand · AS4
**Flow**
  1. **Load data for processing** - [Read metering point operation contract](/en/api/202610/backend-lesen/getmeasuringpointoperationcontractbasic#messstellenbetriebsvertrag-lesen) `GET /getMeasuringPointOperationContractBasic` Try it - [Read meter](/en/api/202610/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it
  2. Message to **gMSB** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response to commitment request
**Check identifiers** - [44169](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44169) — Confirmation commitment request · AS4
**Flow**
  1. Message from **gMSB** · AS4
    **Response per decision tree** - `44169` → [E_2006](/en/referenz/202610/ebd/E_2006) · Check continued commitment
  2. **APERAK checks** - `44169` → `Z33` - `44169` → `Z10` - `44169` → `Z16` - `44169` → `Z17` - `44169` → `Z18`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Continued commitment of the MSB
**Check identifiers** - [17002](/en/schnittstellen/202610/pruefi/ORDERS/PI_17002) — Continued commitment · AS4
**Flow**
  1. **Triggered by incoming message** - [55170](/schnittstellen/202610/pruefi/UTILMD/PI_55170) The MACO APP sends this message itself, as a follow-up process after this incoming message.
  2. Message to **MSBA** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response to continued commitment
**Check identifiers** - [19003](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19003) — Confirmation of continued commitment · AS4 - [19004](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19004) — Rejection of continued commitment · AS4
**Flow**
  1. Message from **MSBA** · AS4
    **Response per decision tree** - `19003`, `19004` → [E_2004](/en/referenz/202610/ebd/E_2004) · Check continued commitment
  2. **APERAK checks** - `19003`, `19004` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Request to take over the metering location by the gMSB
**Check identifiers** - [44168](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44168) — Commitment request / demand · AS4
**Flow**
  1. **Load data for processing** - [Read metering point operation contract](/en/api/202610/backend-lesen/getmeasuringpointoperationcontractbasic#messstellenbetriebsvertrag-lesen) `GET /getMeasuringPointOperationContractBasic` Try it - [Read meter](/en/api/202610/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it
  2. Message to **gMSB** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
Decision trees of this process | EBD | Name | |---|---| | [E_2004](/referenz/202610/ebd/E_2004) | Check continued commitment | | [E_2005](/referenz/202610/ebd/E_2005) | Check deregistration of metering point operation | | [E_2006](/referenz/202610/ebd/E_2006) | Check continued commitment |
## Process information
  1. ### First message **MSBA** sends “Deregistration” (Step 1). From here on, the party involved on this page takes its turn.
## 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 GMSB](/en/prozessdoku/202610/MSB--GMSB/awh-wim-gas-2-0-ende-messstellenbetrieb-vom-msb-an-nb) — default metering point operator · market role MSB - [View MSBA](/en/prozessdoku/202610/MSB--MSBA/awh-wim-gas-2-0-ende-messstellenbetrieb-vom-msb-an-nb) — 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 process begins for the own role with their message, so the transaction is created. Applies to: [1](#schritt-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. Applies to: [4](#schritt-4), [6](#schritt-6) 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), [3](#schritt-3), [4](#schritt-4), [7](#schritt-7)