element <blockTradeId> (local)

Namespace: | http://www.fpml.org/FpML-5/reporting
Type: | TradeIdentifier
Content: | complex, 1 attribute, 7 elements
Defined: | locally witnin PartyTradeIdentifier complexType in fpml-doc-5-3.xsd; see XML source

Content Model Diagram

XML Representation Summary
<blockTradeId
id | = | xsd:ID
| >
Content: | (issuer, tradeId) | (partyReference?, accountReference?, reportingRole?, (tradeId? | versionedTradeId?)+)
</blockTradeId>

Content model elements (7):

  accountReference (defined in PartyAndAccountReferences.model group),
  issuer (defined in TradeIdentifier complexType),
  partyReference (defined in PartyAndAccountReferences.model group),
  reportingRole (defined in TradeIdentifier complexType),
  tradeId (defined in TradeIdentifier complexType),
  tradeId (defined in TradeIdentifier complexType),
  versionedTradeId

Included in content model of elements (17):

  newTradeIdentifier,
  oldTradeIdentifier (defined in TradeChangeContent complexType),
  oldTradeIdentifier (in novation),
  partyTradeIdentifier (defined in PartyTradeIdentifiers complexType),
  partyTradeIdentifier (defined in Portfolio complexType),
  partyTradeIdentifier (defined in TradeIdentifyingItems complexType),
  partyTradeIdentifier (defined in TradeValuationItem complexType),
  partyTradeIdentifier (in tradeHeader),
  partyTradeIdentifier (in tradeReferenceInformation),
  partyTradeIdentifier (in valuationReportRetracted),
  resultingTradeIdentifier,
  tradeIdentifier (defined in TradeChangeBase complexType),
  tradeIdentifier (in deClear),
  tradeIdentifier (in optionExercise),
  tradeIdentifier (in optionExpiry defined in Events.model group),
  tradeIdentifier (in optionExpiry in terminatingEventsReport),
  tradeIdentifier (in tradeMaturity)

Annotation
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).
XML Source (w/o annotations (1); see within schema source)

<xsd:element minOccurs="0" name="blockTradeId" type="TradeIdentifier"/>

XML schema documentation generated with DocFlex/XML 1.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.