14.6.1 Error Messages

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