Start of supply — NB view
Process flow from the perspective of the NB
Process steps
Registration
NB LF (corresponds to LFN)G_0011_G_0012 Start of supply NN from the LF (Gas)G_0012_BeendigungDerZuordnung Check whether a request to terminate the assignment is required (Gas)4400244003Check identifiers
- 44001 — NN registration · 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 balancing
GET /getAccountingBasic - Read metering location
GET /getMeterLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read balancing
Decision tree
44001→G_0011_G_0012— Start of supply NN from the LF (Gas)44001→G_0012_BeendigungDerZuordnung— Check whether a request for termination of the assignment is required (Gas)
Load data for processing
- Read market location
GET /getMarketLocationBasic
- Read market location
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.
Information about existing assignment
NB LF (corresponds to LFN)Check identifiers
- 44036 — Information notification about existing assignment · AS4
Flow
Message to LF (corresponds to LFN) · 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
Deregistration request
NB LF (corresponds to LFA)Check identifiers
- 44010 — Deregistration request from the NB · AS4
Flow
Message to LF (corresponds to LFA) · AS4
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend once the message has been created.
- Transaction created — Create process data
Response to the deregistration request
NB LF (corresponds to LFA)Z3344037Check identifiers
Flow
Message from LF (corresponds to LFA) · AS4
Response per decision tree
44011,44012→ E_3020 · Check deregistration
APERAK checks
44011,44012→Z33
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
Trigger follow-up process
- 44037 — Information notification on termination of the assignment
After processing, the MACO APP starts this follow-up process itself.
Response to registration
NB LF (corresponds to LFN)44001Check identifiers
Flow
Triggered by incoming message
- 44001 — NN registration
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 energy supply contract
GET /getEnergySupplyContractBasic - Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic - Read meter
GET /getCounterBasic
- Read balancing
Message to LF (corresponds to LFN) · 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
Notification of the termination of the assignment
NB LF (corresponds to LFA)44011Check identifiers
- 44037 — Information notification on termination of the assignment · AS4
Flow
Triggered by incoming message
- 44011 — Confirmation of deregistration request
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to LF (corresponds to LFA) · 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 the cancellation of a future assignment
NB LF (future LF)Check identifiers
- 44038 — Information notification on revocation of a future assignment · AS4
Flow
Prozessauslöser
START_AUFH_ZUK_ZUORDNUNGThe backend triggers this step with this event.
Message to LF (future LF) · 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
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
LF (corresponds to LFN) sends “Registration” (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 LFA — the transferring supplier · market role LF
- View LFN — the receiving supplier · market role LF
- View LFZ — future 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.
The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists.
Applies to: 4
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.