Avoiding Conflicts in Data Selection

Carefully consider where you set up data selection so that you do not cause conflicts in your data. You can select the same data items for row definitions, column definitions, and the statement version data selection. Because the data items are the same, you could set up data selection that causes conflicts and that will return unexpected results or no results. For example, if you set up a column definition to return values for business unit A, set up a row definition to return values for business unit B, and set up the statement version to return values for business unit C, the system returns no values for the statement.

Oracle recommends that you:

• Set up data selection in the statement version instead of the column definitions and row definitions for data selection criteria that will apply to all rows and columns on a statement, such as the company and business unit.

• Do not set up data selection for the same data items in the row and column definitions that you will use in the same statement.

  For example, if you want to include a specific category code in your data selection, include it in the data selection in either the row definitions or the column definitions, but not in both the row and column definitions.