schemas.fpml-5-12.confirmation.fpml-msg-5-12.xsd Maven / Gradle / Ivy
A type that can be used to identify the type of business process in a request. Examples include Allocation, Clearing, Confirmation, etc.
A type defining the content model for a request message that can be subsequently corrected or retracted.
Indicates if this message corrects an earlier request.
This provides a mechanism for the requester to assign an ID that can be used for subsequent corrections and retractions, without requiring any acknowledgement or reply from the message recipient. The FpML architecture recommends that services support this feature, because otherwise requesters cannot correct or retract requests until they receive a reply from the service. If the correlation ID is not supplied by the requester, the recipient should provide a correlation ID in its response, which the requester should retain in case subsequent corrections or retractions are required. In this case, the "inReplyTo" element in the message header may be used to link the response to the request.
A type defining a correlation identifier and qualifying scheme
Identification of a business event, for example through its correlation id or a business identifier.
A coding scheme used to describe the matching/confirmation status of a trade, post-trade event, position, or cash flows.
A type used in event status enquiry messages which relates an event identifier to its current status value.
An instance of a unique event identifier.
An event status value.
A type defining the content model for a message normally generated in response to a requestEventStatus request.
A type defining the basic content for a message sent to inform another system that some exception has been detected.
A type defining the content model for an exception message header.
A copy of the unique message identifier (within it own coding scheme) to which this message is responding.
A type defining the basic structure of all FpML messages which is refined by its derived types.
The data type used for identifying a message address.
A type defining the content model for a generic message header that is refined by its derived classes.
A unique identifier (within its coding scheme) assigned to the message by its creating party.
The data type use for message identifiers.
A type defining the content model for a request message that cannot be subsequently corrected or retracted.
A type defining the basic content for a message sent to inform another system that some 'business event' has occured. Notifications are not expected to be replied to.
A type that refines the generic message header to match the requirements of a NotificationMessage.
A copy of the unique message identifier (within it own coding scheme) to which this message is responding.
A version of a specification document used by the message generator to format the document.
A type defining additional information that may be recorded against a message.
Identifies that party that has ownership of this information.
A structure used to group together individual messages that can be acted on at a group level.
A numeric, sequentially ascending (i.e. gapless) value (starting at 1) that can be used to identify and distinguish the individual constituents of a portfolio request. A recipient should ensure that all sequence numbers from 1 to the final sequence number (where submissionsComplete is true) have arrived before completing the portfolio request.
Indicates whether all individual requests have been submitted for this portfolio request.
A structure used to group together individual messages that can be acted on at a group level.
A numeric, sequentially ascending (i.e. gapless) value (starting at 1) that can be used to identify and distinguish the individual constituents of a portfolio request. A recipient should ensure that all sequence numbers from 1 to the final sequence number (where submissionsComplete is true) have arrived before completing the portfolio request.
A structure used to identify a portfolio in a message.
An identifier that is unique for each portfolio-level request, and which can be used to group together the individual messages in the portfolio request.
A type defining the content model for a message allowing one party to query the status of one event (trade or post-trade event) previously sent to another party.
A type defining the basic content of a message that requests the receiver to perform some business operation determined by the message type and its content.
A type refining the generic message header content to make it specific to request messages.
A message to request that a message be retransmitted. The original message will typically be a component of a group of messages, such as a portfolio or a report in multiple parts.
A type that can be used to hold an identifier for a report instance.
A type that allows the specific report and section to be identified.
An identifier for the specific instance of this report.
A strictly ascending sequential (gapless) numeric value that can be used to identify the section of a report.
A type refining the generic message content model to make it specific to response messages.
A type refining the generic message header to make it specific to response messages.
A copy of the unique message identifier (within it own coding scheme) to which this message is responding.
A type defining the content model for a human-readable notification to the users of a service.
The category or type of the notification message, e.g. availability, product coverage, rules, etc.
A human-readable notification.
The time at which the information supplied by the advisory becomes effective. For example, if the advisory advises of a newly planned service outage, it will be the time the service outage begins.
The time at which the information supplied by the advisory becomes no longer effective. For example, if the advisory advises of a newly planned service outage, it will be the time the service outage ends.
A type that can be used to describe the category of an advisory message, e.g.. Availability, Rules, Products, etc., etc..
Event Status messages.
A type defining the content model for a message that allows a service to send a notification message to a user of the service.
The name of the service to which the message applies
The current state of the service (e.g. Available, Unavailable).
A description of the stage of processing of the service, for example EndofDayProcessingCutoffOccurred, EndOfDayProcessingCompleted. [TBD: could be combined with advisory]
A human-readable message providing information about the service..
A type that can be used to describe the processing phase of a service. For example, EndOfDay, Intraday.
A type that can be used to describe a stage or step in processing provided by a service, for example processing completed.
A type defining the content model for report on the status of the processing by a service. In the future we may wish to provide some kind of scope or other qualification for the event, e.g. the currencies, products, or books to which it applies.
The processing cycle or phase that this message describes. For example, EndOfDay or Intraday.
The stage within a processing cycle or phase that this message describes. For example, Netting or Valuation.
The event that occurred within the cycle or step, for example "Started" or "Completed"..
A type that can be used to describe what stage of processing a service is in. For example, Netting or Valuation.
A type that can be used to describe the availability or other state of a service, e.g. Available, Unavaialble.
A type holding a structure that is unvalidated
The verification status of the position as reported by the sender (Verified, Disputed).
The reason for any dispute or change in verification status.
A model group defining the elements used for process correlation. The correlation ID is used to link followup corrections and retractions to the original request, and to help identify which replies link to which requests. The parent correlation ID is used to keep track of the parent process.
An optional identifier used to correlate between related processes
A model group defining the full messsage correlation mechanism, but with optional sequence. Please note that for reports in Reporting view, usage of the correlation and sequence model is not well defined in the standard an may be deprecated from future versions of the standard. Use the ReportReference structure to identify report instances and section numbers if a report must be divided into chunks.
A model group defining the full messsage correlation mechanism. The correlation ID is used to link followup corrections and retractions to the original request, and to help identify which replies link to which requests. (The "inReplyTo" element may also be used for this purpose, but it contains a message identifier rather than a business object identifier.) The sequence ID is used to establish an ordering between multiple messages related to the same business object (identified by the same correlation identifier). It contains a value the must ascend (possibly with gaps) messages on the same correlation ID.
A model group defining the element used for process correlation. The correlation ID is used to link followup corrections and retractions to the original request, and to help identify which replies link to which requests.
A qualified identifier used to correlate between messages
A model group which has exception elements.
An instance of the Reason type used to record the nature of any errors associated with a message.
Any string of additional data that may help the message processor, for example in a rejection message this might contain a code value or the text of the original request (within a CDATA section).
Defines the structure that contains routing and identification information, which allows processing and transfer of the message. It contains only messaging information that is applicable to all messages. If the information is not message related or is not applicable to all messages then it is not defined in the message header.
The unique identifier (within its coding scheme) for the originator of a message instance.
A unique identifier (within its coding scheme) indicating an intended recipent of a message.
A unique identifier (within the specified coding scheme) giving the details of some party to whom a copy of this message will be sent for reference.
The date and time (on the source system) when this message instance was created.
The date and time (on the source system) when this message instance will be considered expired.
The version(s) of specifications that the sender asserts the message was developed for.
Additional message information that may be provided by each involved party.
Defines a model group that allows a constituent of a portfolio to be included in a request retransmission message.
Defines a model group that allows a portfolio reference request structure to be included in a message.
Defines a model group that allows a portfolio to be identified in a response message.
Defines a model group that allows either details of a portoflio constituent or report constituent to be provided. Typically this will be used in a request retransmission message.
Defines a model group that allows a chunck of a report to be included in a request retransmission message.
A model group defining the element used for message sequencing
A numeric value that can be used to order messages with the same correlation identifier from the same sender.
The root element used for rejected message exceptions
© 2015 - 2025 Weber Informatics LLC | Privacy Policy