My Oracle Support Banner

E-PC: GetNextNumberWithGapsCommit does not work with non-standard SQL table names (Doc ID 1306858.1)

Last updated on JULY 21, 2020

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***

Symptoms


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 ..."

ERROR
---------------
Oracle: ORA-00942: table or view does not exist
MS SQL: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

STEPS
---------------
The issue can be reproduced with the following steps:
1. Use GetNextNumberWithGapsCommit with any record that has a non-standard tablename

IMPACT
---------------
Unable to use GetNextNumberWithGapsCommit with any record that has a non-standard tablename, including PeopleTools tables.

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.