Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide > Configuring Common Components of the Siebel Customer-Centric Enterprise Warehouse >

Configuring Loads

The Siebel Customer-Centric Enterprise Warehouse prepackages load mappings for every data warehouse table. Within each load mapping, every input and output port for each extension column is already connected. Thus, if you connect new data to a staging table's extension column using the extract mapping, the default configuration pulls that data through all the load mapping's components and inserts it into the corresponding data warehouse table. However, because the load mapping does not transform data in extension columns, you may need to reconfigure the load mapping to do so. Each of the following sections describes potential configuration approaches:

• Deriving a metric or attribute from other attributes in other staging tables

  If you are going to derive a new metric or attribute from other metrics, attributes, or both in other staging tables, then you need to join all staging tables that contain the data you need. You can join these tables in the load mapping, using the Source Qualifier. For information on how to join tables in the Staging Area, see Joining Objects in the Staging Area.

• Performing calculation transformations

  It is recommended that you modify the Expression transformation to perform calculation transformations in the Source Adapter mapplet.

• Performing a lookup override at the session-level

  If you want to store an additional domained attribute, and you stored the code and code name in the IA_CODES table, then you need to modify the load session's lookup. You have to modify the SQL statement to look up the code using the correct category. This lookup returns the appropriate code name from the IA_CODES table, and the ADI loads both the supplied code and the lookup code name into the target table.

• Resolving currency conversion issues

  If you are storing amount metrics, you only need to supply the amounts in one of the three currencies—document, local, or group currency. By loading one of these three values, the ADI contains logic for deriving the other two. For more information on potential configuration points with currency, see Process for Configuring Currencies. For more information on how each of the three types of currency is handled by the ADI, see About Document, Local, and Group Currencies.