# Obligation gMSB — View NB ## Process flow from the perspective of the NB \nSystem diagram: Verpflichtung gMSB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n3. Bestätigung der\nÜbernahme des\nMessstellenbetriebes\n\ngMSB\n\nAS4\n44169\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n4. Information über\nNeuzuordnung\n\n\ngMSB\n\nAS4\n44112\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nLoad data for processing\n\n\n4 read APIs called\n\nAPI\nlisted at the step\n"} gesamt={"\nSequence diagram: Verpflichtung gMSB — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\ngMSB\n\n\n3. Bestätigung der Übernahme des Messstellenbetr…\nAS4 · PI 44169\n\nCreate transaction\nCreate process data\n\n4. Information über Neuzuordnung\nAS4 · PI 44112\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Confirmation of the takeover of metering point operation
**Check identifiers** - [44169](/en/schnittstellen/202604/pruefi/UTILMD_GAS/PI_44169) — Confirmation commitment request · AS4
**Flow**
  1. Message from **gMSB** · AS4
  2. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/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.
### Information on reassignment
**Check identifiers** - [44112](/en/schnittstellen/202604/pruefi/UTILMD_GAS/PI_44112) — Non-bal.rel. change from NB · AS4
**Flow**
  1. Message from **gMSB** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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.
  3. **Load data for processing** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read metering location](/en/api/202604/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it - [Read grid usage contract](/en/api/202604/backend-lesen/getgridusagecontractbasic#netznutzungsvertrag-lesen) `GET /getGridUsageContractBasic` Try it - [Read meter](/en/api/202604/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it
## Process information
  1. ### Trigger **Runs beforehand:** [End of metering point operation](/en/prozessdoku/202604/NB/WiM-Teil1-ende-messstellenbetrieb) — these processes name the one shown here in their result.
  2. ### First message **gMSB** sends “Confirmation of the takeover of metering point operation” (step 3). From here on, it is the turn of the party involved on this page.
## 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/202604/MSB/awh-wim-gas-2-0-verpflichtung-gmsb) — default metering point operator · 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. The numbers are those of the source; where one is missing, it is missing there.* :::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: [3](#schritt-3) 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) 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: [3](#schritt-3)