This chapter provides information about Customer Dimension table loading process in the Oracle Financial Services Data Foundation application.
This chapter includes the following topics:
· Customer Dimension Loading Overview
· Customer Dimension Population using Stage Party Master Entity
· Customer Dimension Population using Stage Customer Master Entity
· Execution of Customer Dimension Population Batch
The Customer Dimension populates DIM_CUSTOMER table by generating individual numeric Surrogate Keys for every customer reference code. This table will be used in Reporting by joining with other results tables.
The Customer Dimension can be populated from Stage Party Master Entity using the SCD packaged in FSDF with map ref number 335.
STG_PARTY_MASTER should be loaded with all records which are required STG_PARTY_ROLE_MAP should be loaded with all customer records and Party Role should be ‘CUSTOMER’.
The Customer Dimension can be populated from Stage Customer Master Entity using the SCD packaged in FSDF with map ref number 32.
STG_CUSTOMER_MASTER should be loaded with all records which are required.
Topics:
Customer Dimension SCD from Party Master can be executed by executing task present in the seeded batch FSDFINFO_DATA_FOUNDATION_SCD.
To execute the batch, follow these steps:
1. Navigate to the Batch Execution screen.
2. Select the seeded batch FSDFINFO_DATA_FOUNDATION_SCD.
3. Select the AS_OF_DATE for which source customer information is required to be loaded into the table.
4. Click Execute Batch.
5. Monitor the status of the batch from Batch Monitor screen of OFSAAI.
Following are the most common error message which will be logged in the T2T log file present in the ftpshare/logs/<Run_Date>/FSDFINFO/RUN EXECUTABLE folder:
· Unique Constraint Violation: This occurs when attempting re-load or loading existing records for the already executed AS_OF_DATE.
Customer Dimension SCD from Customer Master can be executed by executing task present in the seeded batch FSDFINFO_DATA_FOUNDATION_SCD.
To execute the batch, follow these steps:
1. Navigate to the Batch Execution screen.
2. Select the seeded batch FSDFINFO_DATA_FOUNDATION_SCD.
3. Select the AS_OF_DATE for which source customer information is required to be loaded into the table.
4. Click Execute Batch.
5. Monitor the status of the batch from Batch Monitor screen of OFSAAI.
Following are the most common error message which will be logged in the T2T log file present in the ftpshare/logs/<Run_Date>/FSDFINFO/RUN EXECUTABLE folder:
· Unique Constraint Violation: This occurs when attempting re-load or loading existing records for the already executed AS_OF_DATE.
NOTE:
Following are the two customer based dimensions that are used across various OFSAA applications for their processing and reporting requirements.
· DIM_PARTY
· DIM_CUSTOMER
In the earlier releases, both the dimensions sourced data from separate staging tables i.e. STG_PARTY_MASTER and STG_CUSTOMER_MASTER respectively. This design however enforced the population of customer data in both staging tables.
To address bug - Bug 20486362 - SCD TO POPULATE DIM_CUSTOMER FROM STG_PARTY_MASTER
TO BE ADDED, a new SCD (MAP_REF_NUM = 335) was introduced in FSDF release 8.0.1.0.0 to load DIM_CUSTOMER using STG_PARTY_MASTER and STG_PARTY_ROLE_MAP as the source. Customers, who use applications that have a dependence on DIM_PARTY, are advised to use this SCD instead of SCD, 32. Execute batch DIM_CUSTOMER_SCD_PARTY to populate DIM_CUSTOMER using STG_PARTY_MASTER and STG_PARTY_ROLE_MAP as the source. SCD, 32 will be deprecated in a future release. There are two flows available for DIM_CUSTOMER population. Only one need to be executed accordingly. Following are the two flows:
· Customer Dimension Population using Stage Party Master Entity
· Customer Dimension Population using Stage Customer Master Entity