Documentation for Financial products Markup Language (FpML®)
Definition Type: ComplexType
Name: PackageHeader
Namespace: http://www.fpml.org/FpML-5/reporting
Containing Schema: fpml-business-events-5-10.xsd
Abstract
Documentation:
Identifying information for a tradePackage (a bundle of trades).
Collapse XSD Schema Diagram:
Drilldown into packageInformation in schema fpml-business-events-5-10_xsd3 Drilldown into originatingEvent in schema fpml-business-events-5-10_xsd3 Drilldown into size in schema fpml-business-events-5-10_xsd3 Drilldown into packageType in schema fpml-business-events-5-10_xsd3 Drilldown into orderIdentifier in schema fpml-business-events-5-10_xsd3 Drilldown into packageIdentifier in schema fpml-business-events-5-10_xsd3XSD Diagram of PackageHeader in schema fpml-business-events-5-10_xsd3 (Financial products Markup Language (FpML®))
Collapse XSD Schema Code: 
<xsd:complexType name="PackageHeader">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">Identifying information for a tradePackage (a bundle of trades).</xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
        <xsd:element name="packageIdentifier" type="IssuerTradeId" minOccurs="0" />
        <xsd:element name="orderIdentifier" type="OrderIdentifier" minOccurs="0" />
        <xsd:element name="packageType" type="PackageType" minOccurs="0" maxOccurs="unbounded">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Classification of the package. FpML has defined a list of coding scheme values. Different organizations might have different naming schemes for the packages so the multiplicity of unbounded is meant to support synonyms but it does not mean that a trade has multiple package types.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="size" type="PositiveDecimal" minOccurs="0" />
        <xsd:element name="originatingEvent" type="OriginatingEvent" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">This may be used to describe why a package was created. This can be used to provide context for a newly created package that is not part of a post-trade event. For example, it can report that the package was created as a result of netting activity, or due to a transfer, an allocation process, etc.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="packageInformation" type="PackageInformation" minOccurs="0" />
    </xsd:sequence>
</xsd:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
packageIdentifier nsE:packageIdentifier 0 (1)
orderIdentifier nsE:orderIdentifier 0 (1)
packageType nsE:packageType 0 unbounded
size nsE:size 0 (1)
originatingEvent nsE:originatingEvent 0 (1)
packageInformation nsE:packageInformation 0 (1)
Collapse Derivation Tree:
Collapse References:
nsE:packageHeader
Documentation for Financial products Markup Language (FpML®)

Generated using Liquid Studio - Developer Bundle 21.0.0.0