End of supply from NB to LF — LF view
The NB announces to the LF the termination of the assignment of the LF to the market location or tranche. In the course of the process
- the NB terminates the assignment of the MSB to the market location or metering location upon decommissioning of the market location.
- in the event of a decommissioning of the market location, the NB cancels
- where applicable, the assignment of the LFZ to the market location or tranche.
- where applicable, the assignment of the MSBZ to the market location or metering location.
Process flow from the perspective of the LF
Process steps
Announcement of the termination of the assignment of the LF to the market location or tranche
LF NBZ10Z44E_0609 Check deregistration5500855009Check identifiers
- 55007 — Deregistration / termination of the assignment · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read tranche
GET /getTrancheBasic
- Read market location
APERAK checks
55007→Z10— APERAK check: Is location known ?55007→Z44— APERAK check: Does object property match?
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 energy supply contract
GET /getEnergySupplyContractBasic - Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic - Read tranche
GET /getTrancheBasic
- Read balancing
Decision tree
55007→ E_0609 — Check deregistration
Load data for processing
- Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- 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.
Response to announcement of the termination of the assignment of the LF to the market location or tranche
LF NB55007Flow
Triggered by incoming message
- 55007 — Deregistration / termination of the assignment
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to NB · AS4
Response per decision tree
55008,55009→ E_0609 · LF · 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
Termination of the assignment of the LF to the market location or tranche due to missing response
LF NBZ10Z44E_0609 Check deregistration5500855009Check identifiers
- 55007 — Deregistration / termination of the assignment · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read tranche
GET /getTrancheBasic
- Read market location
APERAK checks
55007→Z10— APERAK check: Is location known ?55007→Z44— APERAK check: Does object property match?
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 energy supply contract
GET /getEnergySupplyContractBasic - Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic - Read tranche
GET /getTrancheBasic
- Read balancing
Decision tree
55007→ E_0609 — Check deregistration
Load data for processing
- Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- 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.
8 Cancellation of the assignment of the LFZ to the market location or tranche
NB LFZ
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55038 — Cancellation of a fut. assignment · AS4
11 Termination of the assignment of the MSB to the market location or metering location
NB MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55611 — Termination of the assignment · AS4
13 Cancellation of the assignment of the MSBZ to the market location or metering location
NB MSBZ
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55611 — Termination of the assignment · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_0609 | Check deregistration |
Process information
Wording of the consolidated version, profile ch. 2.5.2.1, pp. 57–58.
Preconditions
- In the case of a consuming market location: LF is assigned to the market location.
- In the case of a generating market location or a tranche: LF is assigned to the market location or tranche. The following cases are possible:
- Termination of the assignment of the LF to a market location
- Termination of the assignment of the LF to a tranche of a market location
- Termination of the assignment of the LF to all tranches of a market location. The use case “End of supply from NB to LF” must be carried out separately for each tranche.
Results
- In the case of a consuming market location:
- The NB executes the use cases „Billing data grid usage settlement“ and „Billing data balancing group settlement“.
- Where applicable, the NB executes the use case „Beginning of the replacement supply / default supply“.
- In the case of decommissioning: If the market location is assigned to Model 2, NB ends the metering point for NGZ.
- In the case of a generating market location or a tranche:
- The NB executes the use case „Billing data balancing group settlement“.
- Where applicable, the NB executes the use case „Establishing a 100% LF assignment to a generating market location“.
- In the case of the decommissioning of a market location: If the location bundle is not decommissioned, NB informs the market partners of the locations that remain active about the change of the location bundle with the use case "master data change" (here: “Master data change originating from NB (responsible)”) (GPKE Part 4).
- In the case of a consuming market location:
Error case
Result in the error case
The LF remains assigned to the market location or tranche.
Further requirements
- Note: A market location that cannot be assigned to any LF and for which a statutory basic or substitute supply obligation under § 36 and § 38 EnWG may exist is assigned to the E/G by NB via the use case “Start of replacement supply / default supply”.
- If, as a result of the termination of the assignment, a market location can in future be assigned neither to the E/G nor to a contractually designated replacement supplier or any other LF, NB must interrupt the grid connection use at the market location.
Trigger
- Decommissioning of a market location
- the use case „Deactivation of an allocation authorization of the BKV at the NB“ has been carried out and, for the affected market location or tranche, there is no assignment to a BK with an active allocation authorization for the time period immediately following the deactivation
- for the market location, the time series type has changed as of the stated point in time, and no valid allocation authorization exists for that type
Runs beforehand: End of supply from LF to NB — these processes name the one shown here in their result.
First message
NB sends “Announcement of the end of the assignment of the LF to the market location or tranche” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The assignment of the LF to the market location or tranche has ended.
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 LFZ — future supplier · market role LF
- View NB — NB
- View MSB — MSB
- View MSBZ — future metering point operator · market role MSB
Notes on this page
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. The numbers are those of the source; where one is missing, it is missing there.