Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 214 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
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.
Comments
-
I started making an idea and then I saw this one already existed so voted it up! I am including the details of the idea I started to create:
Make Years Service and Average Tenure metrics flexible based on customers specific seniority date configuration.
We recently went live with FDI and found that Years Service and Average Tenure are computing solely based on Work Relationship Start Date (Legal Employer Hire Date) and not Legal Employer Seniority Date as Oracle documentation states it should.
This causes a couple of issues for us as our Fusion Core HR hire dates (V1) aligned with FDI product documentation NOT how FDI is currently behaving:
We cannot use the out of the box dashboards/metrics and need to create and maintain custom solutions that we did not anticipate when we were sold on FDI.
Further, we configured Tenure Bands in the Admin Console > Reporting Configuration and cannot use them because the Average Tenure key metric that includes tenure bands is based on Work Relationship Start Date. We need it based on LE Seniority Date.
Oracle has provided a few additional Years Service metrics (ex: Years Service V1 LE Seniority) however only Average Tenure and the base Years Service work with the Tenure Band configuration.
Customers could be on V1 or V3 seniority dates and may have varying requirements for which seniority/hire date to use for Years Service and Tenure. I would like to see Oracle provide a flexible solution here that would work for any customer. One thought I had was to include the seniority date selection as part of the FDI Reporting Configuration (same place where tenure bands are setup). Customers could then select which seniority date they use and setup their tenure bands.
Data lineage:
Example: Years Service/Tenure show 4 years but we would expect 8.91 based on the LE seniority date. Tenure band name shows this person in 1-5 band we setup vs 6-10.
Screenshot of Admin > reporting configuration. Could an additional field be added to the tenure band section to select which seniority date to use – similar to how the enterprise calendar field currently works?
4 -
Have there been any updates on this? Our organization uses adjusted hire date and would love to be able to configure that like Mike mentioned above.
1 -
We are in the same situation & i'd like to explore whether a seniority date data model & BI publisher report can be connected to FDI and the seniority dates ingested that way. I'm not sure if it's possible, but I figure is worth exploring as an alternate option while the HCM - Seniority Date subject area isn't availble in FDI as a data source.
0 -
@Raghavendra Raghunath-Oracle we spoke many months back on this idea - there has been some continued interest in making the tenure band calculations more flexible. Is there any update on the Oracle side? Is this being considered/worked on?
1 -
Hi @Mike Tytler et al, This has been in our roadmap but has not made it so far to the final list. I see that this seems to be getting a lot of votes. Will surely prioritize this one within the next couple of releases. Will share the planned design in advance with the group here.
Raghu
2 -
@Raghavendra Raghunath-Oracle Thank you! Appreciate your update and support on this! Looking forward to hearing more in the upcoming year.
1 -
We would be very interested in using a customized feature for Tenure Months of Service bands using the Worker Seniority subject area with a Seniority Date and a Seniority Rule Name filter.
1
