> ## 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.

# RRAOOVERRIDES

The RRAOOVERRIDES table contains the Override definitions for RRAO categories.

| Column Name                 | Type   | Not Null |
| --------------------------- | ------ | -------- |
| RRAOCATEGORY                | STRING | Y        |
| RISK\_CLASS                 | STRING | Y        |
| PARAMETER\_SET              | STRING | Y        |
| RESIDUAL\_RISK              | STRING |          |
| EXOTIC\_UNDERLYING          | STRING |          |
| OTHER\_RESIDUAL\_RISK\_TYPE | STRING |          |
| AS\_OF\_DATE                | STRING | Y        |
| EXEMPTION\_REASON           | STRING | Y        |
| ASSET\_CLASS                | STRING | Y        |

## Unique Key

| Override Parameter      | **RRAO** Table Field |
| ----------------------- | -------------------- |
| **OVERRIDE KEY FIELD**  | **RRAOCATEGORY**     |
| **OVERRIDE DATE FIELD** | **AS\_OF\_DATE**     |

Where:

* **Override Parameter**: The parameters to determine where to apply this override.
* **RRAO Table Field**: The field in the [RRAO](./rrao) base table for this override.

### Create Base Store Tuples

See the [Create Override Tuples](../dev/dev-direct-query/customization-and-internals/overrides-with-directquery#create-the-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 [RRAO](./rrao) Table.

| Override Table              |
| --------------------------- |
| RESIDUAL\_RISK              |
| EXOTIC\_UNDERLYING          |
| OTHER\_RESIDUAL\_RISK\_TYPE |

These fields form an intermediate table containing the Override's base store fields and will be merged back into the Override base table: [RRAO](./rrao).

#### 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              | RRAO Field                  | Note              |
| --------------------------- | --------------------------- | ----------------- |
| OVERRIDE KEY FIELD          | RRAOCATEGORY                |                   |
| OVERRIDE DATE FIELD         | AS\_OF\_DATE                |                   |
| PARAMETER\_SET              |                             | No mapping exists |
| RESIDUAL\_RISK              | RESIDUAL\_RISK              |                   |
| EXOTIC\_UNDERLYING          | EXOTIC\_UNDERLYING          |                   |
| OTHER\_RESIDUAL\_RISK\_TYPE | OTHER\_RESIDUAL\_RISK\_TYPE |                   |
| EXEMPTION\_REASON           | EXEMPTION\_REASON           |                   |
| ASSET\_CLASS                | ASSET\_CLASS                |                   |
|                             | RISK\_CLASS                 | No mapping exists |