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 (48):
-
allocationAcknowledgement,
allocationApproved,
allocationRefused,
clearingAcknowledgement,
clearingConfirmed,
clearingRefused,
clearingStatus,
confirmationAcknowledgement,
confirmationAgreed,
confirmationDisputed,
confirmationStatus,
consentAcknowledgement,
consentGranted,
consentRefused,
creditEventAcknowledgement,
creditEventNotification,
creditEventNotificationRetracted,
eventStatusResponse,
executionAcknowledgement,
executionAdvice,
executionAdviceAcknowledgement,
executionAdviceRetracted,
executionNotification,
executionRetracted,
maturityAcknowledgement,
maturityNotification,
optionExpirationNotification,
requestAllocation,
requestAllocationRetracted,
requestClearing,
requestClearingRetracted,
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. 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)
