Fusion HCM OTBI Historical

Reporting Explained
(An Oracle White Paper)

Update Date: September 19, 2014

Author: Ling Xiang, BI Application Product Management

Contributor: Julian Challenger, Fusion HCM Product Management

Contents
Fusion HCM OTBI Historical Reporting Explained ........................................................................ 1

Does Fusion HCM OTBI Support Historical Reporting?......................................................... 3

Subject Areas with Time Dimension .................................................................................... 3

Subject Areas without Time Dimension ............................................................................... 4

Reporting on dimensional attributes ................................................................................... 6

OTBI Historical Reporting Example ...................................................................................... 7

How to Create A Headcount Report with A As-Of Date Prompt (Example)........................... 8

Does Fusion HCM OTBI Support Historical Reporting?
Fusion HCM uses Effective Date extensively to track history. Fusion HCM OTBI supports
historical reporting. Fusion HCM historical reporting comes in 3 categories:

1. Subject areas with Time dimension. Time dimension corresponds to the transaction’s
Effective Date. Time dimension allows users to report historical transactions in these
subject areas. For example, Workforce Management – Worker Assignment Event Real
Time subject area includes a worker’s assignment history.

2. Subject areas without a Time dimension. These subject areas are designed to report the
current information. For example, by default, Workforce Management – Worker
Assignment Real Time reports a worker’s current assignment information. However you
can report historical headcount or assignment information by applying a logical SQL
prefix to reset the default as-of date.

3. Dimensional attributes. By default, dimensional attributes are current information only.

When you report historical transactions, only the current grade, department, location,
etc. attributes are returned by default. You can reset the default as-of date using a
logical SQL prefix to get historical dimensional attribute.

Subject Areas with Time Dimension

Time dimension is linked to the effective date of the primary transactions in the subject area.
For example, Time dimension in Assignment Event subject area represents the effective date of
the assignments and in Salary History subject area it represents the effective date of the salary
change events. (Salary History subject area will be available in Fusion release 9.) Time
dimension allows you to roll up the transactions by month, quarter or year. Subject areas with
Time dimension allow historical reporting on transactions. You can use Time dimension to
report transactional history. For example, by selecting Year and Hire Count from Assignment
Event subject area, you can report hire count by year

Please Note:

Exception to the above rule:

Compensation - Salary Details Real Time subject area only contains the current salary even
though Time dimension is available. Compensation history is available in the Compensation –
Salary History subject area that will be introduced in Release 9.

The following is the list of the subject areas that support historical transaction reporting through
Time dimension:

Subject Area Time Dimension History Reporting

 Subject Area
Benefits - Action Items Real Time
Benefits - Enrollment Opportunities Real Time
Benefits - Enrollments Real Time
Benefits - Potential Life Events Real Time
Compensation - Stock Details Real Time
Payroll - Element Entries Real Time
Payroll - Payments Costing Real Time
Payroll - Payments Distribution Real Time
Payroll - Payroll Run Costing Real Time
Payroll - Payroll Run Results Real Time
Payroll - Retroactive Pay Real Time
Workforce Goals - Goal Alignments Real Time
Workforce Goals - Goal Status Overview Real
Time
Workforce Goals - Goal Tasks Real Time
Workforce Goals - Target Outcomes Real Time
Workforce Management - Absence Real Time
Workforce Management - Documents of
Record Real Time
Workforce Management - Worker Assignment
Event Real Time
Workforce Performance - Performance
Document Status Real Time
Workforce Performance - Performance Rating
Distribution Real Time
Workforce Performance - Performance Rating
Real Time
Workforce Performance - Performance Task
Status Real Time
Workforce Profiles - Model Profile Real Time
Workforce Profiles - Person Profile Real Time
Workforce Talent Review - Talent Review
Meeting Real Time
Subject Areas without Time Dimension
If a subject area has no Time dimension, this subject area is designed to report the latest
transactions as of Today’s date. OTB uses the default Today’s date to resolve the as-of date for
the effective date logic. You can override the default as-of date by supplying an Effective Date
parameter in the logical SQL Prefix.
Time Dimension History Reporting
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
Y History reporting through Time dimension
 Logical SQL Prefix SET VARIABLE PARAM_EFFECTIVE_DATE =’yyyy-mm-dd ‘;

This Logical SQL prefix resets the effective date parameter to a user-defined date before the
report executes. You can set the as-of date to a specific date or a user prompt. This piece of
code resets the as-of date to May 18th, 2006.

• SET VARIABLE PARAM_EFFECTIVE_DATE='2006-05-18';

In Answers, you apply the logical SQL prefix in the Advanced tab, Prefix field.

Please note, Workforce Compensation and Workforce Compensation Budget don’t include Time
dimension but it supports historical reporting through Compensation Plan Date.

The following is the list of subject areas that report the current information by default:

Subject Area Time Dimension History Reporting

 Subject Area
