My Oracle Support Banner

E-WF: Getting 'Think-time PeopleCode Event SQL' Errors After Adding An Escalation Calendar To A Flow (Doc ID 2435609.1)

Last updated on NOVEMBER 15, 2019

Applies to:

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


On : 9.2 version, Requisitions

Getting the following error below after adding an escalation calendar to an approval workflow, no matter what the module is. Becasue of this issue, cannot save and use transactions in any of the modules where workflow was enabled and a calendar was added.


Think-time PeopleCode event (Warning), but a SQL update has occurred in the commit interval. (2,148) EOAW_CORE.ENGINE.AppInst.OnExecute Name:EscalSubmit PCPC:96367 Statement:1427
Called from:EOAW_CORE.NotificationEventHandler.OnExecute Name:ProcessNotifications Statement:1394
Called from:EOAW_CORE.ENGINE.AppInst.OnExecute Name:Launch Statement:21
Called from:EOAW_CORE.LaunchManager.OnExecute Name:DoSubmit Statement:33
Called from:FUNCLIB_REQ.REQ_STATUS.FieldFormula Name:KickoffAW Statement:16

Think-time PeopleCode events such as messages requiring a user response cannot be executed if a SQL update, insert, or delete has occurred in the commit interval. Examples of PeopleCode that invoke update type of SQL includes Process Scheduler, TriggerBusinessEvent, or MarkWorked. A unit of work cannot contain both think-time events and update type SQL.

For this case, customer replication showing that the error happens in Payables module and in ePro module


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.