GPCH: The Solution Delivered Through Bug 35088622 is Incomplete (Company Social Insurance CHE Screen) (Doc ID 3001524.1)

Last updated on FEBRUARY 02, 2024

Applies to:

Symptoms

While testing Bug 3508862 (Company Social Insurance CHE screen) in a PUM Image 46 Demo environment, the following was noticed:

The solution delivered via the above bug solved the original problem, but introduces a new issue: Once the calendar field ( EFFDT) is changed, the same default data is generated.
Functionally, it is correct that the default data is retrieved when the date field is adjusted. But this should be reduced to the contribution values.
The AHV and ALV status values should not be affected. Nor should they be affected when a new row is added.

Steps to replicate the issue:

1. Navigate to Menu > Set Up HCM > Product Related > Global Payroll & Absence Mgmt > Social Security / Insurance > Company Social Insurance CHE and perform the actions below:
- Correct History Mode – open the screen for company KW1 (Effective Date 01.01.2021)
- Change *AHV Status to « 2 Employer »
- Change *ALV Status to « 2 Employer »
- SAVE 

2.  Add a new row (+)
- Under PUM-46 the new values of AHV / ALV / Solidarity Status are no more copied but taken from the former row (OK).
- Contribution values are retrieved with reference to the default date (Today).
 
3. Adapt the « Effective Date » in order to bring it to the first day of the year (i.e. 01.01.2023)
- The new good values of « AHV Status « and « ALV Status « are now changed to the standard values, although it should.
- The contribution values are adapted in order to the changed effective date.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.