Handling of Pending Salary Transactions During Grade Step Progression Processes

The Run Grade Step Progression and Synchronize Grade Step Rates process can now block salary updates when a person has a pending salary transaction. Previously, the processes failed only when there was a pending assignment change.

If enabled, the processes fail the proposed progression or salary update. How you see the error depends on the grade ladder's confirmation type:

  • If Confirmation Type is Manual: You confirm on the Accept on the Review Proposed Progressions and Salary Updates page. If there’s a pending salary transaction, the action won't go through. The status remains as Not Processed, assignment and salary updates aren't applied, and you see this message: You can't propose another salary change because a transaction with a salary change is pending for approval. 
     

    Error message when there's a pending salary transaction and Confirmation Types is Manual

    Results for Process Page Showing an Error Message Because There's a Pending Salary Transaction and Confirmation Type Is Manual  

  • If Confirmation Type is Automatic: The Accept Updates child process attempts to post the salary update. If there’s a pending salary transaction, the attempt fails and assignment and salary updates aren't applied. An error is written to the log file. On the Review Proposed Progressions and Salary Updates page, Status is set to Failed. 
    Error message when there's a pending salary transaction and Confirmation Types is Automatic

    Log File Showing an Error Message Because There's a Pending Salary Transaction and Confirmation Type Is Automatic


     

With this enhancement outcomes align with assignment handling because salary changes are blocked when another salary transaction is pending.

Steps to enable and configure

To enable this feature, set the site-level profile value to Yes for the ORA_CMP_SKIP_SALARY_POST_FROM_GSP_WHEN_PENDING_APPROVAL_ENABLED profile option.

Tips and considerations

  • If you set the site-level profile value to No for the ORA_CMP_SKIP_SALARY_POST_FROM_GSP_WHEN_PENDING_APPROVAL_ENABLED profile option, the process applies the proposed progression or salary update even when a pending salary transaction exists. If an approver later reviews that pending salary transaction, the transaction will fail because the underlying data was changed.
  • If a pending salary transaction also includes an assignment update, you might see the process fail due to the pending assignment update instead of the salary update. Assignment-side failures aren’t controlled by a profile option, and this behavior hasn’t changed in this release.
  • If you run with Confirmation Type is Automatic and the number of failures in the Accept Updates log exceeds the Maximum Errors Allowed setting on the Batch Settings page, you’ll see the process end in failure. Otherwise it ends successfully, even if some transactions failed. This applies to any error type, not just pending transactions, and isn't new with this release. 
  • If your process hits a failure related to a pending transaction, you can complete or withdraw the pending transaction, then run the process again (Automatic) or click Accept again on the Review page (Manual).

Key resources