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

About Deploying Source Systems with Universal Source Systems for Incremental Deployment

The following section discusses the implementation of one or more applications from a specific source system (for example, SAP R/3, Oracle 11i, and PeopleSoft 8.4) with one or more applications using universal source. For example, if you implement Siebel Financial Analytics for Oracle 11i with Siebel Strategic Sourcing Analytics using universal source.

In a cross folder deployment environment, there are two possible scenarios:

• The data sources are mutually exclusive:
  • The dimensional data sources are exclusive. For example, if you have a data source for a Customers dimension in the Oracle 11i source system, you cannot have a similar data source in your universal source.
  • The dimensional data sources are partially exclusive. For example, you may have a data source for the Customers dimension in the Oracle 11i source system and in the universal source, but the list of customers in both of these sources are exclusive.
  • The dimensional data sources are partially exclusive and they can have data similarities. For example, you might have a data source for the Customers dimension in the Oracle source system and in the universal source, and some customers appear in both sources. You can decide to use these customers as different sources and load them separately into the common data warehouse.

    For more information on configuring mutually exclusive data sources, see Configuring Mutually Exclusive Source Systems for Incremental Deployment

• The data sources are not mutually exclusive.

  The dimensional data sources are partially exclusive and they can have data similarities. For example, you might have a data source for the Customers dimension in the Oracle source system and in the universal source, and some customers appear in both sources. You decide to join these customers to get a uniform view from your data warehouse.

  The assumption here is that one data source is a subset of the other data source. For example, the master list of customers are stored in Oracle 11i source system, whereas a subset of customers (for example, web customers) are stored in the universal source. You need to populate the data warehouse and analyze the data with the Oracle 11i source system.

  For more information on configuring nonmutually exclusive data sources, see Configuring Nonmutually Exclusive Source Systems for Incremental Deployment

For mutually exclusive data sources, you have a disjointed set of data loaded in the Siebel Customer-Centric Enterprise Warehouse. The entities in the Siebel Customer-Centric Enterprise Warehouse are separated by the value of Source ID (SOURCE_ID) column. The advantages of this separation are:

• You can query against a particular source system by including the SOURCE_ID column into your query filter.
• If you want to see the number of orders placed by a customer, you can add up the distinct orders grouping by the customer.
• There are no large changes in the Siebel Business Analytics metadata repository. The fact tables are connected to the dimension tables which are populated by the two distinct sources, and there are no conflicts to resolve the surrogate keys.

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