PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

Issues with GetNextNumberWithGapsCommit

edited Oct 10, 2019 11:51AM in PeopleTools and Lifecycle Management - PSFT (MOSC) 4 commentsAnswered

Hello,

I would like to check on the DB flag settings and the effects on function GetNextNumberWithGapsCommit. We have intermittent issues across application where this function is used. I was reviewing the support site but could not get a good article for this specific issue. The issues appears across modules like Absence, eperformance and Recruitment.

The issue is similar to below.

We see the code snippet for this and see the function used to retrieve the LAST_TXN_NUM.

/*Implementing try-catch approach-Murali 12/Aug/2016*/

   try

      &TEMP_TXN_NUM = GetNextNumberWithGapsCommit(GP_INSTALLATION.LAST_TXN_NUM, 99999999, 1);

   catch Exception &E

      WriteToLog(1, "Exception in GetNextNumberWithGapsCommit: DTTM=" | %Datetime | "-LAST_TXN_NUM=" | GP_INSTALLATION.LAST_TXN_NUM | "-Excep=" | &E.StackTrace);

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center