Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide > Deploying Multiple Siebel Customer-Centric Enterprise Warehouse Applications >

Configuring Nonmutually Exclusive Source Systems for Incremental Deployment

For applications such as Siebel Enterprise Sales Analytics (Oracle 11i) and Siebel Enterprise Contact Center Analytics (universal source), there are common dimensions, for example, Customers, Products and so on. You need to choose the master source for each common dimension. For application specific dimensions, for example, Sales Status for Sales, it is not necessary to choose a master source.

It is not necessary to select a master source for fact tables. However, for fact tables that refer to common dimensions (for example, Customers or Products), you need to take necessary care to so that they resolve correctly against the correct dimension. The <DIMENSION>_ID column in the fact table must be formed correctly so that it matches with the format of the KEY_ID column for the corresponding dimension. These changes are normally carried out in the Source Adapter mapplets of the fact table being loaded.

To configure nonmutually exclusive source systems

1. Import both the applications into a new repository.

   For more information on importing applications into a repository, see About the Incremental Deployment of the Siebel Business Analytics Repository.

2. Create multi-application Post Load Initial and Post Load Incremental workflows.

   For more information on building multi-application workflows, see Process of Building Multi-Application Workflows for the Siebel Business Analytics.

   For example, for Siebel Enterprise Sales Analytics (Oracle 11i) and Siebel Enterprise Contact Center Analytics (universal source), create workflows called PLP_EnterpriseSales_ContactCenter_Application_INIT and PLP_EnterpriseSales_ContactCenter_Application_INCR.

3. Identify the tables used in both applications, and for each table, identify the main source system, for example, Oracle 11i.
4. Disable the dimension extract and load sessions in the application workflow.

   For example, for Siebel Enterprise Sales Analytics (Oracle 11i), disable the dimension extract and load sessions in the ORACLE11i_EnterpriseSales_Application workflow, for the tables you are loading from the Oracle 11i source system.

   For Siebel Enterprise Contact Center Analytics (universal source), disable the dimension extract and load sessions in the Universal_EnterpriseContactCenter_Application workflow for the tables you are loading from the Oracle 11i source system.

5. Change the PARM_SVALUE_2 column value in the source system parameter file.

   For example, for the file_parameters_ora11i.csv parameters file, change the PARM_SVALUE_2 column value from OAP11I to SLS_ECC. For the file_parameters_univ.csv parameters file, change the PARM_SVALUE_2 column value from GENERIC to SLS_ECC.

   NOTE:  You must not change the preconfigured values of ORA11I and UNIV for the PARM_TYPE and SOURCE_ID columns.

   For Siebel Contact Center Analytics you need to also run the Universal_All_Applications_Common_Initialize workflow once. This workflow loads Siebel Customer-Centric Enterprise Warehouse domain values—IA_STATUS, IA_EVENT_TYPES and IA_CHNL_TYPES. You can load these domain values through your universal source system.

6. Start the application workflows.

   For example, for a full ETL load for Siebel Enterprise Sales Analytics (Oracle 11i) and Siebel Enterprise Contact Center Analytics (universal source), run the following workflows:

   1. INITIALIZE workflow in the Siebel Applications folder.
   2. ORACLE11i_EnterpriseSales_Application workflow in the Configuration for Oracle Applications v11i folder.
   3. Universal_All_Applications_Common_Initialize workflow in the Configuration for Universal Source folder.
   4. Universal_EnterpriseContactCenter_Application workflow in the Configuration for Universal Source folder
   5. PLP_EnterpriseSales_ContactCenter_Application_INIT in the Configuration for Post Load Processing folder.

      This workflow is created in Step 2.

7. Change the source system parameter files, file_parameters_ora11i.csv and file_parameters_univ.csv, and provide an incremental value in the PARM_NVALUE_1 column.

   For more information on modifying session parameters for parameter files, see About Modifying Session Parameters for Initial and Incremental Loads.

8. Start the incremental ETL runs.

   For example, for an incremental ETL load for Siebel Enterprise Sales Analytics (Oracle 11i) and Siebel Enterprise Contact Center Analytics (universal source), run the following workflows:

   1. ORACLE11i_EnterpriseSales_Application workflow in the Configuration for Oracle Applications v11i folder.
   2. Universal_EnterpriseContactCenter_Application workflow in the Configuration for Universal Source folder.
   3. PLP_EnterpriseSales_ContactCenter_Application_INCR in the Configuration for Post Load Processing folder.

      This workflow is created in Step 2.