Definition Type: Element
Name: tradingEvent
Namespace: http://www.fpml.org/FpML-5/recordkeeping
Type: nsA:TradingEventSummary
Containing Schema: fpml-recordkeeping-processes-5-9.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-9_xsd Drilldown into changeInQuantity in schema fpml-business-events-5-9_xsd Drilldown into changeInNumberOfOptions in schema fpml-business-events-5-9_xsd Drilldown into changeInNotional in schema fpml-business-events-5-9_xsd Drilldown into notionalChange in schema fpml-business-events-5-9_xsd Drilldown into ReportingNotionalChange.model in schema fpml-business-events-5-9_xsd Drilldown into effectiveDate in schema fpml-business-events-5-9_xsd Drilldown into executionDateTime in schema fpml-business-events-5-9_xsd Drilldown into agreementDate in schema fpml-business-events-5-9_xsd Drilldown into AgreementAndEffectiveDates.model in schema fpml-business-events-5-9_xsd Drilldown into eventType in schema fpml-business-events-5-9_xsd Drilldown into eventIdentifier in schema fpml-business-events-5-9_xsd Drilldown into TradingEventSummary in schema fpml-business-events-5-9_xsdXSD Diagram of tradingEvent in schema fpml-recordkeeping-processes-5-9_xsd (Financial products Markup Language (FpML®) - Record Keeping)
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 nsA:eventIdentifier 0 unbounded
eventType nsA:eventType (1) (1)
agreementDate nsA:agreementDate 0 (1)
executionDateTime nsA:executionDateTime 0 (1)
effectiveDate nsA:effectiveDate 0 (1)
notionalChange nsA:notionalChange 0 (1)
changeInNotional nsA:changeInNotional 0 unbounded
changeInNumberOfOptions nsA:changeInNumberOfOptions 0 unbounded
changeInQuantity nsA:changeInQuantity 0 unbounded
payment nsA:payment 0 (1)
<xs:group> nsA:AgreementAndEffectiveDates.model (1) (1)
<xs:group> nsA:ReportingNotionalChange.model 0 (1)
Collapse Derivation Tree:
Collapse Comments:
blog comments powered by Disqus