# Business data request from the MSB to the NB — MSB view ## Process flow from the perspective of the MSB \nSystem diagram: Geschäftsdatenanfrage vom MSB an NB — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB (Strom / G…\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_GESCHAEFTSDATEN\nANFRAGE\n\nAPI\n\n1. Geschäftsdatenanfrage\n\n\nNB\n\nAS4\n17126\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort\n\n\nNB\n\nAS4\n19101, 44060\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Geschäftsdatenanfrage vom MSB an NB — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB (Strom / G…\n\n\nNB\n\n\nSTART_GESCHAEFTSDATENANFRAGE\nTrigger event\n\n1. Geschäftsdatenanfrage\nAS4 · PI 17126\n\nUpdate transaction\nUpdate process data\n\n2. Antwort\nAS4 · PI 19101, 44060 · E_3004\nE_3004 — Geschäftsdatenanfrage zu Stammdaten prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="MSB" /> ## Process steps ### Business data request
**Check identifiers** - [17126](/en/schnittstellen/202610/pruefi/ORDERS/PI_17126) — Request master data metering location (gas) · AS4
**Flow**
  1. **Prozessauslöser** [`START_GESCHAEFTSDATENANFRAGE`](/en/api/202610/ausloeser-msb/start-geschaeftsdatenanfrage) \"\n }\n ],\n \"MESSLOKATION\": [\n {\n \"messadresse\": {\n \"hausnummer\": \"\",\n \"landescode\": \"\",\n \"ort\": \"\",\n \"ortsteil\": \"\",\n \"postfach\": \"\",\n \"postleitzahl\": \"\",\n \"strasse\": \"\",\n \"zusatzInformation\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_GESCHAEFTSDATENANFRAGE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response
**Check identifiers** - [19101](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19101) — Rejection of the request master data · AS4 - [44060](/en/schnittstellen/202610/pruefi/UTILMD_GAS/PI_44060) — Response to the business data request · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `19101` → [E_3004](/en/referenz/202610/ebd/E_3004) · NB · Check business data request for master data
  2. **APERAK checks** - `19101`, `44060` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/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_3004](/referenz/202610/ebd/E_3004) | Check business data request for master data |
## Process information
  1. ### First message The party involved on this page is itself the sender of: „Business data request“ to **NB** (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 NB](/en/prozessdoku/202610/NB/geli-gas-2-0-geschaftsdatenanfrage-vom-msb-an-nb) — NB *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. :::