complexType "PartyTradeInformation"
Namespace:
http://www.fpml.org/FpML-5/confirmation
Content:
complex, 9 elements
Defined:
globally in fpml-doc-5-2.xsd; see XML source
Includes:
definitions of 7 elements
Used:
at 2 locations
Content Model Diagram
XML Representation Summary
<...>
   
Content: 
 partyReference, accountReference?, relatedParty*, reportingRole?, unit*, isAccountingHedge?, category*, trader*, executionDateTime?
</...>
Content Model Elements (9):
accountReference (defined in PartyAndAccountReferences.model group),
category (defined in PartyTradeInformation complexType),
executionDateTime (defined in PartyTradeInformation complexType),
isAccountingHedge,
partyReference (defined in PartyAndAccountReferences.model group),
relatedParty (defined in PartyTradeInformation complexType),
reportingRole,
trader,
unit (defined in PartyTradeInformation complexType)
All Direct / Indirect Based Elements (2):
partyTradeInformation (in tradeHeader), partyTradeInformation (in tradeReferenceInformation)
Known Usage Locations
Annotation
A type defining additional information that may be recorded against a trade.
XML Source (w/o annotations (9); see within schema source)
<xsd:complexType name="PartyTradeInformation">
<xsd:sequence>
<xsd:group ref="PartyAndAccountReferences.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty"/>
<!-- RPTWG 2009-09-04 begin-->
<xsd:element minOccurs="0" name="reportingRole" type="ReportingRole"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="unit" type="Unit"/>
<xsd:element minOccurs="0" name="isAccountingHedge" type="xsd:boolean"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="category" type="TradeCategory"/>
<!-- RPTWG 2009-09-04 end -->
<xsd:element maxOccurs="unbounded" minOccurs="0" name="trader" type="Trader"/>
<xsd:element minOccurs="0" name="executionDateTime" type="ExecutionDateTime"/>
<!--- the following elements were removed from 5.2 because CFTC/SEC reporting requirements were removed from 5.2
<xsd:element name="timestamps" type="TradeProcessingTimestamps" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">Allows timing information about a trade to be recorded.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="cleared" type="xsd:boolean" minOccurs="0" >
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies whether the trade is anticipated to be cleared via a derivative clearing organization</xsd:documentation>
<xsd:appinfo>
<view:override view="transparency" minOccurs="1"/>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="endUserException" type="xsd:boolean" minOccurs="0" >
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies whether the trade is not obligated to be cleared via a derivative clearing organization because the "End User Exception" was invoked.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="nonStandardTerms" type="xsd:boolean" minOccurs="0" >
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies whether the trade contains terms that affect pricing that are not represented by the standard reportable data fields, that is, it indicates a bespoke trade that might otherwise appear from its characteristics to be a standardized trade but is really non-standard. The flag indicates that the price for this trade is not to be construed as being indicative of the market. </xsd:documentation>
<xsd:appinfo>
<view:override view="transparency" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="offMarketPrice" type="xsd:boolean" minOccurs="0" >
<xsd:annotation>
<xsd:documentation xml:lang="en">Indicates that the price does not reflect the current market. For example, in a credit trade where the two counterparties are not of equal credit standing, there is no initial margin and one party pays collateral to the other in the form of an add-on to the price (say a price that would otherwise be 100 at the market is struck at 105 to include the collateral, resulting in a very off-market looking price.)</xsd:documentation>
<xsd:appinfo>
<view:override view="transparency" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="largeSizeTrade" type="xsd:boolean" minOccurs="0" >
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies whether the sender of this trade considers it to be a large notional trade or block trade for reporting purposes, and thus eligible for delayed public reporting.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="executionType" type="ExecutionType" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">Used to describe how the trade was executed, e.g. via voice or electronically.</xsd:documentation>
<xsd:appinfo>
<view:override view="transparency" minOccurs="1"/>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="executionVenueType" type="ExecutionVenueType" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.</xsd:documentation>
<xsd:appinfo>
<view:override view="transparency" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="confirmationType" type="ExecutionType" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation.</xsd:documentation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="counterpartyTypes" type="CounterpartyTypes" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">Used to identify whether this trades involves swaps dealers, major swaps participants, or other types of organizations.</xsd:documentation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
-->
<!--
<xsd:element name="regulator" type="Regulator" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">Used to identify the regulator(s) responsible for monitoring this transaction.</xsd:documentation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
<view:override view="transparency" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
-->
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; defined within this component only; 7/9)
category
Type:
TradeCategory, simple content
Used to categorize trades into user-defined categories, such as house trades vs. customer trades.
Simple Content
xsd:normalizedString
maxLength:
 255
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="category" type="TradeCategory"/>
executionDateTime
Type:
ExecutionDateTime, simple content
Trade execution date time provided by a central execution facility.
Simple Content
xsd:dateTime
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="executionDateTime" type="ExecutionDateTime"/>
isAccountingHedge
Type:
xsd:boolean, predefined, simple content
Specifies whether the trade used to hedge a risk for accounting purposes for the specified party. (TODO: do we need to distinguish between asset and liability hedges?)
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="isAccountingHedge" type="xsd:boolean"/>
relatedParty
Type:
RelatedParty, complex content
Identifies a related party performing a role within the transaction.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty"/>
reportingRole
Type:
ReportingRole, simple content
Identifies the role of this party in reporting this trade (e.g. originator, counterparty).
Simple Content
xsd:normalizedString
maxLength:
 255
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="reportingRole" type="ReportingRole"/>
trader
Type:
Trader, simple content
Identifies the person or persons who assumed the role of trader for this trade.
Simple Content
xsd:normalizedString
maxLength:
 255
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="trader" type="Trader"/>
unit
Type:
Unit, simple content
Identifies the unit/division/desk etc. that executed or supports this trade
Simple Content
xsd:normalizedString
maxLength:
 255
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="unit" type="Unit"/>
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.