# Request for master data change from the MSB to NB (responsible) — LF view ## Process flow from the perspective of the LF \nSystem diagram: Anfrage zur Stammdatenänderung vom MSB an NB (verantwortlich) — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n3. Ggf. Änderung vom NB an\nLF\n\nNB\n\nAS4\n44117, 44160\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\nEBD check: G_0027, G_0030\nG_0027 — Antwort auf\nÄnderung vom MSB\nG_0030 — Antwort auf\nÄnderung vom MSB\n\n\nTrigger follow-up process:\n44119, 44161\n\n\nTriggered by incoming\nmessage: 44117, 44160\n\n\n4. Antwort auf Änderung vom\nNB an LF\n\n\nNB\n\nAS4\n44119, 44161\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Anfrage zur Stammdatenänderung vom MSB an NB (verantwortlich) — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nMSB\n\n\nNB\n\n\n1. Anfrage an NB von MSB\nAS4 · PI 44140\n\n2. Antwort auf Anfrage an NB von MSB\nAS4 · PI 44142 · E_3026\nE_3026 — Anfrage zur Stammdatenänderung prüfen\n\n3. Ggf. Änderung vom NB an LF\nAS4 · PI 44117, 44160\n\nCreate transaction\nCreate process data\n\n4. Antwort auf Änderung vom NB an LF\nAS4 · PI 44119, 44161 · E_3027\nE_3027 — Änderung vom NB prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="LF" /> ## Process steps ### Request to NB from MSB This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [44140](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44140) — Not bal.-rel. request to NB · AS4
### Response to request to NB from MSB This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [44142](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44142) — Response to request · AS4
**Response per decision tree** - `44142` → [E_3026](/en/referenz/202610/ebd/E_3026) · Check request for master data change
### Change from NB to LF, if applicable
**Check identifiers** - [44117](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44117) — Change from MSB with dependencies · AS4 - [44160](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44160) — Change from MSB without 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** - `44117`, `44160` → `Z10` — APERAK check: Is location known ? - `44117`, `44160` → `Z17` - `44117`, `44160` → `Z18`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-lf/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
  5. **Decision tree** - `44117` → `G_0027` — Response to change from the MSB - `44160` → `G_0030` — Response to change from the MSB
  6. **Trigger follow-up process** - [44119](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44119) — Response to change from MSB - [44161](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44161) — Response to change After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
### Response to change from the NB to LF
**Check identifiers** - [44119](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44119) — Response to change from MSB · AS4 - [44161](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44161) — Response to change · AS4
**Flow**
  1. **Triggered by incoming message** - [44117](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44117) — Change from MSB with dependencies - [44160](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44160) — Change from MSB without dependencies The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
  2. Message to **NB** · AS4
    **Response per decision tree** - `44119`, `44161` → [E_3027](/en/referenz/202610/ebd/E_3027) · Check change from the NB
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-lf/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_3027](/referenz/202610/ebd/E_3027) | Check change from the NB | | [E_3026](/referenz/202610/ebd/E_3026) | Check request for master data change |
## Process information
  1. ### First message **NB** sends “If applicable, change from NB to LF” (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 NB](/en/prozessdoku/202610/NB/geli-gas-2-0-anfrage-zur-stammdatenanderung-vom-msb-an-nb-verantwortlich) — NB - [View MSB](/en/prozessdoku/202610/MSB/geli-gas-2-0-anfrage-zur-stammdatenanderung-vom-msb-an-nb-verantwortlich) — 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. ::: 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), [4](#schritt-4)