Definition Type: Element
Name: onBehalfOf
Namespace: http://www.fpml.org/FpML-5/pretrade
Type: nsA:OnBehalfOf
Containing Schema: fpml-shared-5-9.xsd
MinOccurs 0
MaxOccurs 4
Abstract
Documentation:
Indicates which party (or parties) (and accounts) a trade or event is being processed for. Normally there will only be a maximum of 2 parties, but in the case of a novation there could be a transferor, transferee, remaining party, and other remaining party. Also, in the context of a trade package there could be several parties for which limit check is requested, necessitating multiple onBehalfOf elements. Except for these cases, there should be no more than two onBehalfOf references in a message.
Collapse XSD Schema Diagram:
Drilldown into accountReference in schema fpml-shared-5-9_xsd Drilldown into partyReference in schema fpml-shared-5-9_xsd Drilldown into OnBehalfOf in schema fpml-shared-5-9_xsdXSD Diagram of onBehalfOf in schema fpml-shared-5-9_xsd (Financial products Markup Language (FpML®) - Pretrade)
Collapse XSD Schema Code:
<xsd:element name="onBehalfOf" type="OnBehalfOf" minOccurs="0" maxOccurs="4">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">Indicates which party (or parties) (and accounts) a trade or event is being processed for. Normally there will only be a maximum of 2 parties, but in the case of a novation there could be a transferor, transferee, remaining party, and other remaining party. Also, in the context of a trade package there could be several parties for which limit check is requested, necessitating multiple onBehalfOf elements. Except for these cases, there should be no more than two onBehalfOf references in a message.</xsd:documentation>
    </xsd:annotation>
</xsd:element>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
partyReference nsA:partyReference 0 (1)
accountReference nsA:accountReference 0 unbounded
Collapse Derivation Tree:
Collapse Comments:
blog comments powered by Disqus