Start of supply — LFA view
Process flow from the perspective of the LF (LFA)
Process steps
1 Registration
LF (corresponds to LFN) NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 44001 — NN registration · AS4
2 Information about existing assignment
NB LF (corresponds to LFN)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 44036 — Information notification about existing assignment · AS4
Deregistration request
LF (corresponds to LFA) NBZ10Z17Z18G_0009_G_0010 Rejection / confirmation of deregistration request4401144012Check identifiers
- 44010 — Deregistration request from the NB · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
44010→Z10— APERAK check: Is location known ?44010→Z1744010→Z18
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 grid usage contract
GET /getGridUsageContractBasic
- Read energy supply contract
Decision tree
44010→G_0009_G_0010— Rejection / confirmation of deregistration request
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 to the deregistration request
LF (corresponds to LFA) NB44010Check identifiers
Flow
Triggered by incoming message
- 44010 — Deregistration request from the NB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read balancing
GET /getAccountingBasic - Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read balancing
Message to NB · AS4
Response per decision tree
44011,44012→ E_3020 · Check deregistration
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
5 Response to registration
NB LF (corresponds to LFN)
This step runs between other market partners and is not relevant for this view.
Check identifiers
Notification of the termination of the assignment
LF (corresponds to LFA) NBZ10Z17Z18Check identifiers
- 44037 — Information notification on termination of the assignment · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
44037→Z10— APERAK check: Is location known ?44037→Z1744037→Z18
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
7 Information about the cancellation of a future assignment
NB LF (future LF)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 44038 — Information notification on revocation of a future assignment · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_3020 | Check deregistration |
| E_3005 | Check whether the registration can be rejected directly |
| E_3007 | Check start of supply |
Process information
Trigger
Runs beforehand: Billing data for grid usage settlement, Determination of the MaLo ID of the market location, Creation — these processes name the one shown here in their result.
First message
NB sends “Deregistration request” (Step 3). From here on, the party involved on this page takes its turn.
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
- View LFZ — future supplier · market role LF
- 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.
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.