R12: Journal Approval Fails From Email Notification Leading to 100% CPU Usage
(Doc ID 1941690.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle General Ledger - Version 12.1 and later
Information in this document applies to any platform.
GL Journal Approval fails to update the journal status to Approved when submitted from email notifications.
Batch Approval status shows as 'In Process'.
STEPS TO REPRODUCE:
1. The profile options are set as below:
Journals: Find Approver Method= One Stop then Go Direct
Journals: Allow Preparer Approval = No
2. The first approver is approving the journal, then a notification is issued for the last approver
3. The last supervisor approves the journal, but the journal does not get approved
At the same time, the workflow enters into a loop executing the Find Approver GL statements millions of times, which spikes CPU to 100% in the end
4. When performed from the worklist notifications, the approval works fine, showing the journal as Approved
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|