The OBLIGOR_OVERRIDES table contains the Override definitions for the Obligor table.
Column Name
Type
Not Null
OBLIGOR_ID
STRING
Y
RISK_CLASS
STRING
Y
PARAMETER_SET
STRING
Y
OBLIGOR_CATEGORY
STRING
RATING
STRING
RISK_WEIGHT
DOUBLE
DRC_FUND_TREATMENT
STRING
AS_OF_DATE
DATE
Y
Unique Key
Columns
OBLIGOR_ID
RISK_CLASS
PARAMETER_SET
AS_OF_DATE
Override Base Table
The base table for these overrides is the Obligor 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 Obligor table with the following
structure.
Override Parameter
Obligor Table Field
OVERRIDE KEY FIELD
OBLIGOR_ID
OVERRIDE DATE FIELD
AS_OF_DATE
Where:
Override Parameter: The parameters to determine where to apply this override.
Obligor Table Field: The field in the Obligor base table for this override.
Create Base Store Tuples
See the Create Override Tuples section for
an example of how to create the override tuples for the following override fields. These are the fields we want to override in the base override table, in
this case the Obligor Table.
Override Table
PARAMETER_SET
OBLIGOR_CATEGORY
RATING
RISK_WEIGHT
DRC_FUND_TREATMENT
These fields form an intermediate table containing the Override’s base store fields and will be merged back into the Override base table: Obligor.
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: