This chapter covers the following topics:
A dimension is a structure that categorizes data in order to enable users to answer business questions. Dimensions represent the organization of logical attributes that belong to a single logical dimension table.
OIC Analytics for ODI uses the following dimensions in reports:
Organization
Product and Product Hierarchy
Resource and Resource Hierarchy
Group and Group Hierarchy
Time (OIC Period and Interval)
Compensation Plan
Scenario
Dimensions can be either single-level or multi-level. Single-level dimensions store flat data, where as multi-level dimensions store hierarchical data that represents business reporting requirement.
OIC Analytics for ODI uses the Organization dimension when you select organization related details in the various OIC Analytics for ODI reports. If an application environment supports multiple organizations then users can view details specific to their assigned organization only.
OIC Analytics for ODI uses the Product Hierarchy dimension along with the Product dimension when you drill down a product hierarchy in a report. Plan administrators define this hierarchy at the OIC module level.
Product Dimension: This is a single-level dimension with corresponding OIC revenue data.
For example, you can view performance of a single product, without any drill down features.
Product Hierarchy Dimension: This is a multi-level hierarchical dimension for product hierarchies.
For example, you can view performance of all sub-products that fall under a higher-level product or category and then drill down to individual products.
Note: Datamart and BI metadata layer supports only up to 15 levels of information. If you have more levels defined in the OIC system, datamart and BI layer will not support these.
OIC Analytics for ODI uses the Group Hierarchy dimension along with the Group dimension to determine the rollup structure and drives managers’ view of their subordinates. This dimension is based on data in the Resource Manager, Compensation group hierarchy.
Note: Datamart and BI metadata layer supports only up to 15 levels of information. If you have more levels defined in the OIC system, datamart and BI layer will not support these.
OIC Analytics for ODI uses the Group Hierarchy dimension along with the Group dimension to determine the rollup structure and drives managers’ view of their subordinates. This dimension is based on data in the Resource Manager, Compensation group hierarchy.
Note: Note: Datamart and BI metadata layer supports only up to 15 levels of information. If you have more levels defined in the OIC system, datamart and BI layer will not support these.
OIC Analytics for ODI uses the Time dimension when you view reports driven by periods or intervals. All facts use the Time dimension to facilitate time-related reporting and roll up data to different time periods. This dimension is also hierarchical with three levels – period, quarter and year.
Facts are logical collection of measures or calculated data that can be specified in terms of dimensions, such as sum of commissions related to compensation, or commissions earned by a specific resource over a period of time.
Note: Note: Dimensions are attributes that qualify facts and give structure to facts.
OIC Analytics for ODI uses the following facts in the various reports:
Earnings
Quota
The Earning fact stores sales credits and commissions earned by resource OIC. All the OIC transactions that are calculated are stored in this fact table.
For more information about the loading process, see Oracle Incentive Compensation User Guide.
The Earnings fact is based on the following dimensions:
Compensation Plan
Product
Resource
Transaction Type
Time
Organization
Scenario
The Quota fact contains the quotas and attainment for a plan element in a period for each salesperson. This fact is based on the following dimensions:
Compensation Plan
Organization
Time
Resource
OIC Analytics for ODI uses the currency parameter to store data in the facts. Whenever, you run the ODI data load process, the application checks for the global currency and exchange rate defined in the system profile and then performs currency conversion accordingly.
For example, the original transaction amount is 500 CAD, the global currency is set to USD, and the monthly conversion rate is 2. Then the application will store 1,000 USD (500 CAD * 2) as the amount in global currency fields.
Note: You can use different currency fields in a report to view multiple currencies.