Documentation for Financial products Markup Language (FpML®)
Definition Type: Element
Name: tradingEvent
Namespace: http://www.fpml.org/FpML-5/recordkeeping
Type: nsD:TradingEventSummary
Containing Schema: fpml-recordkeeping-processes-5-10.xsd
MinOccurs 0
MaxOccurs unbounded
Abstract
Documentation:
This is provided to support snapshot reporting that requires trading history. Some implementations are using the "trade" event to report the current snapshot of a contract. In these cases it may also be necessary to report the most recent trading event to support regulatory reporting mandates. For this reason the tradingEvent is provided to allow that event to be attached to the trade report.
Collapse XSD Schema Diagram:
Drilldown into payment in schema fpml-business-events-5-10_xsd2 Drilldown into changeInQuantity in schema fpml-business-events-5-10_xsd2 Drilldown into changeInNumberOfOptions in schema fpml-business-events-5-10_xsd2 Drilldown into changeInNotional in schema fpml-business-events-5-10_xsd2 Drilldown into notionalChange in schema fpml-business-events-5-10_xsd2 Drilldown into ReportingNotionalChange.model in schema fpml-business-events-5-10_xsd2 Drilldown into effectiveDate in schema fpml-business-events-5-10_xsd2 Drilldown into executionDateTime in schema fpml-business-events-5-10_xsd2 Drilldown into agreementDate in schema fpml-business-events-5-10_xsd2 Drilldown into AgreementAndEffectiveDates.model in schema fpml-business-events-5-10_xsd2 Drilldown into eventType in schema fpml-business-events-5-10_xsd2 Drilldown into eventIdentifier in schema fpml-business-events-5-10_xsd2 Drilldown into TradingEventSummary in schema fpml-business-events-5-10_xsd2XSD Diagram of tradingEvent in schema fpml-recordkeeping-processes-5-10_xsd (Financial products Markup Language (FpML®))
Collapse XSD Schema Code: 
<xsd:element name="tradingEvent" type="TradingEventSummary" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">This is provided to support snapshot reporting that requires trading history. Some implementations are using the "trade" event to report the current snapshot of a contract. In these cases it may also be necessary to report the most recent trading event to support regulatory reporting mandates. For this reason the tradingEvent is provided to allow that event to be attached to the trade report.</xsd:documentation>
    </xsd:annotation>
</xsd:element>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
eventIdentifier nsD:eventIdentifier 0 unbounded
eventType nsD:eventType (1) (1)
agreementDate nsD:agreementDate 0 (1)
executionDateTime nsD:executionDateTime 0 (1)
effectiveDate nsD:effectiveDate 0 (1)
notionalChange nsD:notionalChange 0 (1)
changeInNotional nsD:changeInNotional 0 unbounded
changeInNumberOfOptions nsD:changeInNumberOfOptions 0 unbounded
changeInQuantity nsD:changeInQuantity 0 unbounded
payment nsD:payment 0 (1)
<xs:group> nsD:AgreementAndEffectiveDates.model (1) (1)
<xs:group> nsD:ReportingNotionalChange.model 0 (1)
Collapse Derivation Tree:
Documentation for Financial products Markup Language (FpML®)

Generated using Liquid Studio - Developer Bundle 21.0.0.0