Oracle Communities

Oracle Analytics and AI

Child Item

Ability to change the date the length of service band calculation uses (e.g. seniority date)

We're getting feedback from customers who want the flexibility to change the date the tenure band (length of service band) uses for calculations, such as using the enterprise seniority date.

Could we enable a feature that lets customers set this date based on their preference? It would greatly improve their experience and accuracy in reporting.

Letting customers change the date the tenure band uses for calculations, like the enterprise seniority date, has big benefits. It makes it easier for them to create their own visualizations for KPIs and ensures their reports are more accurate and tailored to their needs. This flexibility helps them make better decisions with data that fits their specific context.

Currently we're having trouble because we can't change the date the tenure band uses for calculations. This means we can't report on important KPIs for turnover, so we don't know if people are leaving in their first year or after 10 years. It's really hurting our ability to understand and improve employee retention.

Find more posts tagged with

Planned

Reporting

HCM

HCM Analytics Content

FDI

Status: Planned

Comments

Mike Tytler

@Gina DiVenti @Raghavendra Raghunath-Oracle

From "PER_PERIODS_OF_SERVICE":

ADJUSTED_SVC_DATE = Legal Employer Seniority Date

ORIGINAL_DATE_OF_HIRE = Enterprise Seniority Date

Hoping this helps translate the table values to the displayed values in the subject area.

We want to use Legal Employer Seniority Date (same as ADJUSTED_SVC_DATE from PER_PERIODS_OF_SERVICE) for our tenure bands. Which I think is what Gina is after too and the various naming conventions are tripping us up - Gina, please jump in and comment if you are looking for something else.

Flexibility to use all 4 of the dates listed would be ideal.

Mike Tytler

Sorry another clarification - we are on V1 seniority dates which is why I referenced PER_PERIODS_OF SERVICE. Customers on V3 seniority dates would have the dates in PER_SENIORITY_DATES_F

Gina DiVenti

Thanks, Mike! This really helped me realize that our setup might be more unique than I initially thought. The field we are using is actually a DFF in FDI, so I understand it might not be realistic to add it to the list of the four above.

TessaEwens

In our organisation, we use Person Seniority Details = Senority Date and Seniority Date Setup/Seniority Rule Name = Enterprise Seniority Date.

Raghavendra Raghunath-Oracle

Hi @Gina DiVenti are you referring to the one that is related to work relationship details of the worker? can you share the screenshot of that from the application?

@Mike Tytler - is it ok to have the band based on this column(Legal Employer Seniority Date) even though the salary basis subject area is not having this column?

Raghu

Mike Tytler

@Raghavendra Raghunath-Oracle For us, the ideal state would be to have all 4 of the dates you listed available in all of the subject areas. We would also want the tenure bands to be consistent across the subject areas. Ex: tenure bands based on the legal employer seniority date consistently throughout the subject areas.

I am not sure why Oracle did not include all of the dates in the subject area (why not be consistent?). I am ok with getting this tenure band enhancement in place even though the date is not available in the subject area (yet). Getting all of the hire dates consistently added could be another enhancement request if needed.

Anurag Umathe

I agree, We should have a dimension for Seniority dates available in all subject area. This will simplify the security and help users to get Seniority data directly from the subject area they are working on, instead of joining it with Seniority date SA.

Also we observed that, FDI do not show all the Seniority rules we have defined in Fusion. For example, We have seniority Rule based on Union code. and when checked in FDI Seniority Date Subject area, we do not see this rule there. I assume all the data (Rule code and Dates) from PER_SENIORITY_DATES_F should flow to FDI.

Gina DiVenti

@Raghavendra Raghunath-Oracle For OTBI, I think our team has used a combination of Work Relationship Real Time, and Worker Assignment Real Time depending on the need, but overall it pulls from the Seniority Rule Name, filtered to Adjusted Hire Date, and then the Seniority Date field is used. Screenshots from FDI and OTBI are below.

I appreciate you considering this!

FDI:

OTBI:

Fusion:

Raghavendra Raghunath-Oracle

Hi All,

For now, we plan to go ahead with the 4 options for the dates that can be setup as Years of Service or Months of Service Bands

Work Relationship Start Date
LE Seniority Date
Enterprise Hire Date
Enterprise Seniority Date

@Gina DiVenti We may not be able to support the date from the DFF

@Mike Tytler yes, we will plan to add these columns across all subject areas

@Anurag Umathe yes, currently, any seniority rule based on a dimension that is not available in FDI, is not supported. Union is one such. We will enhance it.

Thanks

Raghu

TessaEwens

Hi Raghu,

Thanks for the update, this is great news! When can we expect this change to take place & go live in FDI?

Thanks,
Tessa