# Interruption of grid connection use (disconnect) at the instruction of LF — View NB ## Process flow from the perspective of the NB \nSystem diagram: Unterbrechung der Anschlussnutzung (Sperren) auf Anweisung des LF — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Sperrauftrag\n\nLF\n\nAS4\n17115\n\nLoad data for the incoming\ncheck\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\nAPERAK check: Z10, Z16,\nZ17, Z18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nLoad data for the check\n\n\n4 read APIs called\n\nAPI\nlisted at the step\n\nEBD check: E_1000\nSperrauftrag prüfen (Basiert\nauf Strom EBD:\nE_0470_Sperrauftrag prüfen)\n\n\nTrigger follow-up process:\n19116, 19117\n\n\nTriggered by incoming\nmessage: 17115\n\n\n2. Antwort auf Sperrauftrag\n\n\nLF\n\nAS4\n19116, 19117\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_ANFRAGE_SPERRUN\nG\n\nAPI\n\n3. Anfrage\n\n\nMSB\n\nAS4\n17116\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n4. Antwort auf Anfrage\n\n\nMSB\n\nAS4\n19118, 19119\n\nAPERAK check: Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nProcess trigger received\n\n\n2 alternative events\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n5. Ergebnis des\nSperrauftrags\n\n\nLF\n\nAS4\n21039\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\n2 alternative events\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n6. Ergebnis des\nSperrauftrags\n\n\nMSB\n\nAS4\n21039\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Unterbrechung der Anschlussnutzung (Sperren) auf Anweisung des LF — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nMSB\n\n\n1. Sperrauftrag\nAS4 · PI 17115\n\nCreate transaction\nCreate 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\nSTART_ANFRAGE_SPERRUNG\nTrigger event\n\n3. Anfrage\nAS4 · PI 17116\n\nCreate transaction\nCreate process data\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\nCreate transaction\nCreate process data\n\n2 alternative events\nTrigger event\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\nUpdate transaction\nUpdate process data\n\n2 alternative events\nTrigger event\n\n6. Ergebnis des Sperrauftrags\nAS4 · PI 21039 · E_1003\nE_1003 — Prüfen, ob Sperrauftrag erfolgreich\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Disconnection order
**Check identifiers** - [17115](/en/schnittstellen/202610/pruefi/ORDERS/PI_17115) — Disconnection order · AS4
**Flow**
  1. Message from **LF** · AS4
  2. **Load data for the incoming check** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read metering location](/en/api/202610/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it
  3. **APERAK checks** - `17115` → `Z10` - `17115` → `Z16` - `17115` → `Z17` - `17115` → `Z18`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-nb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
  5. **Load data for the check** - [Read location bundle](/en/api/202610/backend-lesen/getlocationbundlebasic#lokationsbundel-lesen) `GET /getLocationBundleBasic` Try it - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read grid usage contract](/en/api/202610/backend-lesen/getgridusagecontractbasic#netznutzungsvertrag-lesen) `GET /getGridUsageContractBasic` Try it - [Read price sheet](/en/api/202610/backend-lesen/getpricesheetbasic#preisblatt-lesen) `GET /getPriceSheetBasic` Try it
  6. **Decision tree** - `17115` → [E_1000](/en/referenz/202610/ebd/E_1000) — Check disconnection order (Based on electricity EBD: E_0470_Check disconnection order)
  7. **Trigger follow-up process** - [19116](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19116) — Confirmation of disconnection/reconnection order - [19117](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19117) — Rejection of disconnection/reconnection order After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
### 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. **Triggered by incoming message** - [17115](/en/schnittstellen/202610/pruefi/ORDERS/PI_17115) — Disconnection order The MACO APP sends this message itself, as a follow-up process after this incoming message.
  2. Message to **LF** · 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)
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Request
**Check identifiers** - [17116](/en/schnittstellen/202610/pruefi/ORDERS/PI_17116) — Request disconnection · AS4
**Flow**
  1. **Prozessauslöser** [`START_ANFRAGE_SPERRUNG`](/en/api/202610/ausloeser-nb/start-anfrage-sperrung) \"\n }\n ],\n \"AUFTRAG\": [\n {\n \"ausfuehrungsdatum\": \"\"\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 The backend triggers this step with this event.
  2. Message to **MSB** · AS4
  3. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-nb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend once the message has been created.
### Response to request
**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
**Flow**
  1. Message from **MSB** · 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)
  2. **APERAK checks** - `19118`, `19119` → `Z33`
  3. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-nb/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
**Check identifiers** - [21039](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Flow**
  1. **Process trigger** - [`START_AUFTRAGSSTATUS`](/en/api/202610/ausloeser-nb/start-auftragsstatus) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_AUFTRAGSSTATUS\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_WIEDERHERST_LB`](/en/api/202610/ausloeser-nb/start-wiederherst-lb) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_WIEDERHERST_LB\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with one of these events.
  2. **Load data for processing** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - `LESEN_STATUSMITTEILUNG_BASIS`
  3. Message to **LF** · 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)
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Result of the disconnection order
**Check identifiers** - [21039](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Flow**
  1. **Process trigger** - [`START_AUFTRAGSSTATUS`](/en/api/202610/ausloeser-nb/start-auftragsstatus) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_AUFTRAGSSTATUS\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_WIEDERHERST_LB`](/en/api/202610/ausloeser-nb/start-wiederherst-lb) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_WIEDERHERST_LB\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with one of these events.
  2. **Load data for processing** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - `LESEN_STATUSMITTEILUNG_BASIS`
  3. Message to **MSB** · 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)
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
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_1001](/referenz/202610/ebd/E_1001) | Check request (Based on electricity EBD: E_0488_Check request) | | [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) |
## 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/NB/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 **LF** sends “Disconnection 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 LF](/en/prozessdoku/202610/LF/awh-sperrprozesse-gas-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf) — LF - [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. ::: These read accesses are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button. Applies to: [5](#schritt-5), [6](#schritt-6) 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), [6](#schritt-6)