# Cancellation of the interruption and restoration of grid connection use at the instruction of LF — View NB ## Process flow from the perspective of the NB \nSystem diagram: Stornieren der Unterbrechung und Wiederherstellung der Anschlussnutzung auf\nAnweisung des LF — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Stornierung\n\nLF\n\nAS4\n39000\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nLoad data for the check\n\n\nMarktlokation lesen\n\nAPI\n\nEBD check: E_1006\nStornierung prüfen (Basiert\nauf Strom EBD:\nE_0468_Stornierung prüfen)\n\n\nTrigger follow-up process:\n19128, 19129, 39001\n\n\nTriggered by incoming\nmessage: 39000\n\n\n2. Antwort auf Stornierung\n\n\nLF\n\nAS4\n19128, 19129\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nTriggered by incoming\nmessage: 39000\n\n\n3. Weiterleitung der\nStornierung\n\n\nMSB\n\nAS4\n39001\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Stornieren der Unterbrechung und Wiederherstellung der Anschlussnutzung auf\nAnweisung des LF — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nMSB\n\n\n1. Stornierung\nAS4 · PI 39000\n\nCreate transaction\nCreate process data\n\n2. Antwort auf Stornierung\nAS4 · PI 19128, 19129 · E_1006\nE_1006 — Stornierung prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Weiterleitung der Stornierung\nAS4 · PI 39001\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Cancellation
**Check identifiers** - [39000](/en/schnittstellen/202604/pruefi/ORDCHG/PI_39000) — Cancellation of disconnection/reconnection order · AS4
**Flow**
  1. Message from **LF** · AS4
  2. **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.
  3. **Load data for the check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  4. **Decision tree** - `39000` → [E_1006](/en/referenz/202604/ebd/E_1006) — Check cancellation (Based on electricity EBD: E_0468_Check cancellation)
  5. **Trigger follow-up process** - [19128](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19128) — Confirmation of cancellation of disconnection/reconnection order - [19129](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19129) — Rejection of cancellation of disconnection/reconnection order - [39001](/en/schnittstellen/202604/pruefi/ORDCHG/PI_39001) — Forwarding of the cancellation After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
### 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. **Triggered by incoming message** - [39000](/en/schnittstellen/202604/pruefi/ORDCHG/PI_39000) — Cancellation of disconnection/reconnection 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** - `19128`, `19129` → [E_1006](/en/referenz/202604/ebd/E_1006) · NB · Check cancellation (Based on electricity EBD: E_0468_Check cancellation)
  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.
### Forwarding of the cancellation
**Check identifiers** - [39001](/en/schnittstellen/202604/pruefi/ORDCHG/PI_39001) — Forwarding of the cancellation · AS4
**Flow**
  1. **Triggered by incoming message** - [39000](/en/schnittstellen/202604/pruefi/ORDCHG/PI_39000) — Cancellation of disconnection/reconnection order The MACO APP sends this message itself, as a follow-up process after this incoming message.
  2. Message to **MSB** · AS4
  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.
Decision trees of this process | EBD | Name | |---|---| | [E_1006](/referenz/202604/ebd/E_1006) | Check cancellation (Based on electricity EBD: E_0468_Check cancellation) |
## Process information
  1. ### First message **LF** sends “Cancellation” (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/202604/LF/awh-sperrprozesse-gas-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf) — LF - [View MSB](/en/prozessdoku/202604/MSB/awh-sperrprozesse-gas-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-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 process begins for the own role with their message, so the transaction is created. Applies to: [1](#schritt-1)