element <onBehalfOf> (local)

Namespace: | http://www.fpml.org/FpML-5/recordkeeping
Type: | OnBehalfOf
Content: | complex, 2 elements
Defined: | locally witnin OnBehalfOf.model group in fpml-shared-5-3.xsd; see XML source

Content Model Diagram

XML Representation Summary
<onBehalfOf>
Content: | partyReference?, accountReference*
</onBehalfOf>

Content model elements (2):

  accountReference (defined in OnBehalfOf complexType), | partyReference (defined in OnBehalfOf complexType)

Included in content model of elements (15):

  creditEventAcknowledgement, creditEventNotification, eventStatusResponse, nonpublicExecutionReport, nonpublicExecutionReportAcknowledgement, nonpublicExecutionReportRetracted, requestEventStatus, requestRetransmission, requestValuationReport, serviceNotification, valuationReport, valuationReportAcknowledgement, valuationReportRetracted, verificationStatusAcknowledgement, verificationStatusNotification

Annotation
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. Except for this case, there should be no more than two onABehalfOf references in a message.
XML Source (w/o annotations (1); see within schema source)

<xsd:element maxOccurs="4" minOccurs="0" name="onBehalfOf" type="OnBehalfOf"/>

XML schema documentation generated with DocFlex/XML 1.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.