Business transactions for submitting notifications and ... - Energinet.dk

3.1.2 Valid data for operational schedules and day forecasts
MessageHeader
• DocumentIdentification must together with DocumentVersion be unique
• SenderIdentification must contain the existing GLN/EIC code
• RecieverIdentification must contain the existing GLN/EIC code
• DocumentDateTime must be in the correct format (YYYY-MM-DDThh:mm:ssZ)
• ScheduleTimeInterval must be 24 hours
• Domain must contain one of the below-mentioned Area types
OperationalScheduleTimeSeries
• TimeSerieIdentification must be unique in the message
• BusinessType must be a valid code
• UnitIdentification or UnitTypeIdentification must be filled in
• TimeInterval must be 24 hours
• Resolution depends on where the message is used. Either 1 hour (PT01H) or 5
minutes (PT05M) is indicated.
• Position depends on resolution, from 1 to either 24 or 289
• Quantity must be a value to max. one decimal point
The following area type identifications are used:
o 10YDK-1--------W (Western Denmark)
o 10YDK-2--------M (Eastern Denmark)
3.1.3 Second data flow: Acknowledgement document
If the message can be validated in relation to schemas, and the content meets all
validations in the above validation list, the overall operational schedule is approved by
an acknowledgement with the code A01.
In the event of verification errors in relation to the schema or the content, the
notification must be rejected. The acknowledgement will then contain an error code
and an explanatory text.
The acknowledgement will always contain a reference to the original message and
must be processed in accordance with the rules specified in Regulation F.
3.2 Class diagram
In addition to the MessageHeader, an operational schedule includes the
OperationalScheduleTimeSeries class, which is a time series covering a given period of
time.
Doc. no. 141518 22/70