8.1 File Naming Convention
All files that make up a Sales Report Message shall be named in accordance with the following syntax:
The Party Name or DDEX Party ID (DPID) of the Message Recipient.
The MessageRecipient may be omitted if the Sales Report Message is sent to more than one recipient. This information shall be the same as the information conveyed in the file Header (
The Party Name or DDEX Party ID (DPID) of the
This information shall be the same as the information conveyed in the appropriate Record. Note: DDEX Party IDs do not contain special characters.
A description of the service name (e.g. a service tier) to be reported on. Multiple tiers can be communicated by separating them with dashes.
This information shall be the same as the information conveyed in the file Header (
The reporting Period covered by the Message in accordance with ISO 8601:2004. The only allowed syntaxes are:
The territory for which the Usage, Revenue or Sale transactions in this message are reported.
The TerritoryOfUseOrSale shall be provided as a single ISO Territory Code if one territory is to be communicated. Otherwise, the MessageSender and MessageRecipient(s) shall agree a value acceptable to both/all.
The file counter.
For example, the 7th file of a 9-file Sales Report Message would be
The date and time on which the Message was created (the only allowed format is the full basic ISO 8601:2004 format without a time zone designator:
The file extension, to be “
The following constraints apply:
None of the file name elements may contain an underscore character.
None of the file name elements may contain an space character.
When a file name element is to be omitted, the two underscore characters to the left and right follow each other immediately.
Other file naming conventions may be agreed on a bilateral basis (specifically for testing).