5.1.1 HEAD – Header Record
This is the Header Record for all Sales Report Messages created in accordance with this standard. Each file of a Sales Report Message shall have exactly one such Header Record. It shall be the first Record in each file.
Cell Name | Field Definition | Data Type | M/O/C | Example | |
|---|---|---|---|---|---|
1 |
| The Type of the Record; always to contain “HEAD”. | Fixed string | M | HEAD |
2 |
| The Version of the Message. This shall be in the form dsrf/xxx/yyy/zzz with
The specific values for the architecture is provided in each of the Parts defining a Profile for this standard. dsrf/1.1.2/1.6/1.0 would therefore signal that the Message was created in accordance with the Architecture in version 1.1.2, the allowed value set of version 1.6 and the Record Type Record Type Definitions of version 1.0. If the MessageVersion is provided as dsrf/30, Parts 1 and 2 are deemed to be in the initial version as published in 2016. This capability has been retained for backwards compatibility. | Fixed string | M | dsrf/1.1.2/1.6/1.0 |
3 |
| The Identifier of the Profile used for the Message. | String | M | BasicAudioProfile |
4 |
| The Identifier of the Version of the Profile used for the Message. The value for this field is defined in the relevant Profile standard. | String | M | 1.0 |
5 |
| A string used to uniquely identify the Message. The MessageId shall be, in combination with the MessageSenderId, globally unique. Thus, a MessageSender shall never re-use a MessageId. | String | M | 1234567890 |
6 |
| The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD). | ISO datetime | M | 2014-12-14T10:05:00Z |
7 |
| Sequence number of the file within the Flat File Sales Report Message. The first file shall be numbered “1”. The FileNumber must not be larger than NumberOfFiles | Integer | M | 2 |
8 |
| The number of files that the Sales Report is provided in. | Integer | M | 3 |
9 |
| The StartDate of the reporting Period covered by the Message (in ISO 8601:2004 format). This is a string with the syntax YYYY[-MM[-DD]]. | ISO date | M | 2014-12-01 |
10 |
| The EndDate of the reporting Period covered by the Message (in ISO 8601:2004 format). This is a string with the syntax YYYY[-MM[-DD]]. | ISO date | M | 2014-12-01 |
11 |
| The DDEX PartyId (DPID) of the MessageSender | DDEX Party ID | M | PADPIDA2008120501W |
12 |
| The Full Name of the MessageSender | String | M | Apple |
13 |
| The service name (e.g. a service tier) under which the SalesTransaction took place. The ServiceDescription may not contain space characters or underscores. The ServiceDescription shall only be used if it aids the MessageRecipient in determining the sales context(s) of the Message. The ServiceDesctiption is intended to be a human-readable expression of the totality of the services reported in the Message. For sales/usage reports covering one sales context (see Clause 6.5 in Part 1) this should be the same is being the same string used in the file name (see Clause 9.1 in Part 1) and the single Summary Record contained in the Message. For sales reports covering multiple sale contexts, the ServiceDescription in the Header should be the same as on the file name and represent a human-readable summary of the sales contexts provided in the Summary Records. | String | C | PremiumService |
14 |
| The DDEX PartyId (DPID) of the MessageRecipient. This element is mandatory when the Sales Report Message is sent to one MessageRecipient and must not be included when the Sales Report Message is sent to more than one MessageRecipient. | DDEX Party ID | O | PADPIDA2007081601G |
15 |
| The Full Name of the MessageRecipient. This element is mandatory when the Sales Report Message is sent to one MessageRecipient and must not be included when the Sales Report Message is sent to more than one MessageRecipient. | String | O | SACEM |
16 |
| Content owners represented by the MessageRecipient. This only needs to be provided if there are more than one repertoires being administered by the MessageRecipient. RepresentedRepertoire is of value only if the sales/usage report is sent to a collective rights management organisation. | Multiple strings | O | GEMA|PAECOL |