| header | RequestMessageHeader | | Message header. | | 0-1,
mre | |
| validation | Validation | A list of validation sets the sender asserts the document is valid with respect to.
This field is never filled for NSD messages.
| | | 0-∞,
ncf | |
| parentCorrelationId | CorrelationId | A reference to message which register a master agreement. Should be filled in messages
for trade registration when they are being send together with master agreement registration
message.
| Related document form identifier | | 0-1,
nfr | |
| correlationId | CorrelationId | A qualified identifier used to correlate between messages. For NSD messages the format
is [Sender identifier]-[Year]-[Message ID].
| Messages chain identifier | | 0-2,
mre,
nfr | In NSD repository messages only one correlationId element must be filled. |
| sequenceNumber | xsd:positiveInteger | A numeric value that can be used to order messages with the same correlation identifier
from the same sender.
| | | 0-1,
ncf | This is not used in messages to the repository. |
| onBehalfOf | OnBehalfOf | Indicates which party (or parties) (and accounts) a trade or event is being processed
for. Normally there will only be a maximum of 2 parties, but in the case of a novation
there could be a transferor, transferee, remaining party, and other remaining party.
Except for this case, there should be no more than two onABehalfOf references in a
message.
| Message on behalf of. | | 0-4,
ncf | This model is used in messages sent for registration by the repository only. |
| partyId | PartyId | | Repository code of the RA/BRA | | 1-1 | |
| additionalInformation | xsd:string | | Additional information | | 0-1 | |
| partyMasterAgreementId | TradeId | | ID of the master agreement, where party appears as a side | | 0-∞ | |
| party | Party | A legal entity or a subdivision of a legal entity. Parties can perform multiple roles
in a trade lifecycle. For example, the principal parties obligated to make payments
from time to time during the term of the trade, but may include other parties involved
in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee,
broker, calculation agent, etc. In FpML roles are defined in multiple places within
a document. In repository messages this includes reporting role of a party.
| Party | | 0-∞,
mre | |
| account | Account | Optional account information used to precisely define the origination and destination
of financial instruments. In particular this may include client account reference
when defined in this group.
| Party's clients. | Party's client. | 0-∞,
ncf | |