E-PC: GetNextNumberWithGapsCommit does not work with non-standard SQL table names
(Doc ID 1306858.1)
Last updated on JULY 27, 2022
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.4 and later
Information in this document applies to any platform.
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:
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.
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