element <onBehalfOf> (local)
Namespace:  | 
 | 
Type:  | 
 | 
Content:  | 
complex, 2 elements  | 
Defined:  | 
 | 
XML Representation Summary  | 
<onBehalfOf>  | 
     | 
 | 
</onBehalfOf>  | 
Content model elements (2):
- 
 
Included in content model of elements (63):
- 
cancelTradeCashflows, 
collateralAcceptanceAcknowledgement, 
collateralAllocationReport, 
collateralProposalStatus, 
creditEventAcknowledgement, 
creditEventNotification, 
creditEventNotificationRetracted, 
disputeAcknowledgement, 
disputeNotification, 
disputeRetracted, 
eventActivityReport, 
eventActivityReportAcknowledgement, 
eventStatusResponse, 
exposureReport, 
exposureReportAcknowledgement, 
interestStatement, 
interestStatus, 
interestStatusRetracted, 
marginAcknowledgement, 
marginCallStatus, 
marginCallStatusRetracted, 
nettedTradeCashflowsAcknowledgement, 
nettedTradeCashflowsAsserted, 
nettedTradeCashflowsMatchResult, 
nettedTradeCashflowsRetracted, 
nonpublicExecutionReport, 
nonpublicExecutionReportAcknowledgement, 
nonpublicExecutionReportRetracted, 
partyReport, 
partyReportAcknowledgement, 
positionActivityReport, 
positionActivityReportAcknowledgement, 
positionReport, 
positionReportAcknowledgement, 
positionsAcknowledged, 
positionsMatchResults, 
requestCollateralAcceptance, 
requestEventStatus, 
requestInterest, 
requestInterestRetracted, 
requestMargin, 
requestMarginRetracted, 
requestPositionReport, 
requestRetransmission, 
requestSubstitution, 
requestSubstitutionRetracted, 
requestValuationReport, 
resetReport, 
resetReportAcknowledgement, 
returnConfirmationStatus, 
serviceNotification, 
substituteConfirmationStatus, 
substitutionStatus, 
substitutionStatusRetracted, 
terminatingEventsReport, 
terminatingEventsReportAcknowledgement, 
tradeCashflowsAsserted, 
tradeCashflowsMatchResult, 
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)