AssetFlowBase
Type CDM 7.2.0Defines the basic parameters of an asset transfer, e.g. a cashflow: what (the asset), how much (the quantity) and when (the settlement date).
Attributes
All 4 declared on AssetFlowBase. Cardinality in amber is required.
| Name | Type | Card. | Description |
|---|---|---|---|
| quantity | NonNegativeQuantity | 1..1 | Represents the amount of the asset to be transferred. The cashflow amount is always a positive number, as the cashflow direction is implied by the payer/receiver attribute. |
| asset | Asset | 1..1 | Represents the object that is subject to the transfer, it could be an asset or a reference. |
| settlementDate | AdjustableOrAdjustedOrRelativeDate | 1..1 | Represents the date on which the transfer to due. |
| paymentDiscounting | PaymentDiscounting | 0..1 | FpML specifies the FpML PaymentDiscounting.model group for representing the discounting elements that can be associated with a payment. |
Conditions
Validation rules the model enforces on this type, in Rune. An instance that breaks one of these is invalid CDM, whatever produced it.
QuantityUnitExists Condition
Aligns the type of unit and the type of asset.
if asset as Cash exists
then quantity -> unit -> currency exists
else if asset as Commodity exists
then quantity -> unit -> capacityUnit exists
else if asset as Instrument exists
then quantity -> unit -> financialUnit existsOpen AssetFlowBase 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.