My Oracle Support Banner

Credit Line Approval Workflow Shows Incorrect Requester and Notifies them of Approval (Doc ID 2821088.1)

Last updated on NOVEMBER 12, 2021

Applies to:

Oracle Lease and Finance Management - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.5 version, Lease Authoring

ACTUAL BEHAVIOR
---------------
Find that when a credit line is submitted for approval, the parent workflow (OKLCLAPP) is created with the incorrect requester.
The requester does not have access to the credit line, or anything else in the credit line's OU.
When the credit line then approved, the wrong requester is then sent a notification to indicate that in the child workflow (OKLAMAPP).


EXPECTED BEHAVIOR
-----------------------
Expect the correct requester to be selected.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Using lease super user responsibility, a user submits a Credit Line for Approval.
2. The Credit Line Approval Workflows are kicked off using the incorrect Requester.
This confuses users as the person indicated as the requester has no access to the Credit Line as they are in a completely different Operating Unit.

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
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.