6.5 Message Transfer Protocol and File Naming Convention

The transfer of messages defined in accordance with this standard should be effected using SFTP.

All messages defined in accordance with this standard shall be named in accordance with the following syntax:

 RDRR_MessageRecipient_MessageSender_MessageNotificationPeriod_MessageCreatedDateTime.ext

With:

Term

Definition

MessageRecipient

The Party Name or DDEX Party ID (DPID) of the Message Recipient.

The Message Recipient may be omitted if the RevenueDeclarationMessage is sent to more than one recipient. This information shall be the same as the information conveyed in the file Header (RHEA). DDEX Party IDs do not contain special characters.

MessageSender

The Party Name or DPID of the Message Sender.

This information shall be the same as the information conveyed in the appropriate Record. DDEX Party IDs do not contain special characters.

MessageNotificationPeriod

The reporting Period covered by the message in accordance with ISO 8601. The only allowed syntaxes are:

  • yyyy for a year

  • yyyy-mm for a month

  • yyyy-mm-dd for a day

  • yyyy-Qq for a quarter

  • yyyy-Www for a week (starting on a Monday)

  • yyyy-mm-dd--yyyy-mm-dd with the two dates being the start and end date of the period. This syntax required two dashes between the two dates.

MessageCreatedDateTime

The date and time on which the message was created. The only allowed format is the full basic ISO 8601 format without a time zone designator: yyyyymmddThhmmss. The time zone is assumed to be the one of the Message Sender’s  location.

ext

The file extension, to be “.tsv."
When the file is compressed, for example with gzip, the extension should indicate this and may be .tsv.gz.

The following constraints apply:

  1. None of the file name elements may contain an underscore character;

  2. None of the file name elements may contain a space character;

  3. When a file name element is to be omitted, the two underscore characters to the left and right follow each other immediately; and

  4. Other file naming conventions may be agreed on a bilateral basis (specifically for testing).

Search