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