10Base Pay Lookups and Troubleshooting

This chapter contains the following:

HR specialists and line managers can use incremental salary components to itemize new or adjusted salary, to reflect the different reasons for their allocations. Here are the incremental components bundled in the implementation:

  • Adjustment: Regular and automatic adjustment

  • Cost of Living

  • Equity: Adjustment to correct salary compression or inversion

  • Location

  • Market: Adjustment due to salary being out of line with the market

  • Merit

  • Promotion

  • Progression: Regular and automatic adjustment

  • Structured: Adjustment dictated by union or employment contract, such as an increase after three months

You can change or add components to the CMP_SALARY_COMPONENTS lookup type to better support your reporting policies for salary allocations. Use the Manage Common Lookups task in the Setup and Maintenance work area.

Itemization

Incremental component itemizations are stored and used to calculate new salary. When component values change, the payroll element holds the new salary amount calculated from the component adjustments, but doesn't receive individual component amounts for processing. The incremental values entered in the salary record apply only to that record and don't apply to any future salary records.

HR specialists and line managers can use simple salary components to itemize new or adjusted salary, to reflect the different reasons for their allocations. Here are the simple components bundled in the implementation:

  • Basic salary

  • Housing allowance

  • Special allowance

  • City allowance

  • Transport allowance

  • Travel allowance

  • Wage progression rate

  • Variable allowance

  • Overall salary

You can change or add components to the ORA_CMP_SIMPLE_SALARY_COMPS lookup type to better support your reporting policies for salary allocations. Use the Manage Common Lookups task in the Setup and Maintenance work area.

Itemization

Simple component itemizations let you maintain the values for the components and you typically configure them to calculate new salary. When simple component values change, the new salary amount is recalculated. The payroll element holds this new salary amount, but doesn't receive individual component amounts for processing.

Here are some salary-related issues that you may encounter and solutions to help you fix them.

Issue Solution

The salary element entry wasn't created

The element associated with the salary basis won't be created if any inconsistencies exist between the element eligibility and the payroll data of the person's assignment.

Using the Element Entries task in the Person Management work area, set the Effective Date to same date as the salary start date. Then search for the salary basis element in the Element Name column. If the element isn't listed, the person isn't eligible for the element. You need to verify the eligibility and effective dates configured for the element.

The salary ranges are incorrect for an hourly person

Check the annualization factor of the grade rate associated with the salary basis. The annualization factors for the salary basis and grade rate might differ, even if the frequency for both is Hourly. Salary range calculations use the frequencies and factors of the salary basis and the grade rate. If they don't match, the grade rate values are converted to those of the salary basis.

Salary changes are stuck in the approval flow

An individual's salary page has a message that's something like this: Changes to this data are pending approval. HR specialists and compensation managers or administrators don't have a Withdraw option for the transaction in their worklist. And sometimes, the person record gets locked after changing the salary.

Ask the person who submitted the salary change to use their worklist to withdraw the change. They can also see who the current approver is, so they can ask the approver to approve or reject the proposed changes.

If you still see the pending approval notification in the Change Salary flow, your approvals administrator can use the transaction console to cancel the change. If you still see the pending approval, have your help desk log a bug with Oracle Support against the Salary component of Oracle Fusion Workforce Compensation.

Salary notifications are blank

The person may have a custom role. Add the Approve Salary Updates privilege to their application role. Or, add these three resources to a custom entitlement and add the entitlement to their application role.

  • HcmDetectCompletedTransaction.xml

  • ChangeSalaryApprovalTask_TaskFlow.xml

  • ChangePayNtfsFlow.xml

The salary details in notifications are blank

People need to see salary information, but not make any changes.

The person probably doesn't have a compensation role. Depending on whether they should have read-only or read and write accesses to the salary details, add one of these job roles:

  • View Salaries

  • Manage Salaries

For detailed steps to implement this solution, see the Salary Details Are Not Visible in Approval Notifications - You Do Not Have Permission to Access this Information document (ID 2212593.1). The document is on My Oracle Support at http://support.oracle.com.

Grant them access to the Compensation Info task, which they can review salary information. Reserve the Change Salary role for the people who need to manage the salary data.