Сообщения репозитария

eventStatusResponse

The message is used to:

Notify the participant about sending a message to a counterparty for confirmation;
Notify the participant about termination of services with respect to the master agreement, contracts.

The form RM003 – Notification on sending a message to a counterparty is used in the following business processes:

"Master agreement registration" – bilateral consecutive confirmation
"Contract registration" - bilateral combined confirmation
"Quarter report registration" - bilateral consecutive confirmation
"Obligation fulfilment registration" - bilateral consecutive confirmation
"Contract obligation status registration" - bilateral consecutive confirmation
"Termination of the master agreement and cease of services with respect of the master agreement"

Field	Type	Description	Print form title	FFSM title	Properties	Conditions
header	ResponseMessageHeader	A type refining the generic message header to make it specific to response messages.			0-1, mre, nfr
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.
statusItem	EventStatusItem	Defining relation between an event identifier and its current status value.			0-∞, mre
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

Collapse All | Expand All

EventStatusResponse

header(ResponseMessageHeader)

A type refining the generic message header to make it specific to response messages.

messageId(MessageId)

A unique identifier (within its coding scheme) assigned to the message by its creating party. Less when 35 letters or digits.

inReplyTo(MessageId)

A copy of the unique message identifier (within it own coding scheme) to which this message is responding.

sentBy(MessageAddress)

The unique identifier (within its coding scheme) for the originator of a message instance.

sendTo(MessageAddress)

	A unique identifier (within its coding scheme) indicating an intended recipent of a message.

creationTimestamp(dateTime)

The date and time (on the source system) when this message instance was created. Mask 'yyyy-mm-ddThh:mm:ss'.

implementationSpecification(ImplementationSpecification)

The version(s) of specifications that the sender asserts the message was developed for.

version(ImplementationSpecificationVersion)

The version(s) of specifications.

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.

correlationId(CorrelationId)

	In NSD repository messages only one correlationId element must be filled.
	A qualified identifier used to correlate between messages. For NSD messages the format is [Sender identifier]-[Year]-[Message ID].

statusItem(EventStatusItem)

	Defining relation between an event identifier and its current status value.

eventIdentifier(EventIdentifier)

An instance of a unique event identifier. In repository messages filled next elements: partyReference - specified reference on Repository; tradeId - specified repository's number of trade or master agreement (if repository's number isn't assigned then specified NONREF).

Choice the method of definition of a business event.

tradeIdentifier(TradeIdentifier)

	Defines a trade identifier of a business event.

A choice of method of specifying a trade identifier.

Sequence

issuer(IssuerId)

	The data type used for issuer identifiers.

tradeId(TradeId)

	Trade identifier given by a party specified in the 'issuer' element.

Sequence

partyReference(PartyReference)

	Reference to a party.

A choice of a trade identifier type.

tradeId(TradeId)

	Trade identifier given by a party specified in the 'partyReference' element.

Sequence

correlationId(CorrelationId)

	In NSD repository messages only one correlationId element must be filled.
	A qualified identifier used to correlate between messages. For NSD messages the format is [Sender identifier]-[Year]-[Message ID].

status(EventStatus)

An event status value.

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; Reporting Party.

partyId(PartyId)

	A party identifier, e.g. a S.W.I.F.T. bank identifier code (BIC).

partyName(PartyName)

The legal name of the organization.

classification(IndustryClassification)

	The party's industry sector classification.

country(CountryCode)

The country where the party is domiciled.

organizationType(OrganizationType)

The type of an organization's participantion in the OTC derivatives market.