R12: Journal Approval Fails From Email Notification Leading to 100% CPU Usage

(Doc ID 1941690.1)

Last updated on SEPTEMBER 27, 2017

Applies to:

Oracle General Ledger - Version 12.1 and later
Information in this document applies to any platform.
Journal Approval


GL Journal Approval fails to update the journal status to Approved when submitted  from email notifications.

Batch Approval status shows as 'In Process'.



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


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