# Master data change initiated by LF (responsible) — View NB ## Process flow from the perspective of the NB \nSystem diagram: Stammdatenänderung vom LF (verantwortlich) ausgehend — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Änderung vom LF\n\nLF\n\nAS4\n44109, 44120\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z10, Z16,\nZ17, Z18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nEBD check: G_0023, G_0025\nG_0023 — Antwort auf\nÄnderung vom LF\nG_0025 — Antwort auf\nÄnderung vom LF\n\n\nTrigger follow-up process:\n44111, 44121\n\n\n2. Änderung vom LF\n(Weiterleitung an MSB)\n\n\nMSB\n\nAS4\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nTriggered by incoming\nmessage: 44109, 44120\n\n\n3. Antwort auf Änderung vom\nLF\n\n\nLF\n\nAS4\n44111, 44121\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Antwort auf Änderung vom\nLF\n\n\nMSB\n\nAS4\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Stammdatenänderung vom LF (verantwortlich) ausgehend — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nMSB\n\n\n1. Änderung vom LF\nAS4 · PI 44109, 44120\n\nCreate transaction\nCreate process data\n\n2. Änderung vom LF (Weiterleitung an MSB)\nAS4\n\nUpdate transaction\nUpdate process data\n\n3. Antwort auf Änderung vom LF\nAS4 · PI 44111, 44121 · E_3011\nE_3011 — Änderung vom LF prüfen\n\nUpdate transaction\nUpdate process data\n\n4. Antwort auf Änderung vom LF\nAS4\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Change from the LF
**Check identifiers** - [44109](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44109) — Non-bal.rel change from LF · AS4 - [44120](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44120) — Bal.-rel. change from LF · AS4
**Flow**
  1. Message from **LF** · AS4
  2. **Load data for the incoming check** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `44109`, `44120` → `Z10` - `44109`, `44120` → `Z16` - `44109`, `44120` → `Z17` - `44109`, `44120` → `Z18`
  4. **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.
  5. **Decision tree** - `44109` → `G_0023` — Response to change from the LF - `44120` → `G_0025` — Response to change from the LF
  6. **Trigger follow-up process** - [44111](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44111) — Response to change from LF - [44121](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44121) — Response to change from LF After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
### Change from LF (forwarding to MSB)
**Transmission** AS4
**Flow**
  1. Message to **MSB** · AS4
  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.
### Response to change from the LF
**Check identifiers** - [44111](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44111) — Response to change from LF · AS4 - [44121](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44121) — Response to change from LF · AS4
**Flow**
  1. **Triggered by incoming message** - [44109](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44109) — Non-bal.rel change from LF - [44120](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44120) — Bal.-rel. change from LF The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
  2. Message to **LF** · AS4
    **Response per decision tree** - `44111`, `44121` → [E_3011](/en/referenz/202610/ebd/E_3011) · Check change from the LF
  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 change from the LF
**Transmission** AS4
**Flow**
  1. Message from **MSB** · AS4
  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 with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_3011](/referenz/202610/ebd/E_3011) | Check change from the LF |
## Process information
  1. ### Trigger **Runs beforehand:** [Start of replacement supply / default supply](/en/prozessdoku/202610/NB/GPKE-Teil2-beginn-der-ersatz-grundversorgung), [Case 1: LF assignment for EEG market location without DV obligation or KWKG market location without DV obligation](/en/prozessdoku/202610/NB/GPKE-Teil2-fall-1-lf-zuordnung-bei-eeg-marktlokation-ohne-dv-pflicht-bzw-kwkg-marktlokation-ohne-dv-pflicht), [Case 2: LF assignment for EEG market location with DV obligation](/en/prozessdoku/202610/NB/GPKE-Teil2-fall-2-lf-zuordnung-bei-eeg-marktlokation-mit-dv-pflicht), [Case 3: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped without tranches](/en/prozessdoku/202610/NB/GPKE-Teil2-fall-3-lf-zuordnung-bei-kwkg-marktlokation-mit-dv-pflicht-bzw-nicht-eeg-nicht-kwkg-marktlokation-und-marktlokation-wird-nicht-tranchiert-abgebildet), [Case 4: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped with tranches](/en/prozessdoku/202610/NB/GPKE-Teil2-fall-4-lf-zuordnung-bei-kwkg-marktlokation-mit-dv-pflicht-bzw-nicht-eeg-nicht-kwkg-marktlokation-und-marktlokation-wird-tranchiert-abgebildet), [Start of supply](/en/prozessdoku/202610/NB/GPKE-Teil2-lieferbeginn), [Creation](/en/prozessdoku/202610/NB/GPKE-Teil2-neuanlage) — these processes name the one shown here in their result.
  2. ### First message **LF** sends “Change from LF” (step 1). 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 LF](/en/prozessdoku/202610/LF/geli-gas-2-0-stammdatenanderung-vom-lf-verantwortlich-ausgehend) — LF - [View MSB](/en/prozessdoku/202610/MSB/geli-gas-2-0-stammdatenanderung-vom-lf-verantwortlich-ausgehend) — 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 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: [1](#schritt-1), [2](#schritt-2), [3](#schritt-3), [4](#schritt-4)