A Report Authoring Tips

This section provides tips and guidelines for creating effective and timely reports.

Common Report Authoring Tips

Improve all of your Oracle Fusion Data Intelligence reports with these recommendations and answers to frequently asked questions regarding reporting. The information isn’t exhaustive and is updated regularly with additional information and authoring tips.

Tips for Filters

When applying filters to reports, follow these guidelines:

  • Use dashboard filters instead of workbook or canvas filters for user interactions in analyses.
  • Use workbook filters for hidden and non-interaction filters.
  • Set the Limit by Values to None for all filters in custom workbooks or dashboards to improve performance of prompts.
  • When applying a filter on an attribute, use a Code column (when available) instead of a Name or Description column.

Tips for Brushing

Disable brushing to improve report performance. See Update Canvas Properties.

Tips for Working with Currency

To display the currency format for currency amounts, set the number format in each visualization as a custom currency. Then in the subject area folder, select the currency column. See Set Currency Symbols for Visualizations.

Tips for Reporting on Attributes Across Multiple Dimensions

When reporting on attributes against multiple dimensions, always use a measure in the report. In subject areas with more than one fact, the measure sets the correct context in the query, builds an accurate navigational path, and returns the expected results. If you don’t want the measure to show in the report, hide it. See Hide or Delete a Column.

Tips for Presentation Hierarchies

To improve performance, use presentation columns instead of presentation hierarchies. See Work with Presentation Tables and Columns.

Report Authoring Tips for Oracle Fusion HCM Analytics

Improve your Oracle Fusion HCM Analytics reports with these recommendations and answers to frequently asked questions regarding reporting. The information isn’t exhaustive and is updated regularly with additional information and authoring tips.

Tips for Improving Performance of all HCM Reports

  • Use the prebuilt fact metrics whenever possible under the subject area you're using for your report. For each subject area, select the closest or most appropriate prebuilt metric for your reports, and then apply filters as needed.

    Hover over the metric name to see a description of the metric to use for your workbook. For example, to get a headcount of employees use the Employee Headcount metric.

    See Prebuilt in this guide for details.
  • Use prebuilt metrics to build custom calculations.
  • Validate each customization for accuracy.
  • Review the latest updates in this publication (Reference for Oracle Fusion HCM Analytics) to learn about the most appropriate objects and methods for creating customized reports.

Tips for Improving Performance of Reports with Department or Organization Hierarchy Folders

When creating a report that uses attributes from the Department or Organization Hierarchy folders, set filters for Tree Version Effective Start Date and Tree Code to improve performance.

Tips for Improving Performance of Reports on Top Manager, Manager Hierarchy, Assignment Manager List, or Bottom-Up Manager Hierarchy Queries

To improve the performance of Top Manager, Manager Hierarchy, Assignment Manager List, or Bottom-Up Manager Hierarchy queries, follow these guidelines:

  • Run the refresh process Refresh Manager Hierarchy with a null parameter and then with a zero (0) parameter in Fusion Applications prior to running the ETL to see the data in the Manager Hierarchy or Assignment Manager List folders.
  • Filter on Manager Name and Time: Year, Quarter, Month, or Date when any user other than Line Manager runs a report with attributes from the Manager Hierarchy or Assignment Manager List folders in either the select list or the filter list because data in these hierarchy folders are date effective.
  • Use attributes from the Assignment Manager List folder (instead of from the Manager Hierarchy folder) when you aren't drilling to Manager Hierarchy to improve report performance.

Tips for Improving Performance of Reports on Worksheet Manager Hierarchy or Worksheet Manager Hierarchy List in HCM – Workforce Rewards – Workforce Compensation Queries

To improve performance on Worksheet Manager Hierarchy or Worksheet Manager Hierarchy List in HCM – Workforce Rewards – Workforce Compensation queries, follow these guidelines:

  • Run the Synchronize Hierarchy process by providing Plan Name and Cycle Name as parameters in Fusion Applications prior to running the ETL.
  • Filter on Manager Name when any user other than Line Manager runs a report that has attributes from the Worksheet Manager Hierarchy or Worksheet Manager Hierarchy List folders either in the select list or in the filter list.
  • Use attributes from the Worksheet Manager Hierarchy List folder (instead of from the Worksheet Manager Hierarchy folder) when you aren't drilling to Manager Hierarchy to improve report performance.

