Updating Grade Ladder with Steps within Oracle HCM Cloud

Updating Grade Ladder with Steps within Oracle HCM Cloud

Published on: Category: Oracle

In Oracle HCM Cloud you can define a grade ladder with steps if your employees have steps within grades and the steps all have a specific salary rate. For example, someone is a sales manager and has grade 12. There are 8 steps within grade 12. Suppose the sales manager had step 4. In the grade ladder, you can define that there is a rate of €5000,- for grade 12 and step 8, which means a monthly gross salary of €5000,-.

You can also define a progression grade ladder, and create a progression default of progression into one extra step each year. If you define a progression grade ladder and fill in the grades, steps and rates, Oracle also automatically creates a normal grade ladder with these grade steps and rates. Updating the progression grade ladder will also result in updating the normal grade ladder and vice versa.

The rates can also be updated. In a lot of businesses, there are negotiations between the labor unions and the employers about the primary and secondary labor conditions. The outcome of these negotiations could be a salary raise of 2% by July 1st.

One strategy to cope with this requirement is to manually update all the rates within the grade ladder, for each step within each grade. But the rates can also be uploaded with HDL, the HCM Data Loader.

The input for HDL is quite a complicated file. It is easy to make a mistake when you copy the rates from Excel, which can lead to an error when uploading or worse, to wrongly uploaded rates. Also, it takes a lot of time to create these files manually.

Therefore, I set up a special report to create the input file for HDL (almost) automatically. This saves a lot of time and reduces the chances of making a mistake. I created the report in BI Publisher and not in OBIEE Analysis. The most important reason is that in the current version of HCM Cloud, the steps’ rates are not in any subject area. So I created it with SQL.

The model for the report consists of 4 SQL queries, corresponding with the 4 different layers that are required in the input file for HDL. The headers are already in the report. I created a simple report with the 4 sets of fields under each other. The report takes 3 parameters. One, is the effective date for the new grade ladder. In the case discussed above, this is July 1st. The second parameter is the legal employer. Normally, you would set up a grade ladder for each legal employer. The third parameter is the salary increase. In this case, this was 2%. In the SQL, I simply multiplied the current rate with (100 + salary increase) / 100. Thus, the output is already the complete grade ladder including the raise.

The next thing to do is run the report and download it as an Excel file. Open the file and save it as a CSV. Now open the CSV file with notepad or a smart notepad variant. You will see a lot of semicolons in the file. Sometimes more than one. All the semicolons at the end of a line must be removed. And every multiple set of semicolons must be replaced by only one, in such a way that the separator between each two values if only one semicolon. After this is done, the semicolons must be replaced by the pipe symbol: | This is the field separator for HDL.

The file can be zipped and uploaded, and then the update is done. Run the process “Synchronize Grade Step Rates” to also provide the employees with the new salary. Bear in mind that the salary updates will take place when running this process, by setting the parameters on the first page of the progression grade ladder setup:

Stefan van Glabbeek
About the author Stefan van Glabbeek

Oracle Fusion Apps HCM functional consultant at Qualogy. Stefan is also a senior functional and technical PeopleSoft HCM consultant with 14 years of experience. Overall, he has over 18 years of experience in IT.

More posts by Stefan van Glabbeek
Comments
Reply