fpml:tradeIdentifier

Element information

Content

• Sequence [1..1]
  from type fpml:TradeIdentifier
  Choice [1..1]
  • Sequence [1..1]
    1. fpml:issuer [1..1]    
    2. fpml:tradeId [1..1]    
  • Sequence [1..1]
    from group fpml:PartyAndAccountReferences.model
    fpml:partyReference [1..1]    Reference to a party.
    fpml:accountReference [0..1]    Reference to an account.
    1. Choice [1..*]
       • fpml:tradeId    
       • fpml:versionedTradeId    A trade identifier accompanied by a version number. In regulatory reporting views, this should be avoided except for internal mnessaging.
  1. fpml:linkId [0..*]    A link identifier allowing the trade to be associated with other related trades, e.g. the linkId may contain a tradeId for an associated trade or several related trades may be given the same linkId. FpML does not define the domain values associated with this element. Note that the domain values for this element are not strictly an enumerated list.
  2. fpml:allocationTradeId [0..*]    The trade id of the allocated trade. This is used by the block trade to reference the allocated trade.
  3. fpml:blockTradeId [0..1]    The trade id of the block trade. This is used by each one of the allocated trades to reference the block trade. This element can also represent the trade id of the parent trade for N-level allocations. In the case, this element is only used to model N-level allocations in which the trade acts as block and allocated trade at the same time. This basically means the ability to allocate a block trade to multiple allocation trades, and then allocate these in turn to other allocation trades (and so on if desired).
  4. fpml:originatingTradeId [0..*]    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.
  5. fpml:productComponentIdentifier [0..*]    The USIs of the components of this trade, when this trade contains a strategy.

Attributes

Used in

• Type fpml:TradeChangeBase
• Type fpml:DeClear (Element fpml:deClear)
• Type fpml:OptionExercise (Element fpml:optionExercise)
• Type fpml:OptionExpiry (Element fpml:optionExpiry)
• Type fpml:OptionExpiryBase (Element fpml:optionExpiry)
• Type fpml:TradeMaturity (Element fpml:tradeMaturity)
• Type fpml:TradeNotionalChange via extension of fpml:TradeChangeBase (Elements fpml:increase, fpml:termination)

Sample instance

<tradeIdentifier>
   <partyReference href="clearer"/>
   <tradeId tradeIdScheme="http://www.lch.com/coding-scheme/clearing-id">CL000123</tradeId>
</tradeIdentifier>