Tips for Improving Performance of Reports on HCM - Workforce Core Subject Area Queries

To improve performance on Reports in HCM – Workforce Rewards – Workforce Compensation queries, follow these guidelines:

  • When reporting on headcounts, use a date filter applied to the most recent refresh date (or month) to report on the latest snapshot of data. Using To_DateTime(VALUEOF(NQ_SESSION.CURRENT_GREGORIAN_DAY), 'DD-Mon-YY') significantly reduces the time and resources necessary to run the report.
  • Filter using event-based flags

Tips for Improving Performance of Reports on Headcounts

When creating a report using the Headcount metric, the returned value is the last day of the selected period, or if you do a daily refresh, is the most recent snapshot refresh date. If you use the Headcount metric without a filter, you will only see the most recent snapshot. Apply a date filter on the most recent refresh date to select only the most recent data.

Use the expression To_DateTime(VALUEOF(NQ_SESSION.CURRENT_GREGORIAN_DAY), 'DD-Mon-YY') to create the filter on the most recent date, which significantly reduces the query time and resources to return the data you want.
Description of lastrefreshfilter.png follows
Description of the illustration lastrefreshfilter.png

You can use the same principle to select headcount by month. Since headcount by month is returned using the last day of the month, apply an explicit filter to use the last day of the month and the most recent snapshot date to improve performance.
Description of monthendfilter.png follows
Description of the illustration monthendfilter.png

Tips for Using Event-Based Flag Filters

The Assignment Event fact table records all changes and events related to an employee's employment. Use the provided filters to get the results you want. For example, to see Employee Hires by Month, you can use the action type EMPL_ADD_EMP to select new employee hires.



In this example, you don't have any filters applied to the Assignment Event fact table. You can use the HIRE_EVENT_IND flag to identify hire events and optimize performance by filtering directly on the fact table.

Note:

You'll need to use the semantic model extension to use this flag if it's not already available in the subject area.
  1. Create a new step for Add Column.

  2. Add the HIRE_EVENT_IND physical column from the fact table and map it to a new logical column named Hire Event Ind. Be sure the new column is set to Display.
  3. Save and publish the new step.

    In the folder where you published the new step, you see the new Hire Event Ind column.

  4. In the Employee Hire column calculation in the workbook, replace the EMPL_ADD_EMP filter with a new calculation Hire Event IND = 1, and name it New Employee Hires. Add the filter on Assignment Type Code to select employees only..

Tips for Improving Performance of Reports on HCM - Diversity Analysis Subject Area Queries

To improve performance on HCM - Diversity Analysis subject area queries, follow these guidelines:

  • When a report uses any statistical attributes from the folders Promotion Details (Age), (Ethnicity), (Gender) or Termination Details; (Age), (Ethnicity), (Gender) or Salary Details; (Age), (Ethnicity), or (Gender), you need to include the following columns in the report to ensure the statistical attributes are calculated at the correct grain:
    • Reporting Establishment.Reporting Establishment Name
    • Time.Year
    • Legislative Job Category.EEO-1 Category
    • Country.Country Name
    • If you are reporting on Age, Ethnicity, or Gender, also select Age code, Ethnicity, or Gender from the same folder as the statistical attributes.
  • When a report has any statistical attributes from the folders Hiring Details (Age), (Ethnicity), or (Gender), you need to include the following columns in the report to ensure the statistical attributes are calculated at the correct grain:
    • Time.Year
    • Location Details. Location Name
    • Legislative Job Category.EEO-1 Category
    • Country.Country Name
    • If you are reporting on Age, Ethnicity, or Gender, also select Age code, Ethnicity, or Gender from the same folder as the statistical attributes.

Tips for Improving Performance of Reports on HCM - Learning Subject Area Queries

When building a report using the HCM - Learning subject area, include a Time dimension attribute such as Time.Date in the report.

Tips for Improving Performance of Reports on HCM - Workforce Time and Labor Management Subject Area Queries

When designing visualizations, always define default values for the prompts, and choose the most selected values as defaults.

