BusinessApplicationHeaderV01

The Business Layer deals with Business Messages. The behaviour of the Business Messages is fully described by the Business Transaction and the structure of the Business Messages is fully described by the Message Definitions and related Message Rules, Rules and Market Practices. All of which are registered in the ISO 20022 Repository.
A single new Business Message (with its accompagnying business application header) is created - by the sending MessagingEndpoint - for each business event; that is each interaction in a Business Transaction. A Business Message adheres to the following principles:
" A Business Message (and its business application header) must not contain information about the Message Transport System or the mechanics or mechanism of message sending, transportation, or receipt.
" A Business Message must be comprehensible outside of the context of the Transport Message. That is the Business Message must not require knowledge of the Transport Message to be understood.
" A Business Message may contain headers, footers, and envelopes that are meaningful for the business. When present, they are treated as any other message content, which means that they are considered part of the Message Definition of the Business Message and as such will be part of the ISO 20022 Repository.
" A Business Message refers to Business Actors by their Name. Each instance of a Business Actor has one Name. The Business Actor must not be referred to in the Transport Layer.
Specific usage of this BusinessMessageHeader may be defined by the relevant SEG.

Message Identifier: head.001.001.01

Elements

Name	Type	Multiplicity	Definition
CharacterSet	UnicodeChartsCode	[0..1]	Contains the character set of the text-based elements used in the Business Message.
From	Party9Choice	[1..1]	The sending MessagingEndpoint that has created this Business Message for the receiving MessagingEndpoint that will process this Business Message. Note the sending MessagingEndpoint might be different from the sending address potentially contained in the transport header (as defined in the transport layer).
To	Party9Choice	[1..1]	The MessagingEndpoint designated by the sending MessagingEndpoint to be the recipient who will ultimately process this Business Message. Note the receiving MessagingEndpoint might be different from the receiving address potentially contained in the transport header (as defined in the transport layer).
BusinessMessageIdentifier	Max35Text	[1..1]	Unambiguously identifies the Business Message to the MessagingEndpoint that has created the Business Message.
MessageDefinitionIdentifier	Max35Text	[1..1]	Contains the MessageIdentifier that defines the BusinessMessage. It must contain a MessageIdentifier published on the ISO 20022 website. example camt.001.001.03.
BusinessService	Max35Text	[0..1]	Specifies the business service agreed between the two MessagingEndpoints under which rules this Business Message is exchanged. To be used when there is a choice of processing services or processing service levels. Example: E&I.
CreationDate	ISONormalisedDateTime	[1..1]	Date and time when this Business Message (header) was created. Note Times must be normalized, using the "Z" annotation.
CopyDuplicate	CopyDuplicate1Code	[0..1]	Indicates whether the message is a Copy, a Duplicate or a copy of a duplicate of a previously sent ISO 20022 Message.
PossibleDuplicate	YesNoIndicator	[0..1]	Flag indicating if the Business Message exchanged between the MessagingEndpoints is possibly a duplicate. If the receiving MessagingEndpoint did not receive the original, then this Business Message should be processed as if it were the original. If the receiving MessagingEndpoint did receive the original, then it should perform necessary actions to avoid processing this Business Message again. This will guarantee business idempotent behaviour. NOTE: this is named "PossResend" in FIX - this is an application level resend not a network level retransmission.
Priority	BusinessMessagePriorityCode	[0..1]	Relative indication of the processing precedence of the message over a (set of) Business Messages with assigned priorities.
Signature	SignatureEnvelope	[0..1]	Contains the digital signature of the Business Entity authorised to sign this Business Message.
Related	BusinessApplicationHeader1	[0..1]	Specifies the Business Application Header of the Business Message to which this Business Message relates. Can be used when replying to a query; can also be used when canceling or amending.

Validation Rules

RelatedPresentWhenCopyDupl: Related MUST contain the relevant BusinessMessageHeader elements of the BusinessMessage to which this BusinessMessage relates. If CopyDuplicate is present, then Related MUST be present.