DH-321-1 Sales agreement information update
Message DH-321-1 is of message type F04.
Message payload includes the following information:
Information field | Level | Necessity | Field content | Note |
|---|---|---|---|---|
Payload | 1 | 1..1 |
|
|
Start of occurrence | 2 | 1..1 |
| Start of occurrence in accordance with the business process specifications. Agreement start time must be midnight. |
Accounting point data | 2 | 1..1 |
| This information is not updated in this event, it is used to identify the agreement to be updated. |
Accounting point identification | 3 | 1..1 |
| This information is not updated in this event, it is used to identify the agreement to be updated. |
Area information | 2 | 1..1 |
| This information is not updated in this event, it is used to identify the agreement to be updated. |
Metering grid area identification | 3 | 1..1 |
| This information is not updated in this event, it is used to identify the agreement to be updated. |
Agreement information | 2 | 1..1 |
|
|
Contact method | 3 | 1..1 |
| If the contact method for the agreement is electronic, then at least one of the customers must have an email address registered in Datahub. |
Agreement identification | 3 | 1..1 |
| This information is not updated in this event, it is used to identify the agreement to be updated. |
Agreement type | 3 | 1..1 | Sales agreement | This information is not updated in this event, it is used to identify the agreement to be updated. |
Delivery agreement | 3 | 1..1 |
| This information is not updated in this event, it is used to identify the agreement to be updated. |
Fixed-term agreement | 3 | 1..1 | Yes/No |
|
Fixed-term start date | 3 | 0..1 |
| Fixed-term agreement start time must be midnight. Mandatory, if fixed-term agreement. Not allowed if agreement is not fixed term. "Fixed-term start date" must be the same or later than "Agreement start date". "Fixed-term start date" must be earlier than "Agreement end date". "Fixed-term start date" can be at most 3.5 years in the past or 90 days in the future. Updated "Fixed-term start date" must be later than the original "Fixed-term start date". "Fixed-term end date" must be later than "Fixed-term start date". "Fixed-term end date" must be the same or earlier than "Agreement end date". Note: No validations are used for the fixed-term dates if the update does not affect the dates. |
Fixed-term end date | 3 | 0..1 |
| Fixed-term agreement end time must be midnight. Mandatory, if fixed-term agreement. Not allowed if agreement is not fixed term. "Fixed-term start date" must be the same or later than "Agreement start date". "Fixed-term start date" must be earlier than "Agreement end date". "Fixed-term start date" can be at most 3.5 years in the past or 90 days in the future. Updated "Fixed-term start date" must be later than the original "Fixed-term start date". "Fixed-term end date" must be later than "Fixed-term start date". "Fixed-term end date" must be the same or earlier than "Agreement end date". Note: No validations are used for the fixed-term dates if the update does not affect the dates. |
Invoicing method | 3 | 1..1 |
| If the invoicing method is not “Separate invoicing”, the DSO for the accounting point must have “Combined invoicing” set to yes. |
Special termination clause | 3 | 1..1 | Yes/No | If the contact method of the agreement is electronic, then at least one of the customers must have an email address registered in Datahub. Special termination clause can only be reported for a company customer. |
Special termination period | 3 | 0..1 | Special termination period in days | If an agreement has a special termination clause, either the notice period in days or the entire notice period must be specified in the agreement. The notice period specifies the time period during which the agreement may be terminated. If a notice period is used, the supplier must ensure that it is updated in the agreement. |
Notice period | 3 | 0..1 |
| If an agreement has a special termination clause, either the notice period in days or the entire notice period must be specified in the agreement. The notice period specifies the time period during which the agreement may be terminated. If a notice period is used, the supplier must ensure that it is updated in the agreement. |
Termination period start date | 4 | 0..1 |
| A special termination period’s start time must be midnight. If an agreement has a special termination clause, either the notice period in days or the entire notice period must be specified in the agreement. The notice period specifies the time period during which the agreement may be terminated. If a notice period is used, the supplier must ensure that it is updated in the agreement. |
Termination period end date | 4 | 0..1 |
| A special termination period’s end time must be after the termination period’s start date and at midnight. If an agreement has a special termination clause, either the notice period in days or the entire notice period must be specified in the agreement. The notice period specifies the time period during which the agreement may be terminated. If a notice period is used, the supplier must ensure that it is updated in the agreement. |
Interruption critical | 3 | 1..1 | Yes/No |
|
Invoicing channel | 3 | 1..1 |
|
|
Product data | 3 | 0..n |
| If a product is reported for an agreement, the product must be in Datahub, be valid at the start date of the agreement and belong to the party reporting the agreement. |
Product code | 4 | 1..1 |
|
|
Customer note | 3 | 0..1 |
|
|
Contact person | 3 | 0..n |
| If the customer of the agreement is of type company, at least one contact person must be reported. Contact persons are persons that the parties need in customer service situations, and they may differ between sales and grid agreements. There cannot be multiple contact persons with the same contact person type. For each contact person at least one of the name attributes must be reported. The parties may have their own contact persons, but only those that the party deems necessary to pass on to the other party (from the supplier to the DSO or from the DSO to the supplier) are reported to Datahub. |
Contact person type | 4 | 1..1 |
|
|
Given name | 4 | 0..1 |
|
|
Family name | 4 | 0..1 |
|
|
Other name | 4 | 0..1 |
|
|
Contact information | 4 | 1..2 |
| The reported telephone number or email address must be in the correct format (see Datahub Datastandard). The information must be the customer's actual contact information through which the customer can be reached if necessary. Contact information should be left blank if it is not known. |
Contact information type | 5 | 1..1 |
|
|
Telephone number/Email address | 5 | 1..1 |
| A phone number must start with a plus '+'. A phone number may not contain spaces. The country code ‘+358’ may not be followed by the number zero. |
Postal invoicing address | 3 | 1..1 |
| Address information must contain the postal code and either street name and building number or PO Box. Address information may not contain both PO Box and street address information (street name, building number, stairwell identification or apartment). If apartment information is reported, stairwell identification is mandatory. |
Address specifier | 4 | 0..1 | c/o |
|
Street name | 4 | 0..1 |
|
|
Building number | 4 | 0..1 |
| When the address is in Finland, the building number field:
|
Stairwell identification | 4 | 0..1 |
| Rules for the stairwell identification field:
|
Apartment | 4 | 0..1 |
| When the address is in Finland, the apartment field:
|
Postal code | 4 | 1..1 |
| The postal code and post office must match. This check is only performed for addresses located in Finland. |
PO Box | 4 | 0..1 |
|
|
Post office | 4 | 1..1 |
| The postal code and post office must match. This check is only performed for addresses located in Finland. |
Country | 4 | 1..1 | ISO 31661 code used in accordance with alpha-2 |
|
Electronic invoicing address | 3 | 0..1 |
| Mandatory if invoicing channel is electronic invoice. |
Buyer reference | 4 | 0..1 |
|
|
Electronic invoicing address | 4 | 1..1 |
|
|
Operator identification | 4 | 1..1 |
|
|
Other electronic invoicing address | 3 | 0..1 |
| Mandatory if invoicing channel is mobile invoice (telephone number must be reported) or email (email address must be reported). |
Type | 4 | 1..1 |
|
|
Electronic address | 4 | 1..1 |
| A phone number must start with a plus '+'. A phone number may not contain spaces. The country code ‘+358’ may not be followed by the number zero. |