EEX9.2: EX_EMPNOTIFY Process Causes Performance Issue in Saving or Submitting an Expense Report

(Doc ID 2147987.1)

Last updated on JUNE 10, 2016

Applies to:

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


Contention issue is occurring when EX_EMPNOTIFY process is running and at the same time the employee, whose MyWallet entry is getting updated, is pulling the same MyWallet entry into Expense Report and trying to save or submit. The save or submission does not happens until the process goes to Success or No Success.

1. Load a new AMEX GL1025 file / update EX_NOTIFY_SW flag in EX_TRANS record as N (please make sure the count of transaction and distinct Employee ID should be 1000+).
2. Run the EX_EMPNOTIFY process.
3. Monitor the Employee ID for which the MyWallet entry is getting updated.
4. For the same Employee ID, try to create Expense Report by pulling the same MyWallet entry
5. Try saving it.

Expected result:
Expense report should be saved quickly.

Actual result:
Expense report goes into processing state until the EX_EMPNOTIFY process goes to either Success or No Success.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms