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

\nAPI\n"} gesamt={""} titel="NB" /> ## 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**

**Prozessauslöser** [`START_ANFRAGE_STAMMDATENAENDERUNG_GAS`](/en/api/202610/ausloeser-nb/start-anfrage-stammdatenaenderung-gas) \",\n \"gewerbekennzeichnung\": \"\",\n \"name1\": \"\",\n \"name2\": \"\",\n \"name3\": \"\",\n \"name4\": \"\",\n \"partneradresse\": \"\"\n },\n \"hausverwalter\": {\n \"anrede\": \"\",\n \"gewerbekennzeichnung\": \"\",\n \"name1\": \"\",\n \"name2\": \"\",\n \"name3\": \"\",\n \"name4\": \"\",\n \"partneradresse\": \"\"\n },\n \"marktlokationsId\": \"\"\n }\n ],\n \"MESSLOKATION\": [\n {\n \"gasqualitaet\": \"\",\n \"marktrollen\": [\n \"\"\n ],\n \"messlokationsId\": \"\"\n }\n ],\n \"MESSSTELLENBETRIEBSVERTRAG\": [\n {\n \"lokationsId\": \"\",\n \"lokationsTyp\": \"\",\n \"vertragskonditionen\": {\n \"geplanteTurnusablesung\": \"\"\n }\n }\n ],\n \"NETZNUTZUNGSVERTRAG\": [\n {\n \"korrespondenzpartner\": {\n \"anrede\": \"\",\n \"gewerbekennzeichnung\": \"\",\n \"name1\": \"\",\n \"name2\": \"\",\n \"name3\": \"\",\n \"name4\": \"\",\n \"partneradresse\": \"\"\n },\n \"vertragsbeginn\": \"\",\n \"vertragspartner2\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"gueltigAb\": \"\",\n \"kategorie\": \"\",\n \"sparte\": \"\",\n \"transaktionsgrund\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ANFRAGE_STAMMDATENAENDERUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
Message to **LF** · AS4
**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 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**

Message from **LF** · AS4
**Response per decision tree** - `44151`, `44152`, `44138` → [E_3028](/en/referenz/202610/ebd/E_3028) · Check request to LF from NB
**APERAK checks** - `44151`, `44152`, `44138` → `Z33`
**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.

### Change from LF, if applicable (forwarding from NB to MSB)

**Transmission** AS4

**Flow**

Message to **MSB** · AS4
**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**

Message from **MSB** · AS4
**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_3028](/referenz/202610/ebd/E_3028) | Check request to LF from NB |

## Process information

### First message The party involved on this page sends this itself: “Request to LF from NB” to **LF** (step 1).

## 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-lf-verantwortlich) — LF - [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 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)