My Oracle Support Banner

AME: Journal Approval Allows the Preparer to Approve the Journal After Re-assignment, Instead of Error: 3215: Reassigning the notification back to the sender or the owner of the workflow item is not allowed (Doc ID 2332494.1)

Last updated on JUNE 30, 2023

Applies to:

Oracle General Ledger - Version 12.2.4 and later
Oracle Workflow - Version 12.2.4 and later
Information in this document applies to any platform.
AME - Approval Management System


Journal approval is used integrated with Approvals Management Engine (AME). The patching was done according to this document in order to prevent the preparer to approve his own journal: (Doc ID 2875391.1) General Ledger Journal Workflow Approval Reassign to Preparer / Submitter Is Not Working as Expected. General Ledger Allows Approval Workflow Notification Reassign to Preparer / Submitter.

The user preparing the journal is not allowed to approve his own journal. However if the supervisor delegates back to the preparer, he is able to approve the journal disregarding other setups that do not allow this (for example, attribute  "ALLOW_REQUESTOR_APPROVAL" is set to false). The process works fine if the delegation points out to other user than the preparer.

The expectation is to get an error instead, 3215: Reassigning the notification back to the sender or the owner of the workflow item is not allowed.

1. GL Responsibility > Create a journal by User1
2. Submit for approval > This reaches User2
3. User2 delegates back to User1
4. User1 is now able to approve and post the journal




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.