My Oracle Support Banner

GP CORE: After Applying PUM 48, Payroll process Is Either Failing with "ORA-01400: cannot insert NULL into ("PSMAN"."PS_GP_RSLT_ACUM"."USER_KEY2")" or Is Not Populating Values In USER_KEY3 and USER_KEY2 (Doc ID 3025953.1)

Last updated on MAY 30, 2024

Applies to:

PeopleSoft Enterprise HCM Global Payroll Australia - Version 9.2 to 9.2 [Release 9]
PeopleSoft Enterprise HCM Global Payroll Core - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Non-Unicode Database Environments

Symptoms

The following issues have been discovered when running the payroll process after applying PUM Image 48.

Issue 1: The process GPPDPRUN runs to no Success when running the pay calculation and the PI and SOVR are present for the employees being processed. Without PI and SOVR, the process is completed successfully.

Navigation: Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll

Application Program Failed
Action Type : SQL UPDATE
In Pgm Section : SQLRT: EXECUTE-STMT
With Return Code: 01400
Error Message : ORA-01400: cannot insert NULL into ("PSMAN"."PS_GP_RSLT_ACUM"."USER_KEY2")
Stored Stmt : GPPRDMGR_I_ACUM

Issue 2: When running payroll with retro, User Field 2 and User Field 3 are empty for Non Unicode.
Navigation: Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll

Run payroll with retro and check the results for an employee.
Notice in Earnings and Deductions > User Fields, the User Field 2 or User Field 3 are empty.

Navigations:
Global Payroll & Absence Mgmt > Absence and Payroll Processing > Review Absence/Payroll Info > Results by Calendar > Calendar Results
Global Payroll & Absence Mgmt > Absence and Payroll Processing > Review Absence/Payroll Info > Results by Calendar Group > Calendar Group Results


Issue 3: As a result of these 2 issues, the Single Touch Payroll (STP) Prep Process is failing with the following error:

Navigation: Global Payroll & Absence Management > Authority Correspondence > STP Payroll Event Prep AUS

ORA-12899: value too large for column "PSMAN"."PS_GPAU_STP_TMP4"."BALANCE_GRP_NUM" (actual: 15, maximum: 3)
Failed SQL stmt: insert into PS_GPAU_STP_TMP4

 

Changes

 Apply PUM 48.

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Changes
Cause
Solution
References


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