Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide > Integrating Additional Data > Table Formats >

Staging Table Format

Unlike the other tables that are created in the Siebel Business Analytics folder, the staging tables are source-dependent and are created in the prepackaged source-specific configuration folders in the PowerCenter Repository. These tables have the following requirements:

• The default database for staging tables is DB2, however you may change this value as necessary. The primary key for staging tables is a composite of the KEY_ID and SOURCE_ID.
• The naming convention for staging tables is T[SOURCE]_[NAME].
• For Oracle 11i, the staging table is TI_USERS.

The purpose of the staging tables is to speed data extraction by temporarily storing extracted source data that are transformed in an Expression transformation in preparation for the source-independent Siebel Customer-Centric Enterprise Warehouse. Therefore, the order of the columns, and contents is determined by the corresponding source data.

For example, in the staging table TO_USERS, the first eight columns contain attributes about user information, some of which include CREATED_BY, LAST_UPDATED_BY, USER_NAME, and EMAIL_ADDR, and so on, and which are then followed by extension columns and the last two control columns that comprise the primary key, the KEY_ID and the SOURCE_ID.

In contrast, TS_USERS, which is the staging table for user information in SAP, has several columns containing attribute information about users including DEPARTMENT_CODE, DELEGATEE_NAME, REGION_CODE, and LANGUAGE_CODE. The only significant similarities are that the attributes are followed by extension columns and that the primary key is usually a composition of KEY_ID and SOURCE_ID columns. Sometimes, however, the primary key also includes the effective date for the record.