# Business data request from the NB to the MSB — MSB view ## Process flow from the perspective of the MSB \nSystem diagram: Geschäftsdatenanfrage vom NB an MSB — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB\n\nMarket partner\n\n\n\n1. Geschäftsdatenanfrage\n\nNB\n\nAS4\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n2. Antwort\n\n\nNB\n\nAS4\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Geschäftsdatenanfrage vom NB an MSB — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB\n\n\nNB\n\n\n1. Geschäftsdatenanfrage\nAS4\n\nCreate transaction\nCreate process data\n\n2. Antwort\nAS4\n\nUpdate transaction\nUpdate process data\n"} titel="MSB" /> ## Process steps ### Business data request
**Transmission** AS4
**Flow**
  1. Message from **NB** · AS4
  2. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-msb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
### Response
**Transmission** AS4
**Flow**
  1. Message to **NB** · AS4
  2. **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.
## Process information
  1. ### First message **NB** 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 NB](/en/prozessdoku/202610/NB/geli-gas-2-0-geschaftsdatenanfrage-vom-nb-an-msb) — 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. ::: 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)