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

Codes Lookup

Some source systems use intelligent codes that are intuitively descriptive, such as HD for hard disks, while other systems use nonintelligent codes (like numbers, or other vague descriptors), such as 16 for hard disks. While codes are an important tool with which to analyze information, the variety of codes and code descriptions used poses a problem when performing an analysis across source systems. The lack of uniformity in source system codes must be resolved to integrate data for the Siebel Customer-Centric Enterprise Warehouse.

The code lookup in the ADI integrates both intelligent and nonintelligent codes by performing a separate extract for codes, and inserting the codes and their description into a codes table. The codes table provides the ADI with a resource from which it can automatically perform a lookup for code descriptions.

The Analytic Data Interface's architecture uses components, as well as both fact and dimension tables, to facilitate lookup functionality. The following components and process are used in a lookup:

IA_CODES Table

The load control table IA_CODES consolidates all codes for future reference and assigns them a category and a single language for efficient lookup capability.

Codes Mappings

The Siebel Customer-Centric Enterprise Warehouse uses mappings designed to extract codes from source systems and populate the IA_CODES table in preparation for use by the ADI.

To understand how codes mappings function, it is helpful to first understand the columns within IA_CODES. Table 22 describes these columns.

The naming convention for mappings designed for codes lookup is M_[SOURCE]_CODES_[CATEGORY]. Figure 30 shows an example of a code mapping in PowerCenter Mapping Designer.

Figure 30. Sample Codes Mapping: M_S_CODES_REGION

Codes Mapplets

There are several mapplets that support the codes mappings in preparation for the source-independent ADI. They are as follows:

• Source Adapter mapplets. The Source Adapter mapplet connects the source-specific input attributes of CODES and the attributes from control or warehouse tables to the expression transform for mapping them. The naming convention for the Source Adapter codes mapplet is MPLT_SA[Source Abbreviation]_CODES.
• Business Component mapplets. The Business Component mapplet makes the source system attributes of CODES_CUST_CLASS available to the extract mapping. The naming convention for the Business Component codes mapplet is MPLT_BC[Source Abbreviation]_CODES_[CATEGORY].
• ADI Mapplet. The Analytic Data Interface (ADI) mapplet is source system independent and resolves the codes for the target table. The naming convention for the ADI codes mapplet is MPLT_ADI_CODES.

The ADI integrates multiple source system codes by designating one source system instance as a master in a mapping. All other source system codes are then mapped to the master. When the ADI encounters a code that requires definition, it references the load control lookup table to match the source system code to a Siebel Customer-Centric Enterprise Warehouse source-independent code, which retains all the source system codes' original functionality.

The following columns are used to designate a source system instance as the master source system:

• MASTER_ID. Code for the source system designated as master.
• SOURCE_ID. Unique identifier for the source system.