E-PC: GetNextNumberWithGapsCommit does not work with non-standard SQL table names
Last updated on JULY 03, 2017
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.4 and later
Information in this document applies to any platform.
***Checked for relevance on 10-09-2012***
GetNextNumberWithGapsCommit does not work with non-standard SQL table names or PeopleTools tables. It assumes any record it deals with has PS_ added to the front of the record name for its table name.
For example, say there is a Record named GSC_COUNT with a non-standard SQL table name GSC_COUNT. When running GetNextNumberWithGapsCommit on this record, e.g.
&NEXT_NBR = GetNextNumberWithGapsCommit(GSC_COUNT.ACT_SEQ_NBR, 500, 1);
You get the following error:
PSAPPSRV.3384 ? 1-440 15.30.21 0.001000 SamCreateSecondary ---- Successful obtain Second DB connection
PSAPPSRV.3384 ? 1-441 15.30.21 0.000000 Cur#2.3384.FSM RC=0 Dur=0.000000 COM Stmt=UPDATE PS_GSC_COUNT SET ACT_SEQ_NBR = ACT_SEQ_NBR + 1
PSAPPSRV.3384 ? 1-442 15.30.21 0.001000 Cur#2.3384.FSM RC=0 Dur=0.000000 Rollback
PSAPPSRV.3384 ? 1-443 15.30.21 0.000000 Cur#2.3384.FSM RC=0 Dur=0.000000 Disconnect
PSAPPSRV.3384 ? 1-444 15.30.21 0.000000 SQL error. Stmt #: 865 Error Position: 0 Return: 601 - [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'PS_GSC_COUNT'.
Notice the SQL statement "UPDATE PS_GSC_COUNT ..."
Oracle: ORA-00942: table or view does not exist
MS SQL: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name
The issue can be reproduced with the following steps:
1. Use GetNextNumberWithGapsCommit with any record that has a non-standard tablename
Unable to use GetNextNumberWithGapsCommit with any record that has a non-standard tablename, including PeopleTools tables.
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