# Termination of the subscription to the market-location-specific allocation list gas — LF view ## Process flow from the perspective of the LF \nSystem diagram: Beendigung des Abonnements für die marktlokationsscharfe Allokationsliste\nGas — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Beendigung Abo\n\nNB\n\nAS4\n17110\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Beendigung des Abonnements für die marktlokationsscharfe Allokationsliste\nGas — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\n1. Beendigung Abo\nAS4 · PI 17110\n\nUpdate transaction\nUpdate process data\n"} titel="LF" /> ## Process steps ### Termination of subscription
**Check identifiers** - [17110](/en/schnittstellen/202604/pruefi/ORDERS/PI_17110) — Request for the allocation list · AS4
**Flow**
  1. Message to **NB** · AS4
  2. **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.
## Process information
  1. ### First message The party involved on this page is itself the sender of: „Termination of subscription“ to **NB** (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 NB](/en/prozessdoku/202604/NB/prozesse-zur-ermittlung-und-abrechnung-von-mehr-mindermengen-strom-und-gas-beendigung-des-abonnements-fur-die-marktlokationsscharfe-allokationsliste-gas) — NB *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 source does not yet name the event that triggers these steps. Applies to: [1](#schritt-1) 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: [1](#schritt-1)