GeLi_Gas 2.0 ch. 1.6.1 Inventory lists — LF view
Process flow from the perspective of the LF
Process steps
Inventory list of assigned market locations · Change notification for the inventory list · Response to change notification for the inventory list
LF NBZ10Z17Z18Z33E_BestListe Check inventory list44020Check identifiers
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
44019→Z10— APERAK check: Is location known ?44019→Z1744019→Z1844021→Z33— APERAK check: Is referenced message known ?
Write endpoint
44019,44021→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Write endpoint
44020→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Load data for the check
- Read balancing
GET /getAccountingBasic - Read energy supply contract
GET /getEnergySupplyContractBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read balancing
Decision tree
44019→E_BestListe— Check inventory list
Load data for processing
- Read balancing
GET /getAccountingBasic - Read energy supply contract
GET /getEnergySupplyContractBasic - Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read balancing
Trigger follow-up process
- 44020 — Change notification for the inventory list
After processing, the MACO APP starts this follow-up process itself.
Process information
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 — NB
Notes on this page
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.
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: —
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: —
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: —