Configure the data mart project

After you set up the ETL tool, the following configurations are made to restrict the data that is loaded into the data mart:
  • Defining a Catalog: You must determine a catalog for analytical purpose. Only items that belong to this catalog are considered for analysis.
  • Defining hold types for order hold analysis: The model that is shipped along with Business Intelligence consists of all the hold types, including the system-specific hold types. You can exclude specific hold types from the analysis.
  • Defining credit hold types for customer rating: For customer rating, it is recommended that you consider only credit hold types.
  • Modifying weights for customer rating.

A mapping document is provided along with Sterling™ Order Management System to enable you to build the data mart. You can use the mapping document as a reference to understand how data for each table in the data mart is retrieved from the staging database or from the runtime. The data mart mapping document is available at following location: <BI_COGNOS_HOME>\Exports\aw-export.

Two SQL scripts, Db2 Datamart.sql and Oracle Datamart.sql are also provided. These scripts can be run from an SQL interpreter and helps in creating schemas for the data mart. The SQL script for Db2 database creates a DataMart schema along with empty tables and the SQL script for Oracle database creates tables for the current user.

The project files from Cognos® Adaptive Warehouse are included in <BI_COGNOS_HOME>\Exports\aw-export\sterling data source export. These files can be used by InfoSphere® DataStage® or any other ETL tool of your choice to migrate the ETL scripts from Cognos Adaptive Warehouse to the new ETL tool.

If you are using InfoSphere DataStage to build the data mart, refer to IBM InfoSphere Information Server documentation for more information. If you are using any other ETL tool, refer to the corresponding product documentation for more information.