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 (68):
-
allocationAcknowledgement,
allocationApproved,
allocationRefused,
approvalStatusNotification,
clearingAcknowledgement,
clearingConfirmed,
clearingEligibility,
clearingEligibilityAcknowledgement,
clearingRefused,
clearingStatus,
collateralAllocationAccepted,
collateralAllocationAcknowledgement,
confirmationAcknowledgement,
confirmationAgreed,
confirmationDisputed,
confirmationStatus,
consentAcknowledgement,
consentGranted,
consentRefused,
creditEventAcknowledgement,
creditEventNotification,
creditEventNotificationRetracted,
dealStatement,
eventStatusResponse,
executionAcknowledgement,
executionAdvice,
executionAdviceAcknowledgement,
executionAdviceRetracted,
executionNotification,
executionRetracted,
facilityNotification,
facilityPositionStatement,
facilityStatement,
lcNotification,
loanAllocationNotification,
loanBulkServicingNotification,
loanContractNotification,
loanNotificationAcknowledgement,
loanNotificationRetracted,
loanPartyProfileStatement,
loanTradeNotification,
maturityAcknowledgement,
maturityNotification,
optionExpirationNotification,
outstandingContractsStatement,
requestAllocation,
requestAllocationRetracted,
requestClearing,
requestClearingEligibility,
requestClearingRetracted,
requestCollateralAllocation,
requestConfirmation,
requestConfirmationRetracted,
requestConsent,
requestConsentRetracted,
requestEventStatus,
requestExecution,
requestExecutionRetracted,
requestRetransmission,
requestTradeReferenceInformationUpdate,
requestTradeReferenceInformationUpdateRetracted,
serviceNotification,
tradeChangeAdvice,
tradeChangeAdviceAcknowledgement,
tradeChangeAdviceRetracted,
tradeReferenceInformationUpdateAcknowledgement,
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. 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.
XML Source (w/o annotations (1); see within schema source)