Benefits - Setup Real Time
Compensation - Workforce Compensation
Budgets Real Time
Compensation - Workforce Compensation
Real Time
Workforce Management - Employment
Contract Real Time
Workforce Management - Grade Rate Real
Time
Workforce Management - Person Real Time
Workforce Management - Position Real Time
Workforce Management - Work Relationship
Real Time
Workforce Management - Worker Assignment
Real Time
Workforce Profiles - Library Objects Real Time
Workforce Succession Management -
Incumbent Plans Real Time
Workforce Succession Management - Job
Plans Real Time
Workforce Succession Management - Plan
Candidates Real Time
Reporting on dimensional attributes
By default, all dimensions report the current information. When you use Time dimension to
filter transactional history, the time filter doesn’t apply to the dimensional attributes and only
Time Dimension History Reporting
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
History Reporting through Compensation Plan
N Date
History Reporting through Compensation Plan
N Date
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
By default, reporting as of the current date;
The current as-of date can be reset using
logical SQL prefix. This will allow history or
N future-dated transactions
the latest attributes are returned for the historical transactions (this is illustrated in the OTBI
historical reporting example section.)

You can use the logical SQL prefix to reset the as-of date for historical reporting:

SET VARIABLE PARAM_EFFECTIVE_DATE='2006-05-18';

This effective date parameter overrides the default as-of date (Today) to resolve the Effective
Date logic for all dimensions or transactions and fetches the latest information as of the
specified as-of date. This variable has no effect when you use Time dimension to fetch history
as these subject areas explicitly use Time dimension not the implicit default system date to
resolve the date logic.

OTBI Historical Reporting Example

The is example uses Worker Assignment Event and Worker Assignment subject areas to
illustrates how current and historical reporting is manifested in OTBI and how the logical SQL
prefix enables historical as-of reporting.

Date Dept Change Worker Assignment Change

1/1/2014 Dept “JC Department” is created
Worker “JC Lastname” is hired into dept 'JC
1/3/2014
Department'
1/10/2014 Worker "JC Lastname' grade and location changed
Renamed the department to “JC
1/27/2014
Department Updated”

Worker "JC Lastname" changed department to

1/24/2014
“Vision Communications (USA)”

• Workforce Management – Worker Assignment Events Real Time subject area reports
the worker’s assignment history:

Notice the current department name “JC Department Updated’ is displayed for Jan. 3, 2014
assignment even though the department name change happened on Jan. 27 2014
 • Workforce Management – Worker Assignment Real Time subject area reports the
worker’s current assignment information:

• Apply the logical SQL prefix SET VARIABLE PARM_EFFECTIVE_DATE = ‘2014-01-04’ to

Workforce Management – Worker Assignment Real Time. This reports the worker’s
assignment information as of ‘2014-01-04’ showing the worker in the old department
‘JC Department’

• Apply the logical SQL prefix SET VARIABLE PARM_EFFECTIVE_DATE = ‘2014-01-04’ to

Workforce Management – Worker Assignment Events Real Time. This subject area
already includes transaction history. The logical SQL prefix has no effect on the
assignment history being reported but it changes the department to the old department
name ‘JC Department’.

How to Create A Headcount Report with A As-Of Date Prompt (Example)

Workforce Management – Worker Assignment Real Time subject area reports workers’ current
assignment information. This example illustrates how to use Logical SQL prefix to reset the
default as-of date and retrieve workers’ assignment history with a user-specified as-of date
prompt. This technique can be used to dimensions or subject areas that need to reset the
default system as-of date.

1. In Answers, click the New menu, and select Analysis.

2. Select the Workforce Management - Worker Assignment Real Time subject

area.

Location: Select Subject Area window

3. Expand the Worker Assignment folder.

Location: Criteria tab, Subject Areas region

4. Select Head Count and drag it to the Selected Columns region.

5. Expand the Department folder, select Name, and drag it to the Selected
Columns region. This report fetches department headcount as of today.

6. Select the Prompts tab.

7. On the right-hand side of the page, click the New icon button and select Variable
prompt.
8. In the Prompt for field, leave the value of Presentation Variable, and enter
AsOfDate.

9. In the Label field, enter Workers as of (mm/dd/yyyy).

10. Expand the Options region.

11. In the Variable Data Type menu, select Date.

12. Select the Require user input option.

13. Select Dynamic for the Text Field Width.

14. Click OK.

15. Select the Advanced tab.

16. Scroll down to the Advanced SQL Clauses region.

17. In the Prefix field, enter SET VARIABLE

PARAM_EFFECTIVE_DATE='@{AsOfDate}';

18. Click Apply SQL.

19. Click OK to clear the message.

20. Click the Save Analysis icon button.

21. Select My Folders and enter Date-Effective Head count in the Name field.
22. Click OK.

23. At the top of the page, click the Home link to return to the OBI EE home page.

24. Locate your report in the Recent region.

25. Click Open.

26. In the Workers as of mm/dd/yyyy field, enter an effective date in the proper
format.

27.Press OK.

28.Review the results. Now you are looking at department headcount as of Jan. 1st
2010.