Data Model objects: Parameter Maps

The Sterling™ Order Management System Software supports multiple schemas in an installation, separated by both table type (Configuration and Transaction), and Enterprise code. This multiple schema implementation of Analytics requires that you select tables from the correct schema.

A IBM® Cognos® Analytics datasource for each schema facilitates this. The schema is then dynamically selected from the report via the Enterprise selection screen shown in Figure 1.

Within the Framework Manager, there are four data sources, based on type of schema: Configuration, Metadata, MasterData, and Transaction. Data sources within Framework Manager are like pointers to the true data sources defined within Cognos Connection. Database query subjects are hard coded with one of these four schemas. For Release 9.2, the Transaction and MasterData data sources will point to the same schema.

The parameter map shown in Figure 1 enables you to define a prompt. The key that is associated with that prompt will be required for input in reports; it will be used when an Enterprise is selected in a report.

Figure 1. Parameter Map
The parameter map screen where a key and a value for that key are defined.

The input will then be consumed by other parameter maps that map Enterprise code to datasource and schema. Parameter maps can be nested like this, with the value of one map becoming the key to the next.

This parameter map would be configured in Analytics as pictured:

Figure 2. Analytics Map
A parameter map for Cognos, displaying the Properties tab.

The prompt that is defined in the parameter map is put into reports. Prompts defined in Framework Manager can be reused in IBM Cognos Report Studio.

This feature does not support cross-schema unions. All reports are enterprise specific.