# Restoration of grid connection use at start of supply — View MSB ## Process flow from the perspective of the MSB \nSystem diagram: Wiederherstellung der Anschlussnutzung bei Lieferbeginn — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB\n\nMarket partner\n\n\n\n1. Information über\nEntsperrauftrag\n\nNB\n\nAS4\n21040\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z10\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n2. Ergebnis des\nEntsperrauftrags\n\n\nNB\n\nAS4\n21039\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Wiederherstellung der Anschlussnutzung bei Lieferbeginn — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB\n\n\nNB\n\n\n1. Information über Entsperrauftrag\nAS4 · PI 21040\n\nCreate transaction\nCreate process data\n\n2. Ergebnis des Entsperrauftrags\nAS4 · PI 21039 · E_1020\nE_1020 — Prüfen, ob Entsperrauftrag erfolgreich\n\nCreate transaction\nCreate process data\n"} titel="MSB" /> ## Process steps ### Information on the reconnection order
**Check identifiers** - [21040](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21040) — Reconnection order info · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **Load data for the incoming check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `21040` → `Z10`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/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.
### Result of the reconnection order
**Check identifiers** - [21039](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `21039` → [E_1020](/en/referenz/202604/ebd/E_1020) · NB · Check whether the reconnection order was successful (Based on electricity EBD: E_0487_Check whether the reconnection order was successful)
  2. **Load data for the incoming check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/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.
Decision trees of this process | EBD | Name | |---|---| | [E_1020](/referenz/202604/ebd/E_1020) | Check whether the reconnection order was successful (Based on electricity EBD: E_0487_Check whether the reconnection order was successful) |
## Process information
  1. ### Trigger **Runs beforehand:** [Start of supply](/en/prozessdoku/202604/LF--LFA/GPKE-Teil2-lieferbeginn) — these processes name the one shown here in their result.
  2. ### First message **NB** sends “Information on the reconnection order” (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/202604/NB/awh-sperrprozesse-gas-wiederherstellung-der-anschlussnutzung-bei-lieferbeginn) — 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. :::