Oracle Communities

Oracle Analytics and AI

Child Item

Add Time dimension for Seniority Subject Area

We would like to see a Time dimension added to FDI HCM - Worker Seniority subject area so that we can analyze the average tenure over time. We are currently unable to add a time slicer for year, quarter and/or month in this subject area in FDI. This would be helpful to track the change of tenure over time.

Find more posts tagged with

FDI

Needs Votes

Fusion HCM Analytics

Status: Needs Votes

Comments

Raghavendra Raghunath-Oracle

Hi @Sam Reinhart can you please provide an example as to how you plan to use Time dimension with the seniority data of the workers? This subject area provides you the latest seniority of the worker for each of the rules that have been setup.

A sample tabular illustration of how you plan to use this data with Time dimension will help me to prioritise this.

Thanks

Raghu

Sam Reinhart

Hi Raghu!

Here is our use case - We want to see the length of service bands YoY or QoQ, by time. We want to see how many people are in the 1-3 year LOS bands in 2024 vs 2023, by year, quarter and period. We do not currently have a sample illustration as we were hoping FDI could help with deeper insights into Seniority.

Thanks,

Sam

Raghavendra Raghunath-Oracle

Hi Sam,

Currently, The Seniority Data for the combination of worker and the rule name is as of the latest date on which the process was run to compute the seniority. For example: A worker's seniority for a rule is 3 Years hence is categorised under 3-4 Years band

Your requirement is, hypothetically if the rule was run last year then the same worker would have had seniority as 2 years and would be categorised under 0-2 Years band.

Person	Rule	Seniority	Band	Process Run date	Year
Jon	Enterprise	4 Years	3-4	01-Apr-24	2024
Jon	Enterprise	3 Years	3-4	01-Apr-24	2023
Jon	Enterprise	2 Years	0-2	01-Apr-24	2022
Jon	Enterprise	1 Years	0-2	01-Apr-24	2021

This is like having a snapshot of the Worker Seniority YOY

I see there are 8 votes already for your idea

But I want you and others to confirm if my understanding is right

We can evaluate and get back on the forum on the feasibility of this.

Raghu

Sam Reinhart

Thanks Raghu! Sorry for the delay, we are wrapping up our implementation phase. Yes this is the logic we are expecting for this idea/enhancement.

Krish1323

Hi Raghu,

Adding a time dimension will enable Los/tenure calculations by month/quarter/year based on user input using the adjustment service date and Latest Hire Date for seniority rule.

This enhancement will ensure consist logic across multiple reports in the project?

Best Regards,

Murali Krishna

User_CODZH

Hi Raghu,

We wanted to follow up on this and see if there are any updates.

Best Regards,

Heather

Raghavendra Raghunath-Oracle

@Sam Reinhart

@Krish1323

@Riti Malhotra

Hi Heather, and others on this thread,

Can we meet to go over this requirement in detail?
As i mentioned above, this is beyond just adding the Time dimension to the subject area
I would like to get your perspective clearly

Thanks

Raghu