The API HR_MAINTAIN_PROPOSAL_API.INSERT_SALARY_PROPOSAL Does Not Round New Salaries While Loading Where as the New Salaries Are Rounded Off When Entered Through the Application. (Doc ID 2092092.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Human Resources - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.4 version, Application Programming Interface

ACTUAL BEHAVIOR
For Canadian currently, there has been discrepancy between the Oracle application (Core Apps) and API HR_MAINTAIN_PROPOSAL_API.INSERT_SALARY_PROPOSAL to load new salaries.
When the new salaries are entered through the Application, the precision value is set to 4 whereas this is not the same when new salaries will be loaded using the API.

For eg, when a salary like 123.1234156789 is loaded via core application, it will be rounded off and stored in salary table, as 123.1234.
However, if the same salary (123.1234156789) is loaded using API executed as a script, the salary is loaded as it is, i.e. 123.1234156789.


EXPECTED BEHAVIOR
It is expected that the API uploads the salary in the same precision as the Application does.


STEPS
The issue can be reproduced at will with the following steps:
1. Upload a new salary with a salary like 123.12345678
2. The application saves the salary with the precision as 123.1234.
3. Upload the same salary using API which stores the data as 123.12345678.


ADDITIONAL INFORMATION
The PL/SQL anonymous block used to call the API to upload the salary is as below:

  --
  BEGIN
     --
     HR_MAINTAIN_PROPOSAL_API.INSERT_SALARY_PROPOSAL (
         p_pay_proposal_id => v_pay_proposal_id,
         p_assignment_id => v_assignment_id,
         p_business_group_id => v_business_group_id,
         p_change_date => x_change_date,
         p_next_sal_review_date => x_next_sal_review_date,
         p_proposal_reason => v_proposal_reason,
         p_proposed_salary_n => x_proposed_salary,
         p_date_to => null,
         p_object_version_number => v_ovn,
         p_multiple_components => 'N',
         p_approved => x_approved,
         p_element_entry_id => v_element_entry_id,
         p_inv_next_sal_date_warning => v_inv_next_sal_date_warning,
         p_proposed_salary_warning => v_proposed_salary_warning,
         p_approved_warning => v_approved_warning,
         p_payroll_warning => v_payroll_warning);
     --
  END;
  --



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms