# End of metering point operation — MSBA view The use case describes the interactions between the market participants on the occasion of a termination of metering point operation to be initiated by the MSB. The process is also to be applied when a single metering location is decommissioned by a wMSB and gMSB. The NB must ensure uninterrupted metering by involving the gMSB in good time. ## Process flow from the perspective of the MSB (MSBA) \nSystem diagram: Ende Messstellenbetrieb — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB (entsprich…\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_ENDE_MSB\n\nAPI\n\n1. Abmeldung\n\n\nNB\n\nAS4\n55051\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort auf Abmeldung\n\n\nNB\n\nAS4\n55052, 55053\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Weiterverpflichtung des\nMSB\n\n\nNB\n\nAS4\n17002\n\nAPERAK check: Z10, Z17,\nZ18\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n6. Antwort auf\nWeiter-verpflichtung\n\n\nNB\n\nAS4\n19003, 19004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Ende Messstellenbetrieb — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB (entsprich…\n\n\nNB\n\n\nMSB (entspricht gMSB am O…\n\n\nSTART_ENDE_MSB\nTrigger event\n\n1. Abmeldung\nAS4 · PI 55051\n\nUpdate transaction\nUpdate process data\n\n2. Antwort auf Abmeldung\nAS4 · PI 55052, 55053 · E_0202\nE_0202 — Abmeldung Messstellenbetrieb prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Verpflichtungs-anfrage\nAS4 · PI 55168\n\n4. Antwort auf Verpflichtungs-anfrage\nAS4 · PI 55169, 55170 · E_0240\nE_0240 — Verpflichtungsanfrage prüfen\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_0203\nE_0203 — Weiterverpflichtung prüfen\n\nUpdate transaction\nUpdate process data\n\n7. Aufforderung zur Übernahme der einzelnen Mess…\nAS4 · PI 55168\n"} titel="MSBA" /> ## Process steps ### Deregistration
**Check identifiers** - [55051](/en/schnittstellen/202610/pruefi/UTILMD/PI_55051) — End MSB · AS4
**Flow**
  1. **Prozessauslöser** [`START_ENDE_MSB`](/en/api/202610/ausloeser-msb/start-ende-msb) \"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"pruefidentifikator\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ENDE_MSB\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · 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 deregistration
**Check identifiers** - [55052](/en/schnittstellen/202610/pruefi/UTILMD/PI_55052) — Confirmation end MSB · AS4 - [55053](/en/schnittstellen/202610/pruefi/UTILMD/PI_55053) — Rejection end MSB · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `55052`, `55053` → [E_0202](/en/referenz/202610/ebd/E_0202) · Check deregistration of metering point operation
  2. **APERAK checks** - `55052`, `55053` → `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.
### Commitment request This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55168](/en/schnittstellen/202610/pruefi/UTILMD/PI_55168) — Commitment request / demand · AS4
### Response to commitment request This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55169](/en/schnittstellen/202610/pruefi/UTILMD/PI_55169) — Confirmation commitment request · AS4 - [55170](/en/schnittstellen/202610/pruefi/UTILMD/PI_55170) — Rejection commitment request · AS4
**Response per decision tree** - `55169`, `55170` → [E_0240](/en/referenz/202610/ebd/E_0240) · Check commitment request
### Continued commitment of the MSB
**Check identifiers** - [17002](/en/schnittstellen/202610/pruefi/ORDERS/PI_17002) — Continued commitment · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **APERAK checks** - `17002` → `Z10` - `17002` → `Z17` - `17002` → `Z18`
  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.
### 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 to **NB** · AS4
    **Response per decision tree** - `19003`, `19004` → [E_0203](/en/referenz/202610/ebd/E_0203) · Check continued commitment
  2. **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.
### Request to take over the individual metering location by the gMSB This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55168](/en/schnittstellen/202610/pruefi/UTILMD/PI_55168) — Commitment request / demand · AS4
Decision trees of this process | EBD | Name | |---|---| | [E_0202](/referenz/202610/ebd/E_0202) | Check deregistration of metering point operation | | [E_0203](/referenz/202610/ebd/E_0203) | Check continued commitment | | [E_0240](/referenz/202610/ebd/E_0240) | Check commitment request |
## Process information Wording of the consolidated version, profile ch. 2.4.1, p. 30.
  1. ### Preconditions Termination of a MSB contract
  2. ### Results - The NB can distribute the master data changed as a result at the metering or market location of a location bundle to the authorised parties (e.g. the wMSB is in a continued commitment), or - the gMSB can serve the use case „[Obligation gMSB](/en/prozessdoku/202610/MSB--MSBA/WiM-Teil1-verpflichtung-gmsb)“.
  3. ### Error case #### Error cases The metering location was not assigned to the MSB.
  4. ### Trigger **Runs beforehand:** [Contract termination of metering point operation](/en/prozessdoku/202610/MSB--MSBA/WiM-Teil1-kuendigung-messstellenbetrieb) — these processes name the one shown here in their result.
  5. ### First message The party involved on this page sends this itself: “Deregistration” to **NB** (step 1).
  6. ### Objective The MSB is no longer assigned to a metering location or has been obliged to continue performing metering point operation.
## 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/WiM-Teil1-ende-messstellenbetrieb) — default metering point operator · market role MSB - [View NB](/en/prozessdoku/202610/NB/WiM-Teil1-ende-messstellenbetrieb) — NB *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 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: [5](#schritt-5)