My Oracle Support Banner

GPCH: When Upgrading to HCM 9.2.045 Invalid SQL Errors Occurred. (Doc ID 2978957.1)

Last updated on NOVEMBER 15, 2023

Applies to:

PeopleSoft Enterprise HCM Global Payroll Switzerland - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

While applying the HCM 9.2.045, the following scenarios have been encountered: 

Scenario 1:

Invalid SQL in GPCH_AE_ELM.ELM_XML.Step01.OnExecute causes process to fail.

The PeopleCode action in AE GPCH_AE_ELM, section ELM_XML, step Step01 fails with the error below:

Error message:

11:34:24 "SQL error. Function: SQLExec Error Position: 0 Return:

  8601 - [Microsoft ODBC Driver 17 for SQL Server][SQL Server]Incorrect syntax near 'TOT'. [Microsoft](ODBC

  Driver 17 for SQL Server SQL Server Statements) could not be prepared. (SOLSTATE 42000) 8180 Statement:

  DELETE FROM PS GPCH EG PTOTALS TOT WHERE

  NOT EXISTS (SELECT 'X' FROM

  PS GPCH EG PERSON XB WHERE

  TOT.GPCH EG DOMAINID =

  XB.GPCH_ EG DOMAINID AND TOTGPCE R$ PAY YEAR =

  XB GPCH R¢ PAY YEARAND TOT COMPANY =

  XB.COMPANY AND TOT.GPCH SI PROV TYPE =

  XB.GPCH_SI_PROV_TYPE AND TOT.GPCH_SI_PROV_

  CD = XB.GPCH SI PROV CD)"

11:34:24 "SQL error in Exec. (2.280)

GPCH AE ELM.ELM XML.GBL. default. 1900-01-

01. Step01.OnExecute PCPC: 31879 Statement: 452"

11:34:24 "Process 241458 ABENDED at Step

GPCH_AE_ELM.ELM XML.Step01 (PeopleCode) -- RC

= 8"


Scenario 2: 

On lines 416 and 420 of GPCHSI8X.SQR, the SQL statement references "JC.Emplid". SQL Server is case-sensitive, so "Emplid" is not the same as "EMPLID".

Scenario 3: 

The PeopleCode action in AE GPCH_AE_ELM, section ELM_XML, step Step01 fails. On lines 651 and 654, the DELETE statement assigns a table alias. 

Scenario 4:

When attempting to add a new Run Control in either the Monthly or Yearly XML CHE components on line 2 of GPCH_RC_EGOVT.GBL.GPCH_RC_PAYROLL.GPCH_RC_PAY_YEAR.FieldDefault, there is a SQL SELECT that assumes there are rows in GP_CAL_RUN_DTL with RUN_TYPE = 'KWPAY'. 

Steps to reproduce the issue:

1. Apply HCM 9.2.045.
2. Notice that the above issue occurs.

Changes

 

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.