Contract termination — LFA view
Process flow from the perspective of the LF (LFA)
Process steps
Contract termination
LF (corresponds to LFA) LF (corresponds to LFN)G_0005_G_0006 Rejection / consent to contract termination4401744018Check identifiers
- 44016 — Contract termination with the old supplier · AS4
Flow
Message from LF (corresponds to LFN) · AS4
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Load data for the check
- Read energy supply contract
GET /getEnergySupplyContractBasic - Read market location
GET /getMarketLocationBasic
- Read energy supply contract
Decision tree
44016→G_0005_G_0006— Rejection / consent to contract termination
Trigger follow-up process
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response
LF (corresponds to LFA) LF (corresponds to LFN)44016Check identifiers
Flow
Triggered by incoming message
- 44016 — Contract termination with the old supplier
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read energy supply contract
GET /getEnergySupplyContractBasic - Read market location
GET /getMarketLocationBasic - Read balancing
GET /getAccountingBasic
- Read energy supply contract
Message to LF (corresponds to LFN) · AS4
Response per decision tree
44018,44017→ E_3001 · Check contract termination of gas supply contract
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Decision trees of this process
| EBD | Name |
|---|---|
| E_3001 | Check contract termination of gas supply contract |
Process information
Trigger
Runs beforehand: Determination of the MaLo ID of the market location — these processes name the one shown here in their result.
First message
LF (corresponds to LFN) sends “Contract termination” (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 LFN — the receiving supplier · market role LF
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.