9.1 CHEA – Conflict Header Record

This is the conflict header Record for the two messages defined in this part of the RDR standard. Each file shall have exactly one such conflict header Record. It shall be the first Record in each file.

Cell Name 

Field Definition

Data Type

M/O/C

Example

1

RecordType

The type of the Record which shall always contain CHEA.

Fixed string

M

CHEA

2

MessageVersion

The version of the message. This shall be 10.

Fixed string

M

10

3

AvsVersionId

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

String

M

2

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

1234567890

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

6

SenderPartyId

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

DDEX Party ID

M

PADPIDA2008120501W

7

SenderName

The full name of the sender of the message.

String

M

PPL

8

RecipientPartyId

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

DDEX Party ID

M

PADPIDA2007081601G

9

RecipientName

The full name of the recipient of the message.

String

M

UMG

Mandatory – Optional – Conditional