Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OTBI Subject Areas missing Grade Ladder / Grade Step Values
Organization Name
WM MORRISON SUPERMARKETS PLC
Description
Seeded metric value dimensions in OTBI Compensation - Salary Details and Workforce Management - Grade Rates subject areas are not populated with any data from HCM Compensation for Grade Ladders / Grade Step values hence there is no ability to report on "Minimum","Mid Value", "Maximum" and "Value".
OTBI Compensation - Salary Details and Workforce Management - Grade Rates have 'Descriptor' dimensions for Grade Ladders and Grade Steps but the metric 'Facts' "Minimum","Mid Value", "Maximum" and "Value" are only populated for "Grade Rates" not "Grade Steps".
Use Case and Business Need
No ability to report on compensation "Minimum","Mid Value", "Maximum" and "Value" Grade Step values to HR Management and Line Managers
More details
OTBI Compensation - Salary Details and Workforce Management - Grade Rates have 'Descriptor' dimensions for Grade Ladders and Grade Steps but the metric 'Facts' "Minimum","Mid Value", "Maximum" and "Value" are only populated for "Grade Rates" not "Grade Steps"
Original Idea Number: 0179c139de
Comments
-
(I'm just noting a relevant ER#27190781)
0 -
It's a known issue that we don't have the step rate values in OTBI. These come from PER_RATE_VALUES_F table where object type = Step. We do have grade rate values, which come from PER_RATE_VALUES_F where object type = Grade.
PER_RATE_VALUES_F also has columns for min/mid/max which are populated in the various UIs when object type = Grade. Theoretically, the table can store min/mid/max where object type = Step but we don't have any current UI which allows entry of these attributes when object type = step. Question: Is there a requirement to store ranges for steps? If so please you may want to log a separate Idea. Otherwise you may find these turn up zero/blank in reports even if we implement this enhancement.
Some customers will use the grade ranges (for min/mid/max) rather than step ranges and that is already possible today. You just need to create a grade rate including the same grades which are in your grade ladder, and associate that to the salary basis. This is optional - some customers don't bother with ranges when grades have steps.
It doesn't solve the whole problem because step rate value is still not included in OTBI.0 -
Thank you, much appreciated.
0 -
Stephen it would help us immensely if you add your thoughts on how you use the ranges.
0 -
Hi Stephen, scoping is under way, and we are interested to know more about your request. May I have a greater understanding of the use cases?
0 -
This functionality was delivered in 22.04 / 22B. Please see: https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/compensation/releases/22B/22B-compensation-wn.htm#F22334
1 -
Futher functionality is also available in: 23C New Subject Area - Compensation - Workforce Assignment Salary Real Time https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/compensation/releases/23C/23C-compensation-wn.htm#F28574 New Subject Area - Compensation - Workforce Assignment Salary History Real Time https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/compensation/releases/23C/23C-compensation-wn.htm#F28575 24A Dashboards for above https://community.oracle.com/customerconnect/discussion/723415/otbi-compensation-was-custom-dashboards
0