# Request for master data change from the NB to MSB (responsible) — MSB view ## Process flow from the perspective of the MSB \nSystem diagram: Anfrage zur Stammdatenänderung vom NB an MSB (verantwortlich) — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB\n\nMarket partner\n\n\n\n1. Anfrage an MSB\n\nNB\n\nAS4\n44166, 44148\n\nLoad data for the incoming\ncheck\n\n\nMesslokation lesen\n\nAPI\n\nAPERAK check: Z10, Z17,\nZ18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nTrigger follow-up process:\n44149, 44167\n\n\nTriggered by incoming\nmessage: 44148, 44166\n\n\nLoad data for processing\n\n\n3 read APIs called\n\nAPI\nlisted at the step\n\n2. Antwort auf Anfrage an\nMSB\n\n\nNB\n\nAS4\n44167, 44149\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Anfrage zur Stammdatenänderung vom NB an MSB (verantwortlich) — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB\n\n\nNB\n\n\nLF\n\n\n1. Anfrage an MSB\nAS4 · PI 44166, 44148\n\nCreate transaction\nCreate process data\n\n2. Antwort auf Anfrage an MSB\nAS4 · PI 44167, 44149 · E_3033\nE_3033 — Anfrage an MSB prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Ggf. Änderung vom MSB\nAS4 · PI 44160, 44117\n\n4. Antwort auf Änderung vom MSB\nAS4 · PI 44161, 44119 · E_3034\nE_3034 — Änderung vom MSB prüfen\n"} titel="MSB" /> ## Process steps ### Request to MSB
**Check identifiers** - [44166](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44166) — Not bal.-rel. request to MSB without dependencies · AS4 - [44148](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44148) — Request to MSB with dependencies · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **Load data for the incoming check** - [Read metering location](/en/api/202610/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it
  3. **APERAK checks** - `44166`, `44148` → `Z10` - `44166`, `44148` → `Z17` - `44166`, `44148` → `Z18`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-msb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
  5. **Trigger follow-up process** - [44149](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44149) — Response to request - [44167](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44167) — Response to request After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
### Response to request to MSB
**Check identifiers** - [44167](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44167) — Response to request · AS4 - [44149](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44149) — Response to request · AS4
**Flow**
  1. **Triggered by incoming message** - [44148](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44148) — Request to MSB with dependencies - [44166](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44166) — Not bal.-rel. request to MSB without dependencies The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
  2. **Load data for processing** - [Read metering location](/en/api/202610/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it - [Read grid usage contract](/en/api/202610/backend-lesen/getgridusagecontractbasic#netznutzungsvertrag-lesen) `GET /getGridUsageContractBasic` Try it - [Read meter](/en/api/202610/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it
  3. Message to **NB** · AS4
    **Response per decision tree** - `44167`, `44149` → [E_3033](/en/referenz/202610/ebd/E_3033) · Check request to MSB
  4. **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.
### Change from MSB, if applicable This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [44160](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44160) — Change from MSB without dependencies · AS4 - [44117](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44117) — Change from MSB with dependencies · AS4
### Response to change from the MSB This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [44161](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44161) — Response to change · AS4 - [44119](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44119) — Response to change from MSB · AS4
**Response per decision tree** - `44161`, `44119` → [E_3034](/en/referenz/202610/ebd/E_3034) · Check change from the MSB
Decision trees of this process | EBD | Name | |---|---| | [E_3033](/referenz/202610/ebd/E_3033) | Check request to MSB | | [E_3034](/referenz/202610/ebd/E_3034) | Check change from the MSB |
## Process information
  1. ### First message **NB** sends “Request to MSB” (step 1). From here on, the party involved on this page has the next move.
## 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 LF](/en/prozessdoku/202610/LF/geli-gas-2-0-anfrage-zur-stammdatenanderung-vom-nb-an-msb-verantwortlich) — LF - [View NB](/en/prozessdoku/202610/NB/geli-gas-2-0-anfrage-zur-stammdatenanderung-vom-nb-an-msb-verantwortlich) — NB *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) 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)