17.1 Overview
Note:
The details about populating the tier 1 capital component from the Basel table are mentioned below. If you do not have the Basel license, then you can populate the table via script and have the value flow through to Table B.Tier 1 Capital for reporting periods T and T-1 must be designated and reported. Currently, this value should be reported by the Basel capital application fact table:
FCT_REG_LE_CAPITAL_SUMMARY.N_AMOUNT_POST_REG_ADJUSTMENT
If the Basel capital fact table is not licensed, then the tier 1 capital value must be manually loaded into the reporting table via SQL command. The target table is FCT_REG_LE_CAPITAL_SUMMARY and its fields are as follows:
Table 17-1
Column Name | Data Type | Nullable | PK | FK |
---|---|---|---|---|
N_ENTITY_SKEY | NUMBER(10) | No | Yes | No |
N_REP_LINE_SKEY | NUMBER(10) | No | Yes | No |
N_GAAP_SKEY | NUMBER(10) | No | Yes | No |
N_LEV_RATIO_DED_GROUP_SKEY | NUMBER(5) | Yes | No | No |
N_CAPITAL_COMP_GROUP_SKEY | NUMBER(10) | No | Yes | No |
V_RCY_CODE | VARCHAR2(3) | Yes | No | No |
N_COUNTRY_SKEY | NUMBER(10) | Yes | No | No |
N_LOB_SKEY | NUMBER(10) | Yes | No | No |
N_AMOUNT_PRE_REG_ADJUSTMENT | NUMBER(22,3) | Yes | No | No |
N_AMOUNT_POST_REG_ADJUSTMENT | NUMBER(22,3) | Yes | No | No |
F_NON_QUALIFIED_CAP_INSTR_FLAG | CHAR(1) | Yes | No | No |
N_FORECAST_DATE_SKEY | NUMBER(10) | No | Yes | No |
V_SCENARIO_CODE | VARCHAR2(20) | No | Yes | No |
N_MIS_DATE_SKEY | NUMBER(10) | No | Yes | Yes |
N_RUN_SKEY | NUMBER(10) | No | Yes | Yes |
N_BRANCH_SKEY | NUMBER(10) | Yes | No | Yes |
The T1 Capital amount should be entered into the field N_AMOUNT_POST_REG_ADJUSTMENT with the following constraints:
- N_REP_LINE_SKEY = 8110000637
- V_CAP_COMP_GROUP_CODE = ‘OTH’
- V_SCENARIO_CODE should be defaulted to the users’ ‘Baseline’ forecast scenario ID
- N_FORECAST_DATE_SKEY should be defaulted to ‘999991231’