XML Schema Documentation

Element: positionActivityReport

[Table of contents]

Name positionActivityReport
Type PositionActivityReport
Nillable no
Abstract no
Logical Diagram
XML Instance Representation
<positionActivityReport
fpmlVersion=" xsd:token (value comes from list: {'5-0'}) [1]

'Indicate which version of the FpML Schema an FpML message adheres to.'

"

expectedBuild=" xsd:positiveInteger [0..1]

'This optional attribute can be supplied by a message creator in an FpML instance to specify which build number of the schema was used to define the message when it was generated.'

"

actualBuild="9 [0..1]

'The specific build number of this schema version. This attribute is not included in an instance document. Instead, it is supplied by the XML parser when the document is validated against the FpML schema and indicates the build number of the schema file. Every time FpML publishes a change to the schema, validation rules, or examples within a version (e.g., version 4.2) the actual build number is incremented. If no changes have been made between releases within a version (i.e. from Trial Recommendation to Recommendation) the actual build number stays the same.'

"
>
<header> NotificationMessageHeader </header> [0..1]
<validation> Validation </validation> [0..*]
Start Group: Correlation.model [0..1]
<correlationId> CorrelationId </correlationId> [0..1]

'A qualified identifier used to correlate between messages'

End Group: Correlation.model
Start Group: Sequence.model [0..1]
<sequenceNumber> xsd:positiveInteger </sequenceNumber> [0..1]

'A numeric value that can be used to order messages with the same correlation identifier from the same sender.'

End Group: Sequence.model
Start Group: OnBehalfOf.model [0..1]
<onBehalfOf> OnBehalfOf </onBehalfOf> [0..1]

'Indicates which party (and accounts) a trade is being processed for.'

End Group: OnBehalfOf.model
<asOfDate> IdentifiedDate </asOfDate> [0..1]

'The date for which this document reports positions and valuations.'

<dataSetName> xsd:string </dataSetName> [0..1]

'The name of the data set (portfolio, product type, etc.) that this report corresponds to. Used to help document the contents of the report.'

<reportContents> ReportContents </reportContents> [0..1]

'The specific characteristics included in the report.'

<quotationCharacteristics> QuotationCharacteristics </quotationCharacteristics> [0..1]

'The default quotation characteristics for this document (e.g. currency, location). Currency must be specified; other fields may be specified.'

<fromDateTime> xsd:date </fromDateTime> [0..1]

'The starting point for reporting activity in this report.'

<toDateTime> xsd:date </toDateTime> [0..1]

'The ending point for reporting activity in this report.'

<submissionsComplete> xsd:boolean </submissionsComplete> [0..1]

'Indicates whether all portfolio updates have been submitted for this as-of date'

<positionUpdate> PositionUpdate </positionUpdate> [0..*]

'The positions included in the position report.'

<party> Party </party> [0..*]

'A legal entity or a subdivision of a legal entity.','Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.'

<account> Account </account> [0..*]

'Optional account information used to precisely define the origination and destination of financial instruments.'

</positionActivityReport>
Diagram
Schema Component Representation
<xsd:element name="positionActivityReport" type=" PositionActivityReport "/>