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 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
| Override Parameter | Obligor Table Field |
|---|
| OVERRIDE KEY FIELD | OBLIGOR_ID |
| OVERRIDE DATE FIELD | AS_OF_DATE |
- 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 |
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 Table | Obligor Table Field | Note |
|---|
| OVERRIDE KEY FIELD | OBLIGOR_ID | |
| OVERRIDE DATE FIELD | AS_OF_DATE | |
| PARAMETER_SET | | No mapping exists |
| OBLIGOR_CATEGORY | OBLIGOR_CATEGORY | |
| RATING | RATING | |
| RISK_WEIGHT | RISK_WEIGHT | |
| DRC_FUND_TREATMENT | DRC_FUND_TREATMENT | |
| RISK_CLASS | No mapping exists |
