Oracle Communities

Oracle Analytics and AI

Child Item

Termination date appearing in following Enterprise Period – FDI

When working on Turnover reports/visuals in Fusion Data Intelligence Terminations which fall on the last day of the month fall into the following Enterprise Period.

I am aware this is how Oracle calculates terminations however, I am curious to understand how other companies are calculating their turnover data in FDI?

Have you moved to calculating as per FDI or do you have a work around that you have implemented?

Find more posts tagged with

Oracle Fusion Analytics

FDI

Fusion AI Data Platform

Accepted answers

Scott_Turner_

Hi @Rajesh L-Oracle It is more the use of Enterprise Period and when the termination date falls on the last day of the month it count the termination in the following period. (see image below: Noting that the two terminations which occur on 29/02/2024 are being counted in Mar-2024 Enterprise Period.) When you utilise Enterprise Period to calculate turnover it skews the calculations as to how they are normally calculated in Australia.

Richard Kemp-Eyre

Hi Scott,
We've experienced exactly the same issue when trying to use the facts in the Workforce Trend Real Time Subject Area.

The facts are based around the Effective Start Date of the employee's assignment for the entry after their termination - see screenshot below as an example. This example assignment is counted as an April Leaver.

The documentation for this Subject area states:

Time Reporting

This subject area can be used to report on the headcount trend over a period which is historical data reporting.

Time dimension is linked to Trend month is determined by comparing Calendar Month falls between assignment_Effective_Start_Date and Assignment_Effective_End_Date.

See https://docs.oracle.com/en/cloud/saas/human-resources/23d/faohb/Workforce-Management--Workforce-Trend-Real-Time-SA-10.html#Workforce_Management__Workforce_Trend_Real_Time_SA_10_d1e17396

We've tried playing with timestampadd on the various assignment_Effective_Start_Date fields but gave up.

All comments

Rajesh L-Oracle

Hi @Scott_Turner can you share details which specific metric you are using for validation and if you are using any metrics in OTBI for data comparison if there is any data mismatch in FDI we can debug via Support SR

@Nupur Joshi-Oracle can you please share if there are any plans to make any update in headcount/turnover calculation for last day of month in FDI

Scott_Turner_

Richard Kemp-Eyre

Hi Scott,
We've experienced exactly the same issue when trying to use the facts in the Workforce Trend Real Time Subject Area.

The documentation for this Subject area states:

Time Reporting

This subject area can be used to report on the headcount trend over a period which is historical data reporting.

Time dimension is linked to Trend month is determined by comparing Calendar Month falls between assignment_Effective_Start_Date and Assignment_Effective_End_Date.

See https://docs.oracle.com/en/cloud/saas/human-resources/23d/faohb/Workforce-Management--Workforce-Trend-Real-Time-SA-10.html#Workforce_Management__Workforce_Trend_Real_Time_SA_10_d1e17396

We've tried playing with timestampadd on the various assignment_Effective_Start_Date fields but gave up.

TessaEwens

Has anyone had any luck/further traction on this? I'm trying to create a new Worker Turnover calculation using Termination Count(Termination Date), but not having much luck:

TessaEwens

This workaround calculation may work for you @Richard Kemp-Eyre and @Scott_Turner_:

Worker Turnover (Termination Date)
Purpose: Calculates worker Turnover by Termination Date, rather than Assignment Start Date
Calculation:
100 * (
"HCM - Workforce Core"."Facts - Workforce Attrition(By Termination Date)"."Termination Count(Termination Date)"
/
"HCM - Workforce Core"."Facts - Workforce Person Count"."Average Worker Count"
)