DH-127 Deleting an accounting point relation
Event description
The DSO reports the termination of an accounting point relation.
Parties
DSO
Datahub
Supplier
Third Party
Time limits
Effective time of the update | Notes/Exceptions |
|---|---|
The information must be reported as soon as the DSO makes the change in its own system. |
|
Start of occurrence can be 90 days in past at the earliest or maximum 90 days in the future. | When the change allowing the reporting of related accounting point information retroactively is implemented, retroactive corrections to related accounting point information will be permitted from 1.1.2023, for a separately defined period, after which the normal time limits will be applied. The operator will also have the possibility to allow retroactive corrections in exceptional situations beyond the normal time limits. |
Event processing in Datahub
Step | Description |
Removal of accounting points from netting calculation | Datahub removes the accounting points from netting calculations. |
Retroactive calculation during correction processes | If related accounting point information is corrected retroactively so that the netting situation of the accounting points changes, Datahub will perform the calculations for the accounting points in connection with the update. See detailed description. |
Information storage
Origin of information | Information stored |
Information reported by the party | All reported information is stored in Datahub. |
Information processed by Datahub | Information on the removal of accounting points from netting calculation and, where applicable, the results of calculation performed based on the reported event. |
Return of information
Party | Description | Message |
|---|---|---|
DSO | Notification of a successful or rejected termination of an accounting point relation |
Forwarding of information
Party | Description | Message |
|---|---|---|
Supplier | When the relation information update is reported for the future (i.e., start of occurrence is in the future), the updated accounting point information is reported to the supplier associated with the accounting points on the reported start of occurrence. In case of a retroactive update (i.e., start of occurrence is not in the future), the updated accounting point information is not reported to the supplier. Note: Possible (new) notifications will be added in a later version. | |
Third party | When the relation information update is reported for the future (i.e., start of occurrence is in the future), the updated accounting point information is reported to the third parties associated with the accounting points with consideration to the parties' rights to information on the reported start of occurrence. In case of a retroactive update (i.e., start of occurrence is not in the future), the updated accounting point information is not reported to third parties. Note: Possible (new) notifications will be added in a later version. |
Significant errors and consequences
Error | Consequence |
|---|---|
Information is incorrectly reported | Datahub performs the netting calculations with wrong information. If there is a need to correct the accounting point relation information for an accounting point that has been mistakenly removed from use, the DSO can request the Datahub operator to restore the accounting point back to an active state. |
Event cancellation
Information is corrected by creating a new accounting point relation (DH-126).
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
The accounting points must exist in Datahub on the effective date of the deleting of relation. | EC.MPT.108/ |
|
The metering grid area must belong to the reporting distribution system operator. | EC.MPT.103 |
|
The accounting points must be part of the same reported metering grid area. | EC.MPT.157 |
|
The reported accounting points must have information about parallelism (related accounting points) at the moment the notification enters into force. | EC.MPT.173 |
|
The reported consumption accounting point cannot be part of an energy community whose surplus allocation method is ‘SMB’. | EC.MPT.172 |
|
|
|
|
Please observe that the list is not complete. | ||