1. HCM Data Loading Business Objects
  2. Guidelines for Loading Progression Grade Ladders

Guidelines for Loading Progression Grade Ladders

You need to understand key aspects of progression grade ladders to load them successfully using HCM Data Loader. For example, how you load rates differs depending on whether your progression grade ladder has grades with steps or without steps.

Before You Load Progression Grade Ladders

These referenced objects need to exist in the destination environment:

  • Grade and Grade Set

  • Legislative Data Group

If you're using action reasons, you also need to define or load them before you load progression grade ladders.

Progression Grade Ladder Attribute Settings

For the Progression Grade Ladder object, set the attributes shown here:

Attribute Without Step Value With Step Value
GradeType GRADE STEP
ProgressionStyleCode CMP_GSP_GP CMP_GSP_GSP
ProgActionCode CMP_GRADE_STEP_PROGRESSION CMP_GRADE_STEP_PROGRESSION
SalaryActionCode CMP_GRADE_STEP_PROGRESSION CMP_GRADE_STEP_PROGRESSION

Rate Loading

Here's how you load the rates:

Grade Type How You Load Rates
GRADE Use the separate Progression Grade Rate object.
STEP Use the Progression Step Rate and Progression Step Rate Value components of the Progression Grade Ladder object.
Tip:

Give the Progression Grade Ladder and Progression Step Rate components the same name because they've a one-to-one relationship. If you created a ladder with steps using the Progression Grade Ladder compensation task, the step rate and the ladder already have the same name.

Translatable Names

You can translate the name of the progression grade ladder using the Progression Grade Ladder Translation object.

  • If you're using grades with steps, you can also translate the name of the progression step rate. Use the Progression Step Rate Translation object. If you're using the same name for the progression grade ladder and progression step rate, as recommended, then use the same translated value for both.

  • If you're using grades without steps, you can also translate the name of the progression grade rate. Use the Progression Grade Rate Translation object.

Date and Salary Fast Formulas

You can optionally use fast formulas in your progression grade ladders to decide transaction dates or salary rates. If you do use them, the formulas must exist in the destination environment before you load Progression Grade Ladder objects.

  • Date formulas need to have the Salary Progression Date Determination Rule type.

  • Salary calculation formulas need to have the Salary Progression Rate Calculation Rule type.

When a fast formula decides the values of these date attributes, set the attributes to CMP_GSP_DATE_RULE:

  • ProgressionDateCode
  • SalaryChangeDateCode
  • RateChangeDateCode

Then specify the formula name on the ProgressionDateRuleName, SalaryChangeDateRuleName, or RateChangeDateRuleName attribute, as appropriate.

When fast formula decide the value for the SalaryCalculationMethodCode attribute, set the attribute to CMP_GSP_RATE_RULE. Then specify the formula name with the SalaryCalculationRuleName attribute.

The fast formulas must exist in the target environment before you load Progression Grade Ladder objects. Date formulas must have the Salary Progression Date Determination Rule type. Salary calculation formulas must have the Salary Progression Rate Calculation Rule type.

Progression Grade Ladder Deletion

You can delete a progression grade ladder if another object, such as an assignment, doesn't reference the ladder. Any linked grades and eligibility profiles are unaffected.

  • If the ladder doesn't have steps, you need to delete the linked Progression Grade Rate and Progression Rule objects separately.

  • If the ladder has steps, when you delete the ladder you're also deleting the linked step rates and values. You need to delete the linked Progression Rule object separately.

Reference

The Loading Data for Grade Step Progression document explains how you can load and update grade ladder and grade attributes for grade step progression. The document (ID 2569900.1) is on My Oracle Support at https://support.oracle.com.

Related Topics