Editing the Operational Reporting model

You can review the conditions for editing the Operational Reporting model.

Ensure that you have downloaded the sample Operational Reporting Model before you get started. For more information, see Downloading the sample Operational Reporting Model.

The downloaded SMCF-Analytics.cpf must be opened by using Cognos® Framework Manager.

Following are conditions for editing the Operational Reporting model:

• Limited local processing should not be used during development unless absolutely necessary. This enforces the practice of pushing all operations down to the database, as opposed to pushing them to memory.
• Views should not be used unless all the following conditions are met:
  • All tables in the view are in the same schema type, and will be for the foreseeable future.
  • All tables in the view are necessary; that is, there is no "might use" data (example, Mark For Key on YFS_ORDER_HEADER).
  • Either one of the following conditions are met:
    • The view is meant to be used as a stepping stone for query subjects and has complex calculations.
    • There is a combination of unions and group by in some inventory use cases.

    Some views may still be necessary as group by is not always enforced as expected within Cognos, due to the aggregation logic it adds on its own.

• All Query Subjects to be used in other query subjects should have their relationships created manually with Filters. Columns and tables not directly referenced may be "optimized" out of the SQL. Using Filters prevents this.
• Filters should be created for the organization code and other cross-schema columns on the query subjects. The filter can contain the prompt. This pushes a where clause down to the individual schema. For example, by filtering enterprise code on order header, only orders from the enterprise will be read into memory.
• All filters should be created at the same level as relationships.