LF (54)
E_0609 — Check deregistration
Check deregistration
| Attribute | Value |
|---|---|
| Designation | Check deregistration |
| Market role | LF |
| Regulatory determination / chapter | GPKE |
| Section | 6.4.1: AD: End of supply from NB to LF |
| Check identifiers | checked: 55007 · response: 55008, 55009 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Was it stated in the business transaction that this is a consuming market location or a dormant market location? | yes | → Step 20 | — |
| — | — | no | → Step 510 | — |
| 20 | Is this the deregistration of a market location that is to be separated out of a customer installation? Note: The transaction reason supplement states „dormant market location“. | yes | → Step 25 | — |
| — | — | no | → Step 30 | — |
| 25 | Is the market location named in the use case a „dormant market location“ of a customer installation (§ 20 para. 1d EnWG or § 10 c EEG)? | no | A01 | Cluster: Rejection The market location named in the deregistration is not a „dormant market location“ of a customer installation. |
| — | — | yes | → Step 30 | — |
| 30 | Has the end-of-supply notification already been positively confirmed for the identical deregistration date for the market location named in this business transaction? | yes | A02 | Cluster: Rejection End of supply on the deregistration date has already been confirmed |
| — | — | no | → Step 40 | — |
| 40 | Was the lead time met? Note: The maximum and the minimum lead time are to be checked. | no | A03 | Cluster: Rejection Lead time was not met |
| — | — | yes | → Step 50 | — |
| 50 | Is the transaction reason move-out due to decommissioning present? | yes | → Step 60 | — |
| — | — | no | → Step 80 | Note: One of the following transaction reasons applies: deregistration due to missing allocation authorization because of deactivation of the BKV at the NB deregistration due to missing allocation authorization because of change of ZRT |
| 60 | Does LF have information that the market location is not being/has not been decommissioned? | yes | A04 | Cluster: Rejection The LF has information that the market location is not being / has not been decommissioned. Note: The information must be described/named in the response. |
| — | — | no | → Step 130 | — |
| 80 | Is the transaction reason deregistration due to missing allocation authorization owing to change of ZRT present? | yes | → step 90 | — |
| — | — | no | → step 85 | Note: The transaction reason “deregistration due to missing allocation authorization” applies because of deactivation of the BKV at the NB. |
| 85 | Is the specified date “End of supply” the next 1st of a calendar month 00:00? | no | A05 | Cluster: Rejection The end of supply must fall on the 1st of a calendar month at 00:00. |
| — | — | yes | → Step 100 | — |
| 90 | Was the time series type at the market location concerned changed as of the transmitted end of supply to a ZRT for which, from the point of view of the LF, the NB would have to hold an allocation authorization? Notes: - There is presumably a data inconsistency regarding the allocation authorization between NB and LF. - If there is no change of the time series type as of the transmitted end of supply, the question is to be answered with yes. | yes | A06 | Cluster: Rejection There is a change to a time series type for which an allocation authorization exists from the perspective of the LF. Notes: - From the perspective of the LF, the necessary allocation authorization would have to be held by the NB. - The LF clarifies the matter with the BKV, and the latter if necessary with the NB. |
| — | — | no | → Step 130 | Note: The LF knows that the BKV has not granted the necessary allocation authorization. |
| 100 | Has the BKV carried out the deactivation of the allocation authorization for the ZRT assigned to the named market location as of the transmitted end of supply? | no | A07 | Cluster: Rejection From the point of view of the LF, the allocation authorization for the ZRT named at the market location was not deactivated. Note: The LF clarifies the matter with the BKV and the latter, where applicable, with the NB. |
| — | — | yes | → Step 120 | — |
| 120 | Is the receipt date of the deregistration after the 5th WT of the month in which the allocation authorization ends? | yes | A09 | Cluster: Rejection Deadline exceeded |
| — | — | no | → Step 130 | — |
| 130 | Has a previously unspecified error occurred? | yes | A99 | Cluster: Rejection Other Note: The identified problem must be described/named in the response. End of usability: 01.04.2027 00:00 |
| — | — | no | A10 | Cluster: Consent Consent is given to the end of supply |
| 510 | Has the end-of-supply notification already been positively confirmed for the identical deregistration date for the market location or tranche named in this business transaction? | yes | A21 | Cluster: Rejection End of supply on the deregistration date has already been confirmed |
| — | — | no | → Step 520 | — |
| 520 | Was the lead time met? Note: The maximum and the minimum lead time are to be checked. | no | A22 | Cluster: Rejection Lead time was not met |
| — | — | yes | → Step 530 | — |
| 530 | Is the transaction reason decommissioning present? | yes | → Step 540 | — |
| — | — | no | → Step 560 | Note: One of the following transaction reasons applies: deregistration due to missing allocation authorization because of deactivation of the BKV at the NB deregistration due to missing allocation authorization because of change of ZRT |
| 540 | Does LF have information that the market location or tranche is not being/has not been decommissioned? | yes | A23 | Cluster: Rejection The LF has information that the market location or tranche is not being / has not been decommissioned. Note: The information must be described/named in the response. |
| — | — | no | → Step 610 | — |
| 560 | Is the transaction reason deregistration due to missing allocation authorization owing to change of ZRT present? | yes | → Step 570 | — |
| — | — | no | → Step 565 | Note: The transaction reason “deregistration due to missing allocation authorization” applies because of deactivation of the BKV at the NB. |
| 565 | Is the specified date “End of supply” the next 1st of a calendar month 00:00? | no | A24 | Cluster: Rejection The end of supply must fall on the 1st of a calendar month at 00:00. |
| — | — | yes | → Step 580 | — |
| 570 | Was the time series type at the market location or tranche concerned changed as of the transmitted end of supply to a ZRT for which, from the point of view of the LF, the NB would have to hold an allocation authorization? Notes: - There is presumably a data inconsistency regarding the allocation authorization between NB and LF. - If there is no change of the time series type as of the transmitted end of supply, the question is to be answered with yes. | yes | A25 | Cluster: Rejection There is a change to a time series type for which an allocation authorization exists from the perspective of the LF. Notes: - From the perspective of the LF, the necessary allocation authorization would have to be held by the NB. - The LF clarifies the matter with the BKV, and the latter if necessary with the NB. |
| — | — | no | → Step 610 | Note: The LF knows that the BKV has not granted the necessary allocation authorization. |
| 580 | Has the BKV carried out the deactivation of the allocation authorization for the ZRT assigned to the named market location or tranche as of the transmitted end of supply? | no | A26 | Cluster: Rejection From the point of view of the LF, the allocation authorization for the ZRT named at the market location or tranche was not deactivated. Note: The LF clarifies the matter with the BKV and the latter, where applicable, with the NB |
| — | — | yes | → Step 600 | — |
| 600 | Is the receipt date of the deregistration after the 5th WT of the month in which the allocation authorization ends? | yes | A28 | Cluster: Rejection Deadline exceeded |
| — | — | no | → Step 610 | — |
| 610 | Has a previously unspecified error occurred? | yes | A99 | Cluster: Rejection Other Note: The identified problem must be described/named in the response. End of usability: 01.04.2027 00:00 |
| — | — | no | A29 | Cluster: Consent Consent is given to the end of supply |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A01 | Rejection | The market location named in the deregistration is not a “dormant market location” of a customer installation. | 55009 |
A02 | Rejection | End of supply as at the deregistration date has already been confirmed | 55009 |
A03 | Rejection | Lead time was not met | 55009 |
A04 | Rejection | The LF has information that the market location is not being / has not been decommissioned. Note: the information is to be described/named in the response. | 55009 |
A05 | Rejection | The end of supply must fall on the 1st of a calendar month at 00:00. | 55009 |
A06 | Rejection | A change to a time series type exists for which an allocation authorization exists from the point of view of the LF. Notes: - From the point of view of the LF, the necessary allocation authorization would have to be held by the NB. - The LF clarifies the matter with the BKV and the latter, if necessary, with the NB. | 55009 |
A07 | Rejection | From the perspective of the LF, the allocation authorization for the ZRT named at the market location has not been deactivated. Note: The LF clarifies the matter with the BKV, and the latter, if necessary, with the NB. | 55009 |
A09 | Rejection | Deadline exceeded | 55009 |
A99 (2 outputs) | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.04.2027 00:00 | 55009 |
A10 | Consent | End of supply is consented to | 55008 |
A21 | Rejection | End of supply as at the deregistration date has already been confirmed | 55009 |
A22 | Rejection | Lead time was not met | 55009 |
A23 | Rejection | The LF has information that the market location or tranche is not being / has not been decommissioned. Note: the information is to be described/named in the response. | 55009 |
A24 | Rejection | The end of supply must fall on the 1st of a calendar month at 00:00. | 55009 |
A25 | Rejection | A change to a time series type exists for which an allocation authorization exists from the point of view of the LF. Notes: - From the point of view of the LF, the necessary allocation authorization would have to be held by the NB. - The LF clarifies the matter with the BKV and the latter, if necessary, with the NB. | 55009 |
A26 | Rejection | From the perspective of the LF, the allocation authorization for the ZRT named at the market location or tranche has not been deactivated. Note: The LF clarifies the matter with the BKV, and the latter, if necessary, with the NB | 55009 |
A28 | Rejection | Deadline exceeded | 55009 |
A29 | Consent | End of supply is consented to | 55008 |
Notes on this page
Role of the numbers: »response« are the check identifiers that list this tree in the ebd_code column of the check identifier table (knowledge-collection · FV 202610); »checked« is the difference set to it from the return path of the process steps. The »response check identifier« column of the result codes assigns a cluster only because this tree carries exactly one checked message and exactly one response per pole; their pole comes from the use case title of the response.
Consistent with the generated process
All 18 result codes of the decision tree are contained in the generated process E_0609.bpmn.