Definition Type: Element
Name: originatingTradeId
Namespace: http://www.fpml.org/FpML-5/pretrade
Type: nsA:TradeIdentifier
Containing Schema: fpml-doc-5-9.xsd
MinOccurs 0
MaxOccurs unbounded
Abstract
Documentation:
The trade id of the trade(s) upon which this was based, for example the ID of the trade that was submitted for clearing if this is a cleared trade, or of the original trade if this was novated or cancelled and rebooked, or the list of trades that were netted or compressed together in the case of a compression event. The originatingEvent will explain why the trade was created; the existence and number of originatingTradeId elements should correspond to the originatingEvent, and they should be interpreted using that field. If the trade is inside a business event structure (such as a novation or a compression event) this element shuld not be populated; instead the event shoudl be used to represent the other trades.
Collapse XSD Schema Diagram:
Drilldown into versionedTradeId in schema fpml-doc-5-9_xsd Drilldown into tradeId in schema fpml-doc-5-9_xsd Drilldown into accountReference in schema fpml-shared-5-9_xsd Drilldown into partyReference in schema fpml-shared-5-9_xsd Drilldown into PartyAndAccountReferences.model in schema fpml-shared-5-9_xsd Drilldown into tradeId in schema fpml-shared-5-9_xsd Drilldown into issuer in schema fpml-shared-5-9_xsd Drilldown into IssuerTradeId.model in schema fpml-shared-5-9_xsd Drilldown into id in schema fpml-doc-5-9_xsd Drilldown into TradeIdentifier in schema fpml-doc-5-9_xsdXSD Diagram of originatingTradeId in schema fpml-doc-5-9_xsd (Financial products Markup Language (FpML®) - Pretrade)
Collapse XSD Schema Code:
<xsd:element name="originatingTradeId" type="TradeIdentifier" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">The trade id of the trade(s) upon which this was based, for example the ID of the trade that was submitted for clearing if this is a cleared trade, or of the original trade if this was novated or cancelled and rebooked, or the list of trades that were netted or compressed together in the case of a compression event. The originatingEvent will explain why the trade was created; the existence and number of originatingTradeId elements should correspond to the originatingEvent, and they should be interpreted using that field. If the trade is inside a business event structure (such as a novation or a compression event) this element shuld not be populated; instead the event shoudl be used to represent the other trades.</xsd:documentation>
    </xsd:annotation>
</xsd:element>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
issuer nsA:issuer (1) (1)
tradeId nsA:tradeId (1) (1)
partyReference nsA:partyReference 0 (1)
accountReference nsA:accountReference 0 (1)
tradeId nsA:tradeId (1) (1)
versionedTradeId nsA:versionedTradeId (1) (1)
<xs:group> nsA:IssuerTradeId.model (1) (1)
<xs:group> nsA:PartyAndAccountReferences.model (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
id nsA:id (Optional)
Collapse Derivation Tree:
Collapse Comments:
blog comments powered by Disqus