Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt

Use this file to discover all available pages before exploring further.

The TRANCHE_OVERRIDES table contains the Override definitions for the Tranches.
Column NameTypeNot Null
TRANCHESTRINGY
RISK_CLASSSTRINGY
PARAMETER_SETSTRINGY
BUCKETSTRING
SENIORITYSTRING
RATINGSTRING
TYPESTRING
REGIONSTRING
ASSET_CLASSSTRING
ATTACHMENTDOUBLE
DETACHMENTDOUBLE
RISK_WEIGHTDOUBLE
AS_OF_DATEDATEY

Unique Key

Columns
TRANCHE
RISK_CLASS
PARAMETER_SET
AS_OF_DATE

Override Base Table

The base table for these overrides is the Tranche table. To define Overrides you must add facts to the base table. For details on why this is required, see Overrides With DirectQuery.

Inject Base Table

For each override, you must generate multiple entries in the Tranche table with the following structure.
Override Table
PARAMETER_SET
BUCKET
CSRQUALITY
CSRSECTOR
CSRRATING
EQUITY_MARKET_CAP
EQUITY_ECONOMY
EQUITY_SECTOR
POOL
ATTACHMENT
DETACHMENT
These fields form an intermediate table containing the Override’s base store fields and will be merged back into the Override base table: Tranche.

Map Override Fields to Base Table Fields

Once you create your tuples for each override field, you can then map the tuples back to the base store using the following relationship:
Override TableTranche FieldNote
OVERRIDE KEY FIELDTRANCHE
OVERRIDE DATE FIELDAS_OF_DATE
PARAMETER_SETNo mapping exists
BUCKETBUCKET
SENIORITYSENIORITY
RATINGRATING
TYPETYPE
REGIONREGION
ASSET_CLASSASSET_CLASS
ATTACHMENTATTACHMENT
DETACHMENTDETACHMENT
RISK_WEIGHTRISK_WEIGHT
RISK_CLASSNo mapping exists