Tips for Using Timestamp Fields As Filters in Reports On HCM - Health And Safety Incidents Subject Area Queries

When filtering on Timestamp fields, use "is greater than or equal to", "is greater than", "is less than or equal to", "is less than", or "between".

Tips for Improving Performance of Reports on HCM - Workforce Core Queries

To improve performance on HCM - Diversity Analysis subject area queries, follow these guidelines:
  • Use the prebuilt workbooks available and build or modify them whenever possible. You can make a copy of the original workbook in a custom folder.
  • Remove TopN filters on Year. Instead use explicit values, or dynamically pick the current year, and change it using -1 and -2 based on the current date to give similar behavior.
  • Always leverage prebuilt metrics for all requirements until and unless that metric isn't available.
  • For the tiles displaying current or previous month headcount metrics, filter on one day instead of multiple years.
  • Apply the selective filters only to the visualization as needed. Adding filters on the visualization where it isn't needed degrades the efficiency of the query.
  • Convert generic filters to dashboard filters with the Apply button to avoid sending pre-matured queries to the database. This reduces unnecessary load on the database.
  • Instead of using variables for Year, Quarter, and Month filters, create prompts on Time.Year and bind the prompt to the variabel created on Year. Variables created for quarter and month are set to a default value of All, so these prompts can be set to limit by Year, and Year and Quarter.
  • The Geo Selector derived attribute uses Department Hierarchy. Department Name is in the else part, which is nothing but the leaf node in the hierarchy. Therefore, use Common.Department.Department Name which will reduce the additional call to the Hierarchy table.
  • Tune the OCPU limit of Autonomous Data Warehouse.
  • In master/detail reports, ensure filters are aligned on all people.
  • In master/detail reports, ensure assignments for each person use the same worker type (such as pending or contingent) to avoid reporting two workers per person (one pending and one contingent).
  • In master/detail reports, be aware that inactive pending worker assignments the manager name is NULL.
  • In master/detail reports, ensure when assignment level attributes are added that you restrict the pending worker types by adding a filter on "assignment type <> 'P'".

Tips for Improving Cross-Subject Area Queries

To improve performance on cross- -subject area queries, follow these guidelines:
  • When joining two subject areas in a report, be sure to use at least one attribute from a common dimension used in the report.
  • When using common dimensions, always pick attributes from the common dimension from a single subject area.
  • Always include a measure from each subject area that is used in the report.
  • If all the metrics and attributes needed for the report are available in a single subject area and fact, use that subject area only and don't create a cross-subject srea query. Such a report performs better and is easier to maintain.

Recommended Filters

Subject Area Presentation Columns (* Required Filter)
HCM - Check-Ins

Time - Year or QTR or Month* or Time – Enterprise Year or Enterprise Quarter or Enterprise Period*

Review Period.Review Period Name

HCM - Diversity Analysis

Promotions/Salary/Terminations-based reports:

Time.Year*

Reporting Establishment.Reporting Establishment Name

Legislative Job Category.EEO-1 Category (Job Category)

Country.Country Name

Hiring-related reports:

Time.Year*

Location Details.Location Name

Legislative Job Category.EEO-1 Category (Job Category)

Country.Country Name

HCM - Goals and Career Development

Content based on Performance Goals-related measures:

  • Review Period.Review Period Name*
  • Performance Goal Plan.Goal Plan Name

Content based on Development Goals related measures:

  • Assignment Manager List.Manager Name
HCM - Health and Safety Incidents

Time - Year or QTR or Month or Date*

HCM - HR Help Desk Requests Overview
  • Time – Year or QTR or Month*
  • Time – Enterprise Year or Enterprise Quarter or Enterprise Period*
HCM – Journeys

Time – Year or QTR or Month* or Time – Enterprise Year or Enterprise Quarter or Enterprise Period*

Allocated Journeys.Allocated Journey Name

Manager Information.Manager Name

HCM - Learning

Time – Year or QTR or Month *

Common folder: Business Unit Name or Department Name or Location Name

Learning Records: Learning Item Type

Learning Enrollments: Enrolled on Date/ Enrollment Record Due Date

