Start of supply — LFN view
Process flow from the perspective of the LF (LFN)
Process steps
Registration
LF (corresponds to LFN) NBCheck identifiers
- 44001 — NN registration · AS4
Flow
Prozessauslöser
START_LIEFERBEGINNThe backend triggers this step with this event.
Message to NB · AS4
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
Information about existing assignment
LF (corresponds to LFN) NBZ33Check identifiers
- 44036 — Information notification about existing assignment · AS4
Flow
Message from NB · AS4
APERAK checks
44036→Z33— APERAK check: Is referenced message known ?
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
3 Deregistration request
NB LF (corresponds to LFA)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 44010 — Deregistration request from the NB · AS4
Response to registration
LF (corresponds to LFN) NBZ33Check identifiers
Flow
Message from NB · AS4
APERAK checks
44003,44002→Z33— APERAK check: Is referenced message known ?
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
6 Notification of the termination of the assignment
NB LF (corresponds to LFA)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 44037 — Information notification on termination of the assignment · AS4
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_3005 | Check whether the registration can be rejected directly |
| E_3007 | Check start of supply |
| E_3020 | Check deregistration |
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
The party involved on this page is itself the sender of: „Registration“ 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 LFA — the transferring 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.