element <originatingTradeId> (local)
Namespace:
Type:
Content:
complex, 1 attribute, 7 elements
Defined:
Content Model Diagram
XML Representation Summary
<originatingTradeId
   
 = 
xsd:ID
   
>
   
Content: 
</originatingTradeId>
Content model elements (7):
accountReference (defined in PartyAndAccountReferences.model group),
issuer (defined in IssuerTradeId.model group),
partyReference (defined in PartyAndAccountReferences.model group),
reportingRole (defined in TradeIdentifier complexType),
tradeId (defined in IssuerTradeId.model group),
tradeId (defined in TradeIdentifier complexType),
versionedTradeId
Included in content model of elements (22):
feeTradeIdentifier,
newTradeIdentifier,
oldTradeIdentifier (defined in OldTrade.model group),
oldTradeIdentifier (defined in TradeChangeContent complexType),
partyTradeIdentifier (defined in PartyTradeIdentifiers complexType),
partyTradeIdentifier (defined in Portfolio complexType),
partyTradeIdentifier (defined in TradeIdentifyingItems complexType),
partyTradeIdentifier (defined in TradeValuationItem complexType),
partyTradeIdentifier (defined in Withdrawal complexType),
partyTradeIdentifier (in tradeHeader),
partyTradeIdentifier (in tradeReferenceInformation),
partyTradeIdentifier (in valuationReportRetracted),
partyTradeIdentifier (in verificationStatusNotification),
resultingTradeIdentifier,
tradeIdentifier (defined in OptionExercise complexType),
tradeIdentifier (defined in OptionExpiry complexType),
tradeIdentifier (defined in TradeChangeBase complexType),
tradeIdentifier (in deClear),
tradeIdentifier (in nonpublicExecutionReportRetracted),
tradeIdentifier (in optionEvent),
tradeIdentifier (in optionExpiry in terminatingEventsReport),
tradeIdentifier (in tradeMaturity)
Annotation
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.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="originatingTradeId" type="TradeIdentifier"/>

XML schema documentation generated with DocFlex/XML 1.10b5 using DocFlex/XML XSDDoc 2.8.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.