My Oracle Support Banner

OTAC/TEE: Best Practices for Report Efficiency in OBI (Doc ID 2074276.1)

Last updated on DECEMBER 31, 2020

Applies to:

Oracle Taleo Platform Cloud Service - Reporting for OBI - Version 20B and later
Information in this document applies to any platform.

Goal

Document Purpose:

Whether you are new to reporting with Oracle Business Intelligence (OBI) for Oracle Taleo or a seasoned report developer, it is normal to find some challenges when it comes to building reports for optimized peak performance.

That means creating reports that do not end with database timeout errors, exceeding maximum query rows, or not running to completion.

Here are a few tips for optimizing reports in OBI that may help!

 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 General Optimization Tips
 Remove All Unused or Duplicated Fields from Selected Columns
 Add a Date Range to the Filters
 Use the Operator "Is Between" for Date Ranges
 Avoid Using "Contains" or "LIKE" Operators
 Keep Custom Formulas Concise
 Keep Sub-Queries Simple
 Avoid Overuse of MAX and MIN Functions
 Use "Include Null Values" with Caution:
 Optimization Tips for Recruiting Subject Area
 Use Filters to Exclude Requisition or Candidate Records Not Visible in Recruiting
 Order Columns and Filters by Class
 Order Filters to Eliminate the Largest Amount of Data First
 When Using History Tracking Fields, Include Filters for Them
 Add Measures When Including Profile Fields
 For Cycle Time or Aging Fields, Use the Attribute
 Optimization Tips for Recruiting (Legacy) Subject Area
 Use Filters to Exclude Requisition or Candidate Records Not Visible in Recruiting
 Use Columns from the Context Folder
 Use the ID Columns for Filters
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.