# Business data request from the LF to the NB — NB view ## Process flow from the perspective of the NB \nSystem diagram: Geschäftsdatenanfrage vom LF an NB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Geschäftsdatenanfrage\n\nLF\n\nAS4\n17101, 17102\n\nAPERAK check: Z14, Z15,\nZ16, Z10, Z18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nTriggered by incoming\nmessage: 17103, 17126,\n17132\n\n\nProcess trigger received\n\n\nSTART_ERHEBUNG_MESSWE\nRTE\n\nAPI\n\n2. Antwort\n\n\nLF\n\nAS4\n44035, 19101, 19102…\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Geschäftsdatenanfrage vom LF an NB — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\n1. Geschäftsdatenanfrage\nAS4 · PI 17101, 17102\n\nCreate transaction\nCreate process data\n\nSTART_ERHEBUNG_MESSWERTE\nTrigger event\n\n2. Antwort\nAS4 · PI 44035, 19101, 19102… · E_3003\nE_3003 — Geschäftsdatenanfrage zu Stammdaten prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Business data request
**Check identifiers** - [17101](/en/schnittstellen/202610/pruefi/ORDERS/PI_17101) — Request master data market location (gas) · AS4 - [17102](/en/schnittstellen/202610/pruefi/ORDERS/PI_17102) — Request for values · AS4
**Flow**
  1. Message from **LF** · AS4
  2. **APERAK checks** - `17101` → `Z14` - `17101` → `Z15` - `17101`, `17102` → `Z16` - `17102` → `Z10` - `17102` → `Z18`
  3. **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.
### Response
**Check identifiers** - [44035](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44035) — Response to the business data request · AS4 - [19101](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19101) — Rejection of the request master data · AS4 - [19102](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19102) — Rejection of the request values · AS4 - [13008](/en/schnittstellen/202610/pruefi/MSCONS/PI_13008) — Load curve (gas) · AS4 - [13009](/en/schnittstellen/202610/pruefi/MSCONS/PI_13009) — Energy quantity (gas) · AS4 - [13002](/en/schnittstellen/202610/pruefi/MSCONS/PI_13002) — Meter reading (gas) · AS4
**Flow**
  1. **Triggered by incoming message** - [17103](/schnittstellen/202610/pruefi/ORDERS/PI_17103) - [17126](/schnittstellen/202610/pruefi/ORDERS/PI_17126) - [17132](/schnittstellen/202610/pruefi/ORDERS/PI_17132) The MACO APP sends this message itself, as a follow-up process after one of these incoming messages. In addition, the backend can trigger this step with an event — the next item.
  2. **Prozessauslöser** [`START_ERHEBUNG_MESSWERTE`](/en/api/202610/ausloeser-nb/start-erhebung-messwerte) \"\n ],\n \"lokationsId\": \"\"\n }\n ],\n \"ZAEHLER\": [\n {\n \"zaehlernummer\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"anfrageReferenz\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"lokationsTyp\": \"\",\n \"sparte\": \"\",\n \"typ\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ERHEBUNG_MESSWERTE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  3. Message to **LF** · AS4
    **Response per decision tree** - `19101`, `19102` → [E_3003](/en/referenz/202610/ebd/E_3003) · Check business data request for master data
  4. **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.
Decision trees of this process | EBD | Name | |---|---| | [E_3003](/referenz/202610/ebd/E_3003) | Check business data request for master data |
## Process information
  1. ### First message **LF** sends “Business data request” (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-geschaftsdatenanfrage-vom-lf-an-nb) — LF *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)