ExecutionDetails
Type CDM 7.2.0Defines specific attributes that relate to trade executions.
Extends —
Extended by —
Attributes 3
Namespace cdm.event.common
Attributes
All 3 declared on ExecutionDetails. Cardinality in amber is required.
| Name | Type | Card. | Description |
|---|---|---|---|
| executionType | ExecutionTypeEnum | 1..1 | Identifies the type of execution, e.g. via voice, electronically... |
| executionVenue | LegalEntity | 0..1 | Represents the venue on which a trade was executed. |
| packageReference | IdentifiedList | 0..1 | A reference to the package linking the trade with other trades, in case the trade was executed as part of a package (hence this attribute is optional). |
Conditions
Validation rules the model enforces on this type, in Rune. An instance that breaks one of these is invalid CDM, whatever produced it.
ExecutionVenue Condition
When the execution type is set to 'Electronically', the execution venue must be specified.
if executionType = ExecutionTypeEnum -> Electronic
then executionVenue existsReferenced by
3 types hold an ExecutionDetails as an attribute.
Functions
Model functions that produce or consume this type. These are the CDM's own behaviour — the logic a correct implementation has to match.
| Function | Role | Description |
|---|---|---|
| Create_PackageExecutionDetails | returns | Add a package component to an execution details object. This package component is constructed using an identifier for the package and the list of identifiers for its components. |
| EmptyExecutionDetails | returns | — |
| MapExecutionDetails | returns | — |
| Create_PackageExecutionDetails | takes | Add a package component to an execution details object. This package component is constructed using an identifier for the package and the list of identifiers for its components. |
Open ExecutionDetails in the Model Browser
Walk the tree and the reference graph interactively, and switch releases to see how the type has changed. Free, no signup.