5.1.5 Setting up Dimension Loader
FSI_DIM_LOADER_SETUP_DETAILS table should have record for each dimension that has to be loaded using the dimension loader. The table contains seeded entries for key dimensions that are seeded with the application.
The following are sample entries in the setup table:
| Column Name | Description | Sample Value |
| n_dimension_id | This stores the Dimension ID | 1 |
| v_intf_b_table_name | Stores the name of the Staging Base table | Stg_org_unit_b_intf |
| v_intf_member_column | Stores the name of the Staging Member Column Name | V_org_unit_id |
| v_intf_tl_table_name | Stores the name of the Staging Translation table | Stg_org_unit_tl_intf |
| v_intf_attr_table_name | Stores the name of the Staging Member Attribute table | Stg_org_unit_attr_intf |
| v_intf_hier_table_name | Stores the name of the Staging Hierarchy table | Stg_org_unit_hier_intf |
| d_start_time | Start time of loader - updated by the loader program. | |
| d_end_time | End time of loader - updated by the loader program. | |
| v_comments | Stores Comments. | Dimension loader for organization unit. |
| v_status | Status updated by the Loader program. | |
| v_intf_member_name_col | Stores the name of the Member | V_org_unit_name |
| v_gen_skey_flag | Flag to indicate if surrogate key needs to be generated for alphanumeric codes in the staging. Applicable only for loading dimension data from master tables. Not applicable for loading dimension data from interface tables. Note: Although the application UI may display an alphanumeric dimension member ID, the numeric member ID is the value stored in member-based assumption rules, processing results, and audit tables.Implications for Object Migration: Numeric dimension member IDs should be the same in both the Source and Target environments, to ensure the integrity of any member-based assumptions you wish to migrate. If you use the Master Table approach for loading dimension data and have set it up to generate surrogate keys for members, this can result in differing IDs between the Source and Target and therefore would be a concern if you intend to migrate objects which depend on these IDs. | |
| v_stg_member_column | Name of the column that holds member code in the staging table. Applicable for loading dimension data from the master tables. (sample value v_org_unit_code) –this appears to be the alphanumeric code | v_org_unit_code v_gl_code v_common_coa_code v_prod_code v_entity_code v_party_id |
| v_stg_member_name_col | Name of the column that holds member name in the staging table. Applicable only for loading dimension data from master tables. Not applicable for loading dimension data from interface tables. | |
| v_stg_member_desc_col | Name of the column that holds description in the staging table. Applicable only for loading dimension data from master tables. Not applicable for loading dimension data from interface tables. | |
| v_stg_intf_member_column | Name of the column that holds member code in the staging table. Applicable for loading dimension data only from the interface tables. | v_org_unit_code v_gl_code v_common_coa_code v_prod_code v_lv_code v_cust_ref_code |
Note:
Ensure FSI_DIM_LOADER_SETUP_DETAILS.V_STG_MEMBER_COLUMN is updated as mentioned following for Legal Entity and Customer dimensions.
| Dimension Loader Approach | V_STG_MEMBER_COLUMN for Legal Entity | V_STG_MEMBER_COLUMN for Customer |
| Using Interface Table (fn_drmDataLoader) | V_LV_CODE | V_CUST_REF_CODE |
| Using Master Table (fn_STGDimDataLoader) | V_ENTITY_CODE | V_PARTY_ID |