# Cancellation of the interruption and restoration of grid connection use at the instruction of LF — View LF The LF sends - a cancellation of the order for the disconnection (case a) or - a cancellation of the order for the reconnection (case b) of a market location, so that - grid connection use at the market location remains possible (successful cancellation of case a) or - the market location remains disconnected (successful cancellation of case b). If the MSB was already involved, it must be informed as well. ## Process flow from the perspective of the LF \nSystem diagram: Stornieren der Unterbrechung und Wiederherstellung der Anschlussnutzung 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. Stornierung\n\n\nNB\n\nAS4\n39000\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort auf Stornierung\n\n\nNB\n\nAS4\n19128, 19129\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Stornieren der Unterbrechung und Wiederherstellung der Anschlussnutzung 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. Stornierung\nAS4 · PI 39000\n\nUpdate transaction\nUpdate process data\n\n2. Antwort auf Stornierung\nAS4 · PI 19128, 19129 · E_0468\nE_0468 — Stornierung prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Weiterleitung der Stornierung\nAS4 · PI 39001\n"} titel="LF" /> ## Process steps ### Cancellation
**Check identifiers** - [39000](/en/schnittstellen/202604/pruefi/ORDCHG/PI_39000) — Cancellation of disconnection/reconnection order · AS4
**Flow**
  1. **Process trigger** - [`START_STORNO_AUFTRAG`](/en/api/202604/ausloeser-lf/start-storno-auftrag) \"\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_STORNO_AUFTRAG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_STORNO_SE_AUFTRAG`](/en/api/202604/ausloeser-lf/start-storno-se-auftrag) \"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"auftragsReferenz\": \"\",\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_STORNO_SE_AUFTRAG\",\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/202604/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 cancellation
**Check identifiers** - [19128](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19128) — Confirmation of cancellation of disconnection/reconnection order · AS4 - [19129](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19129) — Rejection of cancellation of disconnection/reconnection order · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `19128`, `19129` → [E_0468](/en/referenz/202604/ebd/E_0468) · NB · Check cancellation
  2. **APERAK checks** - `19128`, `19129` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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.
### Forwarding of the cancellation This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [39001](/en/schnittstellen/202604/pruefi/ORDCHG/PI_39001) — Forwarding of the cancellation · AS4
Decision trees of this process | EBD | Name | |---|---| | [E_0468](/referenz/202604/ebd/E_0468) | Check cancellation |
## Process information Wording of the consolidated version, profile ch. 3.5.3.1, pp. 111–112.
  1. ### Preconditions - The affected market location is assigned to LF. - In accordance with the grid usage contract (supplier framework agreement) concluded between LF and NB, the LF has instructed the NB to have the grid connection use at the named market location of the AN supplied by the LF - to interrupt (case a: use case „[Interruption of grid connection use (disconnect) at the instruction of the LF](/en/prozessdoku/202604/LF/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf)“) or - to reconnect (case b: use case „[Restoration of grid connection use (reconnect) at the instruction of the LF](/en/prozessdoku/202604/LF/GPKE-Teil2-wiederherstellung-der-anschlussnutzung-entsperren-auf-anweisung-des-lf)“). - It is therefore a consuming market location. - The reason for the disconnection order or reconnection order no longer applies, e.g. because the customer has settled the claim of the LF or the LF has accepted the AN's objection. - The interruption of the grid connection use (case a) or restoration of the grid connection use (case b) via the affected market location has not yet taken place.
  2. ### Results - The grid connection use via the affected market location is still possible (successful cancellation of case a: disconnection order was successfully canceled), or - the market location remains disconnected (successful cancellation of case b: the reconnection order was cancelled successfully).
  3. ### Error case #### Result in the error case - If the cancellation of case a is unsuccessful: - In order to lift the disconnection of the market location, LF starts the use case “[Restoration of grid connection use (reconnect) on the instruction of LF](/en/prozessdoku/202604/LF/GPKE-Teil2-wiederherstellung-der-anschlussnutzung-entsperren-auf-anweisung-des-lf)” (case b). - If the cancellation of case b is unsuccessful: - For the disconnection of the market location, LF starts the use case „[Interruption of grid connection use (disconnect) on the instruction of LF](/en/prozessdoku/202604/LF/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf)“ (case a).
  4. ### Further requirements - The cancellation of an order can be carried out by the LF at any time, irrespective of the status at the NB, as long as the disconnection order or reconnection order from the NB has not yet been executed at the AN. - If a disconnection order is successfully cancelled, the use case “[Interruption of grid connection use (disconnect) on the instruction of the LF](/en/prozessdoku/202604/LF/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf)” is continued with the SD step "ref Billing of another service" in order to bill any services incurred up to that point.
  5. ### First message The party involved on this page is itself the sender of: „Cancellation“ to **NB** (step 1).
  6. ### Objective The LF cancels an order for the disconnection or reconnection of a market location before it has been carried out by the NB.
## 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/GPKE-Teil2-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf) — NB - [View MSB](/en/prozessdoku/202604/MSB/GPKE-Teil2-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf) — MSB *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.*