# Interruption of grid connection use (disconnect) at the instruction of LF — View LF ## Process flow from the perspective of the LF \nSystem diagram: Unterbrechung der Anschlussnutzung (Sperren) 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\n2 alternative events\n\nAPI\n\n1. Sperrauftrag\n\n\nNB\n\nAS4\n17115\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort auf Sperrauftrag\n\n\nNB\n\nAS4\n19116, 19117\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Ergebnis des\nSperrauftrags\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: Unterbrechung der Anschlussnutzung (Sperren) auf Anweisung des LF — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\nMSB\n\n\n2 alternative events\nTrigger event\n\n1. Sperrauftrag\nAS4 · PI 17115\n\nUpdate transaction\nUpdate process data\n\n2. Antwort auf Sperrauftrag\nAS4 · PI 19116, 19117 · E_1000\nE_1000 — Sperrauftrag prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Anfrage\nAS4 · PI 17116\n\n4. Antwort auf Anfrage\nAS4 · PI 19118, 19119 · E_1001\nE_1001 — Anfrage prüfen (Basiert auf Strom EBD: E_0488_Anfrage prüfen)\n\n5. Ergebnis des Sperrauftrags\nAS4 · PI 21039 · E_1002, E_1003\nE_1002 — Ablehnung prüfen, ggf. Clearing durchführen\nE_1003 — Prüfen, ob Sperrauftrag erfolgreich\n\nCreate transaction\nCreate process data\n\n6. Ergebnis des Sperrauftrags\nAS4 · PI 21039 · E_1003\nE_1003 — Prüfen, ob Sperrauftrag erfolgreich\n"} titel="LF" /> ## Process steps ### Disconnection order
**Check identifiers** - [17115](/en/schnittstellen/202610/pruefi/ORDERS/PI_17115) — Disconnection order · AS4
**Flow**
  1. **Process trigger** - [`START_ANFRAGE_SPERRUNG`](/en/api/202610/ausloeser-lf/start-anfrage-sperrung) \"\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_ANFRAGE_SPERRUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_SPERRAUFTRAG`](/en/api/202610/ausloeser-lf/start-sperrauftrag) \"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_SPERRAUFTRAG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with one of these events.
  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 disconnection 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_1000](/en/referenz/202610/ebd/E_1000) · NB · Check disconnection order (Based on electricity EBD: E_0470_Check disconnection 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.
### Request This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [17116](/en/schnittstellen/202610/pruefi/ORDERS/PI_17116) — Request disconnection · AS4
### Response to request This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [19118](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19118) — Confirmation of request disconnection · AS4 - [19119](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19119) — Rejection of request disconnection · AS4
**Response per decision tree** - `19118`, `19119` → [E_1001](/en/referenz/202610/ebd/E_1001) · MSB · Check request (Based on electricity EBD: E_0488_Check request)
### Result of the disconnection 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_1002](/en/referenz/202610/ebd/E_1002) · NB · Check rejection, perform clearing if necessary (Based on electricity EBD: E_0501_Check rejection, perform clearing if necessary) - `21039` → [E_1003](/en/referenz/202610/ebd/E_1003) · NB · Check whether the disconnection order was successful (Based on electricity EBD: E_0472_Check whether the disconnection 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 disconnection 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_1003](/en/referenz/202610/ebd/E_1003) · NB · Check whether the disconnection order was successful (Based on electricity EBD: E_0472_Check whether the disconnection order was successful)
Decision trees of this process | EBD | Name | |---|---| | [E_1000](/referenz/202610/ebd/E_1000) | Check disconnection order (Based on electricity EBD: E_0470_Check disconnection order) | | [E_1002](/referenz/202610/ebd/E_1002) | Check rejection, perform clearing if necessary (Based on electricity EBD: E_0501_Check rejection, perform clearing if necessary) | | [E_1003](/referenz/202610/ebd/E_1003) | Check whether the disconnection order was successful (Based on electricity EBD: E_0472_Check whether the disconnection order was successful) | | [E_1001](/referenz/202610/ebd/E_1001) | Check request (Based on electricity EBD: E_0488_Check request) |
## 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: „Disconnection 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-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf) — NB - [View MSB](/en/prozessdoku/202610/MSB/awh-sperrprozesse-gas-unterbrechung-der-anschlussnutzung-sperren-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: [5](#schritt-5)