# Interruption of grid connection use (disconnect) at the instruction of LF — View NB In accordance with the grid usage contract (supplier framework contract) concluded between the LF and the NB, the LF instructs the NB to interrupt the grid connection use at the named market location of the AN supplied by the LF. The number of disconnection attempts per disconnection order depends on the general terms and conditions of the NB. The LF announces the disconnection to the AN. The NB checks whether the necessary preconditions for a disconnection are met and carries the disconnection out if they are. If the MSB has not granted the NB general consent to carry out the disconnection/reconnection, the MSB is asked. The NB informs the LF, where applicable the MSB and where applicable the ÜNB about the disconnection result. ## 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\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_0470\nSperrauftrag 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\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\n7. Ergebnis des\nSperrauftrags\n\n\nÜNB\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\nÜNB\n\n\n1. Sperrauftrag\nAS4 · PI 17115\n\nCreate transaction\nCreate process data\n\n2. Antwort auf Sperrauftrag\nAS4 · PI 19116, 19117 · E_0470\nE_0470 — 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_0488\nE_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_0472, E_0501\nE_0472 — Prüfen, ob Sperrauftrag erfolgreich\nE_0501 — Ablehnung prüfen, ggf. Clearing durchführen\n\nUpdate transaction\nUpdate process data\n\n2 alternative events\nTrigger event\n\n6. Ergebnis des Sperrauftrags\nAS4 · PI 21039 · E_0472\nE_0472 — Prüfen, ob Sperrauftrag erfolgreich\n\nUpdate transaction\nUpdate process data\n\n2 alternative events\nTrigger event\n\n7. Ergebnis des Sperrauftrags\nAS4 · PI 21039 · E_0472\nE_0472 — Prüfen, ob Sperrauftrag erfolgreich\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Disconnection order
**Check identifiers** - [17115](/en/schnittstellen/202604/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/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read metering location](/en/api/202604/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it
  3. **APERAK checks** - `17115` → `Z10`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/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/202604/backend-lesen/getlocationbundlebasic#lokationsbundel-lesen) `GET /getLocationBundleBasic` Try it - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read grid usage contract](/en/api/202604/backend-lesen/getgridusagecontractbasic#netznutzungsvertrag-lesen) `GET /getGridUsageContractBasic` Try it - [Read price sheet](/en/api/202604/backend-lesen/getpricesheetbasic#preisblatt-lesen) `GET /getPriceSheetBasic` Try it
  6. **Decision tree** - `17115` → [E_0470](/en/referenz/202604/ebd/E_0470) — Check disconnection order
  7. **Trigger follow-up process** - [19116](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19116) — Confirmation of disconnection/reconnection order - [19117](/en/schnittstellen/202604/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/202604/pruefi/ORDRSP/PI_19116) — Confirmation of disconnection/reconnection order · AS4 - [19117](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19117) — Rejection of disconnection/reconnection order · AS4
**Flow**
  1. **Triggered by incoming message** - [17115](/en/schnittstellen/202604/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_0470](/en/referenz/202604/ebd/E_0470) · NB · Check disconnection order
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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/202604/pruefi/ORDERS/PI_17116) — Request disconnection · AS4
**Flow**
  1. **Prozessauslöser** [`START_ANFRAGE_SPERRUNG`](/en/api/202604/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/202604/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/202604/pruefi/ORDRSP/PI_19118) — Confirmation of request disconnection · AS4 - [19119](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19119) — Rejection of request disconnection · AS4
