DH-424 Cancellation of request for disconnection

1 Event description
2 Parties
3 Time limits
4 Event processing in Datahub
5 Information storage
6 Return of information
7 Forwarding of information
8 Significant errors and consequences
9 Event cancellation
10 Validation rules

Cancellation of request for disconnection

Event description

A supplier reports a cancellation of a disconnection request it has sent earlier. The supplier requests the DSO to cancel the requested disconnection since the disconnection has been requested for the wrong accounting point or the accounting point no longer needs to be disconnected.

Parties

Supplier
Datahub
DSO
Balancing service provider

Time limits

Effective time of the update

Effective time of the update
The start of occurrence cannot be in the past.
If the supplier wants to cancel the requested disconnection on the requested disconnection date, this event is not used for the cancellation; instead, a connection request (DH-411) must be submitted.

Event processing in Datahub

Step	Description
Cancellation of a previous disconnection request	The disconnection request for the same accounting point with the same date no longer waits for the DSO to disconnect the accounting point.
Balance information update	The supplier’s balance information, which was terminated with the disconnection request, is linked to the supplier again.

Information storage

Origin of information	Information stored
Information processed by Datahub	Balance information

Return of information

Party	Description	Message

Party	Description	Message
Supplier	Notification of successful or rejected cancellation request.	ACK

Forwarding of information

Party	Description	Message

Party	Description	Message
DSO	The cancellation request is forwarded to the accounting point’s DSO.	DH-424-2
Balancing service provider	If the notification of disconnection changes a customer’s supplier information due to the updated agreement and the customer has issued an ‘Accounting point’s balance responsibility information’ authorization for the accounting point, the new balance responsibility information is forwarded to the balancing service provider. The authorization must be valid on the reporting date of the event and the validity of the changed data must overlap with the validity of the authorization.	DH-136-2

Significant errors and consequences

Error	Consequence

Error	Consequence
Cancellation is reported for the wrong disconnection request.	A customer’s electricity supply is not disconnected as requested.

Event cancellation

The event cannot be cancelled.

Validation rules

Please see Datahub Validation Rules for a more thorough list.

Rule	Error code	Note

Rule	Error code	Note
The notified disconnection time is midnight.	EC.MPT.107
The accounting point is recorded in Datahub.	EC.MPT.115
The accounting point must not have the status ‘Removed from use’ or ‘Deleted’.	EC.MPT.120
The cancellation using this message must be made no later than the day before the disconnection date.	EC.MPT.125	If the supplier wants to cancel the requested disconnection on the requested disconnection date, this event is not used for the cancellation; instead, a connection request (DH-411) must be submitted.
The status of the accounting point reported in the message must be ‘Disconnected’.	EC.MPT.143
At the accounting point, there is a waiting disconnection request from the same supplier for the same date (the cancellation disconnection date matches the original requested connection date).	EC.MPT.153	The disconnection request is considered pending as long as the DSO has not sent the DH-422 event. Delay notifications do not affect the status.
The supplier must hold a valid sales agreement for the accounting point at the moment of sending the cancellation and for the cancellable disconnection date.	EC.AGR.238
Please observe that the list is not complete.