HCM - Performance Management
  • Time – Year or QTR or Month* or Time – Enterprise Year or Enterprise Quarter or Enterprise Period*
  • Performance Document.Performance Document Name
  • Review Period.Review Period Name
HCM - Positions

Time – Year or QTR or Month*

HCM - Profile Matching
  • Job Profile.Profile Name*
  • Model Job.Job Name

When reporting on content based on attributes from Person Profile – Skill Gap Details, add these filters:

  • Person Profile – Skill Gap Details.Content Type*
  • Person Profile – Score Details.Percentile
HCM – Succession Management Time – Year or Time – Enterprise Year
HCM - Talent Acquisition

Time - Year/QTR/Month/Date*

Organization.Organization Name

HCM - Talent Profile
  • Business Unit.Business Unit Name

When reports use metrics from a Model profile based on a Job or Position, use one of these filters:

  • Job Model Profile Details.Profile Name
  • Position Model Profile Details.Profile Name

When a report has metrics from Person Profile, use the filters from: Person Profile - Skills and Qualifications or Talent Ratings

HCM - Talent Review Meetings Time - Year or QTR or Month* or Time – Enterprise Year or Enterprise Quarter or Enterprise Period *
HCM – Worker Seniority Seniority Details.Seniority Rule Name*
HCM - Workforce Absence Management

Content based on facts in the Absences folder:

  • Time – Year/QTR/Month* or Time – Enterprise Year/Enterprise Quarter/Enterprise Period*
  • Business Unit.Business Unit Name

Content based on facts in the Employment Plan Participation folder:

  • Time – Year/QTR/Month* or Time – Enterprise Year/Enterprise Quarter/Enterprise Period*
  • Business Unit.Business Unit Name
  • Absence Plan.Plan Type

When reporting on Accrual Balance, you must include one of these filters:

  • Accrual Balance Details.Balance Calculation Date
  • Attribute Accrual Balance Details.Accrual Period End Date
HCM – Workforce Core
  • Time – Year/QTR/Month* or Time – Enterprise Year/Enterprise Quarter/Enterprise Period*
  • Business Unit.Business Unit Name
  • Country.Country Name
  • Job Family.Job Family Name
HCM - Workforce Gains and Losses

Time.Year or QTR or Month* or Time – Enterprise Year or Enterprise Quarter or Enterprise Period*

This subject area provides gains and losses based on various Assignment events, so when reporting on this subject area, use a filter from the list below to identify gains and losses from a particular type of event:

  • Gain and Loss Details.Business Unit Gain Loss Flag
  • Gain and Loss Details.Department Gain Loss Flag
  • Gain and Loss Details.Full Time/ Part Time Gain Loss Flag
  • Gain and Loss Details.Grade Gain Loss Flag
  • Gain and Loss Details.Job Gain Loss Flag
  • Gain and Loss Details.Location Gain Loss Flag
  • Gain and Loss Details.Position Gain Loss Flag
  • Gain and Loss Details.Supervisor Gain Loss Flag
HCM - Workforce Rewards - Payroll Balances

Time – Year/QTR/Month: Filter using smaller time periods to improve performance

Payroll Period – Payroll Period Name (in particular when the report is at Person Grain)

Payroll.Payroll Name

When using Balance Value (base measure) in a report, apply a filter on Balance Dimension.Balance Dimension Name.to prevent metric values from being multiplied by the number of configured balance dimensions

HCM - Workforce Rewards - Payroll Costing

Time – Year/QTR/Month: Filter using smaller time periods to improve performance).

Element – Element Classification

Use at least one segment from the Costing Segments folder; use the Segment code wherever possible

Payroll.Payroll Name

HCM - Workforce Rewards - Salary Basis
  • Time – Year/QTR/Month* or Time – Enterprise Year/Enterprise Quarter/Enterprise Period*
  • Business Unit.Business Unit Name
HCM - Workforce Rewards - Workforce Compensation

Compensation Plan Cycle.Plan Cycle Name*

Business Unit.Business Unit Name

Compensation Plan.Plan Name*

HCM – Workforce Time and Labor Management

Time – Year or QTR or Month*

Reported Time Card Start Date and Time

Reported Time Card End Date and Time

Common folder: Business Unit Name or Department Name or Legal Employer name.