# End of supply from NB to LF — NB view ## Process flow from the perspective of the NB \nSystem diagram: Lieferende von NB an LF — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_LIEFERENDE\n\nAPI\n\n1. Abmeldung\n\n\nLF\n\nAS4\n44007\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort auf Abmeldung\n\n\nLF\n\nAS4\n44008, 44009\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Lieferende von NB an LF — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nSTART_LIEFERENDE\nTrigger event\n\n1. Abmeldung\nAS4 · PI 44007\n\nUpdate transaction\nUpdate process data\n\n2. Antwort auf Abmeldung\nAS4 · PI 44008, 44009 · E_3002\nE_3002 — Abmeldung prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Deregistration
**Check identifiers** - [44007](/en/schnittstellen/202604/pruefi/UTILMD_GAS/PI_44007) — NN deregistration from NB · AS4
**Flow**
  1. **Prozessauslöser** [`START_LIEFERENDE`](/en/api/202604/ausloeser-nb/start-lieferende) \"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"freitext\": \"\",\n \"kategorie\": \"\",\n \"sparte\": \"\",\n \"transaktionsgrund\": \"\",\n \"transaktionsgrundergaenzung\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_LIEFERENDE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **LF** · 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.
### Response to deregistration
**Check identifiers** - [44008](/en/schnittstellen/202604/pruefi/UTILMD_GAS/PI_44008) — Confirmation of deregistration from NB · AS4 - [44009](/en/schnittstellen/202604/pruefi/UTILMD_GAS/PI_44009) — Rejection of deregistration from NB · AS4
**Flow**
  1. Message from **LF** · AS4
    **Response per decision tree** - `44008`, `44009` → [E_3002](/en/referenz/202604/ebd/E_3002) · Check deregistration
  2. **APERAK checks** - `44008`, `44009` → `Z33`
  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 with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_3002](/referenz/202604/ebd/E_3002) | Check deregistration |
## Process information
  1. ### Trigger **Runs beforehand:** [End of supply from LF to NB](/en/prozessdoku/202604/NB/GPKE-Teil2-lieferende-von-lf-an-nb) — these processes name the one shown here in their result.
  2. ### First message The party involved on this page sends this itself: “Deregistration” to **LF** (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 LF](/en/prozessdoku/202604/LF/geli-gas-2-0-lieferende-von-nb-an-lf) — LF *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. :::