# Restoration of grid connection use (reconnect) at the instruction of LF — View LF ## Process flow from the perspective of the LF \nSystem diagram: Wiederherstellung der Anschlussnutzung (Entsperren) auf Anweisung des LF — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_ENTSPERRAUFTRAG\n\nAPI\n\n1. Entsperrauftrag\n\n\nNB\n\nAS4\n17117\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort auf\nEntsperrauftrag\n\n\nNB\n\nAS4\n19116, 19117\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Ergebnis des\nEntsperrauftrags\n\n\nNB\n\nAS4\n21039\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z10, Z17,\nZ18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Wiederherstellung der Anschlussnutzung (Entsperren) auf Anweisung des LF — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\nMSB\n\n\nSTART_ENTSPERRAUFTRAG\nTrigger event\n\n1. Entsperrauftrag\nAS4 · PI 17117\n\nUpdate transaction\nUpdate process data\n\n2. Antwort auf Entsperrauftrag\nAS4 · PI 19116, 19117 · E_1004\nE_1004 — Entsperrauftrag prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Information über Entsperrauftrag\nAS4 · PI 21040\n\n4. Ergebnis des Entsperrauftrags\nAS4 · PI 21039 · E_1005\nE_1005 — Prüfen, ob Entsperrauftrag erfolgreich\n\nCreate transaction\nCreate process data\n\n5. Ergebnis des Entsperrauftrags\nAS4 · PI 21039 · E_1005\nE_1005 — Prüfen, ob Entsperrauftrag erfolgreich\n"} titel="LF" /> ## Process steps ### Reconnection order
**Check identifiers** - [17117](/en/schnittstellen/202610/pruefi/ORDERS/PI_17117) — Reconnection order · AS4
**Flow**
  1. **Prozessauslöser** [`START_ENTSPERRAUFTRAG`](/en/api/202610/ausloeser-lf/start-entsperrauftrag) \",\n \"lokationsId\": \"\"\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_ENTSPERRAUFTRAG\",\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-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response to reconnection order
**Check identifiers** - [19116](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19116) — Confirmation of disconnection/reconnection order · AS4 - [19117](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19117) — Rejection of disconnection/reconnection order · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `19116`, `19117` → [E_1004](/en/referenz/202610/ebd/E_1004) · NB · Check reconnection order (Based on electricity EBD: E_0497_Check reconnection order)
  2. **APERAK checks** - `19116`, `19117` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Information on the reconnection order This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [21040](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21040) — Reconnection order info · AS4
### Result of the reconnection order
**Check identifiers** - [21039](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `21039` → [E_1005](/en/referenz/202610/ebd/E_1005) · NB · Check whether the reconnection order was successful (Based on electricity EBD: E_0499_Check whether the reconnection order was successful)
  2. **Load data for the incoming check** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `21039` → `Z10` — APERAK check: Is location known ? - `21039` → `Z17` - `21039` → `Z18`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-lf/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 This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [21039](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Response per decision tree** - `21039` → [E_1005](/en/referenz/202610/ebd/E_1005) · NB · Check whether the reconnection order was successful (Based on electricity EBD: E_0499_Check whether the reconnection order was successful)
Decision trees of this process | EBD | Name | |---|---| | [E_1004](/referenz/202610/ebd/E_1004) | Check reconnection order (Based on electricity EBD: E_0497_Check reconnection order) | | [E_1005](/referenz/202610/ebd/E_1005) | Check whether the reconnection order was successful (Based on electricity EBD: E_0499_Check whether the reconnection order was successful) |
## Process information
  1. ### Trigger **Runs beforehand:** [Cancellation of the interruption and restoration of grid connection use on the instruction of the LF](/en/prozessdoku/202610/LF/GPKE-Teil2-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf) — these processes name the one shown here in their result.
  2. ### First message The party involved on this page is itself the sender of: „Reconnection order“ 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/awh-sperrprozesse-gas-wiederherstellung-der-anschlussnutzung-entsperren-auf-anweisung-des-lf) — NB - [View MSB](/en/prozessdoku/202610/MSB/awh-sperrprozesse-gas-wiederherstellung-der-anschlussnutzung-entsperren-auf-anweisung-des-lf) — 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: [2](#schritt-2) 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: [4](#schritt-4)