Editing the Business Intelligence model

You can review the conditions for editing the Business Intelligence model.

Following are conditions for editing the Business Intelligence 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).
  • One of the following:
    • 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 bys (some inventory use cases)

    Some views may still be necessary as group-bys are 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, then only orders from the enterprise will be read into memory.
• All filters should be created at the same level as relationships.
• Query Subjects should be grouped by schema type at the highest level.