System diagram: Anfrage zur Stammdatenänderung vom NB an LF (verantwortlich)

# Request for master data change from the NB to LF (responsible) — LF view ## Process flow from the perspective of the LF \nSystem diagram: Anfrage zur Stammdatenänderung vom NB an LF (verantwortlich) — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Anfrage an LF vom NB\n\nNB\n\nAS4\n44150, 44137\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z10, Z17,\nZ18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\nPI 44137\n\nCreate transaction\n\n\nCreate process data\n\nAPI\nPI 44150\n\nEBD check: G_0039, G_0038,\nG_0040\nG_0039 — Ablehnung der\nAnfrage\nG_0038 — Antwort auf\nAnfrage\nG_0040 — Antwort auf\nAnfrage\n\n\nTrigger follow-up process:\n44138\n\n\nTriggered by incoming\nmessage: 44137\n\n\n2. Antwort auf Anfrage an LF\nvom NB\n\n\nNB\n\nAS4\n44151, 44152, 44138\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={""} titel="LF" /> ## Process steps ### Request to LF from the NB

**Check identifiers** - [44150](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44150) — Bal.-rel. request to LF · AS4 - [44137](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44137) — Not bal.-rel. request to LF · AS4

**Flow**

Message from **NB** · AS4
**Load data for the incoming check** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
**APERAK checks** - `44150`, `44137` → `Z10` — APERAK check: Is location known ? - `44150`, `44137` → `Z17` - `44150`, `44137` → `Z18`
**Write endpoint** - `44137` → 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.
**Write endpoint** - `44150` → 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.
**Decision tree** - `44150` → `G_0039` — Rejection of the request - `44150` → `G_0038` — Response to request - `44137` → `G_0040` — Response to request
**Trigger follow-up process** - [44138](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44138) — Response to request After processing, the MACO APP starts this follow-up process itself.

### Response to request to LF from NB

**Check identifiers** - [44151](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44151) — Response to request · AS4 - [44152](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44152) — Rejection of the request · AS4 - [44138](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44138) — Response to request · AS4

**Flow**

**Triggered by incoming message** - [44137](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44137) — Not bal.-rel. request to LF The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to **NB** · AS4
**Response per decision tree** - `44151`, `44152`, `44138` → [E_3028](/en/referenz/202610/ebd/E_3028) · Check request to LF from NB
**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.

### Change from LF, if applicable (forwarding from NB to MSB) This step runs between other market partners and is not relevant for this view.

**Transmission** AS4

### Response to change from the LF This step runs between other market partners and is not relevant for this view.

**Transmission** AS4

Decision trees of this process

| EBD | Name | |---|---| | [E_3028](/referenz/202610/ebd/E_3028) | Check request to LF from NB |

## Process information

### First message **NB** sends “Request to LF from NB” (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 NB](/en/prozessdoku/202610/NB/geli-gas-2-0-anfrage-zur-stammdatenanderung-vom-nb-an-lf-verantwortlich) — NB - [View MSB](/en/prozessdoku/202610/MSB/geli-gas-2-0-anfrage-zur-stammdatenanderung-vom-nb-an-lf-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. ::: 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)