# GeLi_Gas 2.0 ch. 1.6.1 Inventory lists — NB view ## Process flow from the perspective of the NB \nSystem diagram: GeLi_Gas 2.0 Kap. 1.6.1 Bestandslisten — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\nTriggered by incoming\nmessage: 44020\n\nProcess trigger received\n\n\nSTART_VERSAND_BESTAND\nSLISTE_GAS\n\nAPI\n\n\n\nLF\n\nAS4\n44019, 44020, 44021\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: GeLi_Gas 2.0 Kap. 1.6.1 Bestandslisten — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nSTART_VERSAND_BESTANDSLISTE_GAS\nTrigger event\n\n\nAS4 · PI 44019, 44020, 44021\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Inventory list of assigned market locations · Change notification for the inventory list · Response to change notification for the inventory list
**Check identifiers** - [44019](/en/schnittstellen/202604/pruefi/UTILMD_GAS/PI_44019) — Inventory list of assigned market locations · AS4 - [44020](/en/schnittstellen/202604/pruefi/UTILMD_GAS/PI_44020) — Change notification for the inventory list · AS4 - [44021](/en/schnittstellen/202604/pruefi/UTILMD_GAS/PI_44021) — Response to change notification for the inventory list · AS4
**Flow**
  1. **Triggered by incoming message** - [44020](/en/schnittstellen/202604/pruefi/UTILMD_GAS/PI_44020) — Change notification for the inventory list The MACO APP sends this message itself, as a follow-up process after this incoming message. In addition, the backend can trigger this step with an event — the next item.
  2. **Prozessauslöser** [`START_VERSAND_BESTANDSLISTE_GAS`](/en/api/202604/ausloeser-nb/start-versand-bestandsliste-gas) \"\n ],\n \"prognosegrundlage\": \"\"\n }\n ],\n \"MARKTLOKATION\": [\n {\n \"marktlokationsId\": \"\"\n }\n ],\n \"NETZNUTZUNGSVERTRAG\": [\n {\n \"vertragskonditionen\": {\n \"haushaltskunde\": \"\",\n \"netznutzungsvertrag\": \"\",\n \"netznutzungszahler\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"gueltigAb\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_BESTANDSLISTE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  3. Message to **LF** · AS4
  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.
## Process information
  1. ### First message The party involved on this page is itself the sender: “” to **LF** (the first step).
## 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-geli-gas-2-0-kap-1-6-1-bestandslisten) — 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. ::: The source does not name this step; the heading names the use cases of its messages. Applies to: [—](#schritt-ohne-nr-0)