7.1 RHEA.01 — Header Record

This is the header Record for all messages defined in this part of the RDR-R standard. Each message defined in this part of the RDR standard shall have exactly one header Record. It shall be the first Record in each file.

To indicate a relationship between a RevenueDetails message and a RevenueSummary message, a conditional data element SummaryMessageId is used to link the two. This element shall be used in the RevenueDetails message to reference the RevenueSummary message if such a message is also sent.

Cell Name 

Field Definition

Data Type

M/O/C

Example

1

RecordType

The type of the Record which shall always contain the value RHEA.01.

Fixed string

M

RHEA.01

2

MessageVersion

The version of the message. This shall be 11.

Fixed string

M

11

3

AvsVersionId

The identifier of the version of the DDEX allowed-value sets used in the message.

String

M

4

4

MessageId

A string used to uniquely identify the individual message created in accordance with this part of the RDR standard.

The MessageId shall be, in combination with the SenderPartyId, globally unique.

Therefore, a sender of a message created in accordance with this standard shall never use the same MessageId in two different messages.

String

M

98765654321

5

MessageCreatedDateTime

The date and time at which the Message was created (the only allowed format is RFC 3339: YYYY-MM-DDThh:mm:ssTZD, where TZD stands for time zone designator, which can be the letter Z or an offset from UTC in the format +hh:mm or -hh:mm).

Date

M

2014-12-31T10:05:00Z

6

SummaryMessageId

The string identifying the RevenueSummary message which summarises the RevenueDetails message with which it is associated. This Cell shall remain empty where the header Record is being used in a RevenueReport message.

String

C

1234567890

7

UsageStartDate

The date identifying the beginning of the period of usage for which the revenue data is being communicated in the relevant message in ISO 8601 format. This is a string with the syntax YYYY[-MM[-DD]].

Date

M

2014-12-31

8

UsageEndDate

The date identifying the end of the period of usage for which the revenue data is being communicated in the relevant message in ISO 8601 format). This is a string with the syntax YYYY[-MM[-DD]].

Date

M

2014-12-31

9

DistributionDate

The date of the distribution covered by the message (in ISO 8601 format. This is a string with the syntax YYYY[-MM[-DD]].

Date

M

2014-12-31

10

DistributionDescription

A string describing the nature of the distribution of revenue which is the subject of the relevant message. This can be an identifier for the distribution or a description of its type, for example, a provisory distribution, a cancellation of a provisory distribution, a final distribution or a settlement distribution.

String

O

Final distribution

11

SenderPartyId

The DDEX Party Identifier (DPID) of the sender of the message.

DDEX

Party ID

M

PADPIDA2008120501W

12

SenderName

The full name of the sender of the message.

String

M

PPL

13

RecipientPartyId

The DDEX Party Identifier (DPID) of the recipient of the message.

This element is mandatory when a RevenueReport message or a RevenueDetails message (whether or not in combination with a RevenueSummary message) is being sent to only one message recipient. A RecipientPartyId shall not be included when the relevant message is sent to more than one message recipient.

DDEX

Party ID

O

PADPIDA2007081601G

14

RecipientName

The full name of the recipient of the message.

This element is mandatory when a RevenueReport message or a RevenueDetails message (whether or not in combination with a RevenueSummary message) is being sent to only one message recipient. A RecipientName shall not be included when the relevant message is sent to more than one message recipient.

String

O

SCPP

Mandatory – Optional – Conditional

Search