My Oracle Support Banner

EEX 9.2: Fatal SQL Error On Timesheet When Project/Activity Is On Two Rows With Hours Allocated To Both Rows (Doc ID 2750861.1)

Last updated on APRIL 26, 2021

Applies to:

PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Fatal SQL error on timesheet when project/activity is on 2 rows with hours allocated to both rows.

ERROR

SQL error in Exec. (2,280) TE_TIME_ENTRY.GBL.SavePreChange PCPC:19847 Statement:200
During the execution of SQL, an error occurred in the Exec subroutine. The preceding message should have described the SQL being executed.


STEPS

The issue can be reproduced at will with the following steps:

1. Create a new timesheet and ensure there are 2 rows with the same project/activity that have hours allocated to them.
2. Try to save for later and it is allowed.
3. Now go back to the time report and try to save it again and "A fatal PeopleCode SQL error occurred. Please consult your system log for details" is displayed.
4. Click on ok and the above error message is displayed.



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.