Categories
- All Categories
- Oracle Analytics Learning Hub
- 17 Oracle Analytics Sharing Center
- 17 Oracle Analytics Lounge
- 224 Oracle Analytics News
- 44 Oracle Analytics Videos
- 15.8K Oracle Analytics Forums
- 6.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 84 Oracle Analytics Trainings
- 15 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)
Comments
-
@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.
0 -
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
0 -
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.
0 -
In our organisation, we use Person Seniority Details = Senority Date and Seniority Date Setup/Seniority Rule Name = Enterprise Seniority Date.
0 -
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
0 -
@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.
1 -
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.
1 -
@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:
1
