Diagram
| Super-types: | Document < Message (by extension) < ResponseMessage (by extension) < TradeErrorResponse (by extension) |
|---|---|
| Sub-types: |
|
| Name | TradeErrorResponse |
|---|---|
| Abstract | yes |
| Documentation | An abstract trade error response message containing a singe trade or trade reference. |
'Indicate which version of the FpML Schema an FpML message adheres to.'
"'This optional attribute can be supplied by a message creator in an FpML instance to specify which build number of the schema was used to define the message when it was generated.'
"'The specific build number of this schema version. This attribute is not included in an instance document. Instead, it is supplied by the XML parser when the document is validated against the FpML schema and indicates the build number of the schema file. Every time FpML publishes a change to the schema, validation rules, or examples within a version (e.g., version 4.2) the actual build number is incremented. If no changes have been made between releases within a version (i.e. from Trial Recommendation to Recommendation) the actual build number stays the same.'
">'An element that allows the full details of the trade to be used as a mechanism for identifying the trade for which the post-trade event pertains'
'A container since an individual trade can be referenced by two or more different partyTradeIdentifier elements - each allocated by a different 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.'