**Flow**
  1. Message from **MSB** · AS4
    **Response per decision tree** - `19118`, `19119` → [E_0488](/en/referenz/202604/ebd/E_0488) · MSB · Check request
  2. **APERAK checks** - `19118`, `19119` → `Z33`
  3. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/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/202604/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Flow**
  1. **Process trigger** - [`START_AUFTRAGSSTATUS`](/en/api/202604/ausloeser-nb/start-auftragsstatus) \"\n }\n ],\n \"STATUSMITTEILUNG\": [\n {\n \"positionsdaten\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"antwortstatus\": \"\",\n \"antwortstatusCodeliste\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"fertigstellungsdatum\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_AUFTRAGSSTATUS\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_WIEDERHERST_LB`](/en/api/202604/ausloeser-nb/start-wiederherst-lb) \"\n }\n ],\n \"STATUSMITTEILUNG\": [\n {\n \"positionsdaten\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"fertigstellungsdatum\": \"\",\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/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - `LESEN_STATUSMITTEILUNG_BASIS`
  3. Message to **LF** · AS4
    **Response per decision tree** - `21039` → [E_0472](/en/referenz/202604/ebd/E_0472) · NB · Check whether the disconnection order was successful - `21039` → [E_0501](/en/referenz/202604/ebd/E_0501) · NB · Check rejection, perform clearing if necessary
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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/202604/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Flow**
  1. **Process trigger** - [`START_AUFTRAGSSTATUS`](/en/api/202604/ausloeser-nb/start-auftragsstatus) \"\n }\n ],\n \"STATUSMITTEILUNG\": [\n {\n \"positionsdaten\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"antwortstatus\": \"\",\n \"antwortstatusCodeliste\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"fertigstellungsdatum\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_AUFTRAGSSTATUS\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_WIEDERHERST_LB`](/en/api/202604/ausloeser-nb/start-wiederherst-lb) \"\n }\n ],\n \"STATUSMITTEILUNG\": [\n {\n \"positionsdaten\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"fertigstellungsdatum\": \"\",\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/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - `LESEN_STATUSMITTEILUNG_BASIS`
  3. Message to **MSB** · AS4
    **Response per decision tree** - `21039` → [E_0472](/en/referenz/202604/ebd/E_0472) · NB · Check whether the disconnection order was successful
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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/202604/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Flow**
  1. **Process trigger** - [`START_AUFTRAGSSTATUS`](/en/api/202604/ausloeser-nb/start-auftragsstatus) \"\n }\n ],\n \"STATUSMITTEILUNG\": [\n {\n \"positionsdaten\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"antwortstatus\": \"\",\n \"antwortstatusCodeliste\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"fertigstellungsdatum\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_AUFTRAGSSTATUS\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_WIEDERHERST_LB`](/en/api/202604/ausloeser-nb/start-wiederherst-lb) \"\n }\n ],\n \"STATUSMITTEILUNG\": [\n {\n \"positionsdaten\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"fertigstellungsdatum\": \"\",\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/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - `LESEN_STATUSMITTEILUNG_BASIS`
  3. Message to **ÜNB** · AS4
    **Response per decision tree** - `21039` → [E_0472](/en/referenz/202604/ebd/E_0472) · NB · Check whether the disconnection order was successful
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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_0470](/referenz/202604/ebd/E_0470) | Check disconnection order | | [E_0472](/referenz/202604/ebd/E_0472) | Check whether the disconnection order was successful | | [E_0488](/referenz/202604/ebd/E_0488) | Check request | | [E_0501](/referenz/202604/ebd/E_0501) | Check rejection, perform clearing if necessary |
## Process information Wording of the consolidated version, profile ch. 3.5.1.1, pp. 103–104.
  1. ### Preconditions - This is a consuming market location. If the consuming market location is electrically connected to one or more generating market locations in such a way that the interruption of grid connection use also affects this generating market location or these generating market locations, this UC is nevertheless applicable. - The market location to be disconnected is assigned to LF. - The market location is not already disconnected. - The market location to be disconnected is in the low voltage level. - The metering point operation is carried out at all metering locations of the market location to be disconnected by the same MSB; i.e. the MSB of the market location is the MSB of the metering location(s).
  2. ### Results - The market location is disconnected. - Billing can be carried out via the use case „Billing of another service". The costs of the reconnection are also charged to the LF that ordered the successful disconnection of the market location.
  3. ### Error case #### Result in the error case - The grid connection use via the affected market location is still possible. - The disconnection order was ended without success (reasons: e.g. market location cannot be identified on site, access to the market location not possible, passive refusal of access or active refusal of access). Note: costs incurred up to that point due to an unsuccessful interruption can be settled via the use case “Billing of another service"." - If required, the LF can restart the use case „Interruption of the grid connection use (disconnect) on instruction of the LF“, where applicable with the involvement of a bailiff. #### Error cases - This is a generating market location or a tranche. - The market location to be disconnected is not in the low voltage level. - The MSB of the market location is not the MSB of the metering locations.
  4. ### Further requirements - A disconnection of a market location is not equivalent to a decommissioning. In the event of a disconnection, MSB must continue to fulfil its obligations, in particular the transmission of values to the authorized parties. This means that MSB transmits or applies the disconnection meter reading or "zero consumption substitute values" for the period of the disconnection. - A disconnected market location remains part of the balancing. - If the disconnection of the market location is carried out with the participation of MSB, these steps take place bilaterally outside this process standardization. - The cancellation of a disconnection order is described in the use case „[Cancellation of the interruption and restoration of the grid connection use on the instruction of the LF](/en/prozessdoku/202604/NB/GPKE-Teil2-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf)“. If a disconnection order is successfully canceled, the use case „Interruption of the grid connection use (disconnect) on the instruction of the LF“ described here continues with the SD step "ref Billing of another service" so that the services incurred up to that point can be billed. - After an active refusal of access, no further disconnection attempt is made within a disconnection order. - The disconnection of a market location involving a bailiff must always be ordered separately. - If the affected market location is not in the low voltage grid and/or MSB of the market location is not at the same time MSB of all metering locations of the market location, communication takes place NON-EDIFACT. - Note: If the consuming market location is electrically connected to one or more generating market locations in such a way that the interruption of the grid connection use also affects these generating market location(s), the disconnection order of LF for the consuming market location is not to be rejected on the grounds that this prevents the feed-in of the generated electricity quantities into the grid.
  5. ### Trigger **Runs beforehand:** [Cancellation of the interruption and restoration of grid connection use on the instruction of the LF](/en/prozessdoku/202604/NB/GPKE-Teil2-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf) — these processes name the one shown here in their result.
  6. ### First message **LF** sends “Disconnection order” (step 1). From here on, it is the turn of the party involved on this page.
  7. ### Objective The grid connection use via the affected market location is no longer possible.
## 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/202604/LF/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf) — LF - [View MSB](/en/prozessdoku/202604/MSB/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf) — MSB - [View ÜNB](/en/prozessdoku/202604/UENB/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf) — ÜNB · market role UENB *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.* 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), [7](#schritt-7)