E-WF:Page Composer - Fatal PeopleCode SQL Error Occurred (Doc ID 2224055.1)

Last updated on MARCH 13, 2017

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.55 and later
Information in this document applies to any platform.

Symptoms

On : 8.55 version, Page Composer

Page Composer - Fatal PeopleCode SQL error occurred in sql server as SQL Server does not support aliases on Delete statements.

method dataCleanUp
  /*** */
  /*** Data clean-up for level 4 (really at level 3) style overrides. Buffer is in level 3 and sometimes needs extra data clean-up when field is deleted */
  /*** */
  /*** delete orphans for fields that were deleted */
  SQLExec("DELETE FROM PS_EOPCFIELD_STYLE S WHERE NOT EXISTS (SELECT 'X' FROM PS_EOPC_FIELD F WHERE F.EOPCMAIN_ID = S.EOPCMAIN_ID AND F.EOPCFORMAT_ID = S.EOPCFORMAT_ID AND F.EOPCFIELD_ID = S.EOPCFIELD_ID)");
  /*** delete any old data where style override is null or blank */
  rem Removed 8/8/16 SQLExec("DELETE FROM PS_EOPCFIELD_STYLE S WHERE EOPCSTYLEHTML IS NULL AND EOPCSTYLECLASS = ' ' AND EOPCSTYLECLASS_LBL = ' '");
end-method;

ERROR
-----------------------

SQL Server does not support aliases on Delete statements.
PSAPPSRV.23212 (3634) 1-1300157 00.16.29 2927.237000 SQL error. Function: SQLExec
  Error Position: 0
  Return: 8010 - [Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'S'.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Statement(s) could not be prepared. (SQLSTATE 37000) 8180
  Original Statement: DELETE FROM PS_EOPCFIELD_STYLE S WHERE NOT EXISTS (SELECT 'X' FROM PS_EOPC_FIELD F WHERE F.EOPCMAIN_ID = S.EOPCMAIN_ID AND F.EOPCFORMAT_ID = S.EOPCFORMAT_



STEPS
-----------------------

The replication steps are not clear. However upon checking the peoplecode of EOPC_MAIN.mainData.dataCleanUp, I can see the following.
SQLExec("DELETE FROM PS_EOPCFIELD_STYLE S WHERE NOT EXISTS (SELECT 'X' FROM PS_EOPC_FIELD F WHERE F.EOPCMAIN_ID = S.EOPCMAIN_ID AND F.EOPCFORMAT_ID = S.EOPCFORMAT_ID AND F.EOPCFIELD_ID = S.EOPCFIELD_ID)");

This statement is not allowed in SQL server.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot approve transactions.

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