Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide > Initializing and Populating the Siebel Customer-Centric Enterprise Warehouse >

About the Source-Specific Main Workflows

This section allows you to prepare your source-specific main workflow so that it meets your implementation requirements. In this source-specific main workflow, the Siebel Business Analytics provide you with the logic to extract all the data from a particular source system. Depending on your source system, the workflow contains worklets for each Siebel Business Analytics product.

You may want to remove some worklets that are not part of your implementation, depending on the module or product family you want to use. After configuring your main workflow, run it to capture your first, complete extraction of all the rows in your source database. The result provides you with a populated target schema that you can use for further configuration.

Most of the source-specific main workflows that you see in the Navigation window of the Workflow Manager contain nested worklets.

These usually include:

• Prepare worklet
• Fact extract worklet
• Dimension extract worklet
• Dimensions load worklet
• Facts load worklet
• Execution finished worklet

About Choosing Which Rows To Keep in the Data Warehouse

The purpose of the primary extract sessions is to track any physical deletions that occur in the source system. Primary extract sessions do not perform a full data extract; they extract only the KEY_ID and SOURCE_ID for facts. The delete sessions delete the rows that are in the data warehouse.

If rows are physically removed from your source system, you must make a choice about retaining the rows in your data warehouse:

• If you want to retain the rows in the data warehouse even though the rows are removed from the source system, then keep the default primary extract sessions, and the corresponding delete session disabled.
• If you do not want to retain the rows in the data warehouse after they are removed from the source system, then enable the default primary extract sessions, and the corresponding delete session.
• If your source system archives rows, you may want to set a parameter to search for archive dates, and then execute the delete session only on rows that have been archived and are no longer needed in the warehouse. See the discussion on deletion configuration for source-archived records, in About Working with Primary Extract and Delete Mappings.
• The PRE_D sessions for aggregate tables are disabled. If you enable the primary extract sessions and the corresponding delete sessions, you should also enable the corresponding PRE_D sessions.