DH-121 Creating an accounting point
Event description
A DSO creates a new accounting point in Datahub.
Parties
DSO
Datahub
Time limits
Effective time of the update and its reporting |
|---|
The new accounting point must be reported as soon as the required information has been stored in the DSO’s own system. |
Start of occurrence at the earliest 3 years retroactively, at the latest current day at 00:00. |
Event processing in Datahub
Step | Description |
Connection capacity of the accounting point | Datahub calculates the connection capacity based on fuse size if connection capacity is not otherwise specified. |
Information storage
Origin of information | Information stored |
Information reported by the party | All reported information is stored in Datahub. |
Datahub stores and forwards information on a post office located in Finland in upper case, even if the post office name is reported differently to Datahub. | |
Information processed by Datahub | Connection capacity, if not specified in the message. |
Return of information
Party | Description | Message |
|---|---|---|
DSO | Notification of successful or rejected creation of an accounting point. |
Significant errors and consequences
Error | Consequence |
|---|---|
The address of the accounting point is incorrectly reported or a faulty accounting point is created (for example, the accounting point does not exist) | An agreement is made for the wrong accounting point. |
Other accounting point information is incorrectly reported | The supplier makes an agreement with the customer on wrong terms (product/price list is incorrect). |
Event cancellation
The creation of an accounting point can be cancelled with an accounting point deletion event (DH-123), provided that no other events have yet been associated with the accounting point.
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
The accounting point ID (GS1) is in the correct format. | EC.MPT.101 |
|
The notified time of entry into force of the accounting point is midnight. | EC.MPT.107 |
|
The accounting point’s code must not already be recorded in Datahub. | EC.MPT.100 |
|
The metering grid area must be recorded in the system. | EC.MGA.100 |
|
The metering grid area must belong to the reporting distribution system operator. | EC.MPT.103 |
|
The accounting point cannot be created with the status ‘Removed from use’ or ‘Deleted’. | EC.MPT.102 |
|
If the accounting point sub-type is the production unit’s own use, the accounting point type must be ‘Consumption’. | EC.MPT.148 |
|
If the accounting point type is production, the metering method must be continual metering. | EC.MPT.149 |
|
The accounting point’s creation event cannot be used to report information about a related accounting point or energy community. | EC.CPF.024 |
|
|
|
|
Please observe that the list is not complete. | ||