Approver Not Being Reset After Withdraw and Change The Requisition When Using Position Hierarchy And Forward Method Is Direct.

(Doc ID 1621799.1)

Last updated on JUNE 01, 2016

Applies to:

Oracle iProcurement - Version 12.1.3 and later
Information in this document applies to any platform.


On Applications 12.1.3
Find that Approver is not reset to correct person after making changes that should reflect in change in approval list.

-- Expected Behaviour
To see the Approver reset correctly.

-- What is working
Charge Account and Approver list is changed correctly when using Position Hierarchy and forward method as Hierarchy.

-- Steps
The issue can be reproduced at will with the following steps.
1. Create a requisition with delivery to location , charge is generated correctly and approver list has user : 'A' . Submit the requisition.
2. Now change the requisition (withdraw) and change to delivery location to onetime location, charge account is changed and approver list has now user : 'B' . Submit the requisition.
3. Now again change the requisition (withdraw) and change the delivery to location to proper location as initial value and charge account is changed . However this time the approver remains as 'B'

Business Impact
The issue has the following business impact:
Due to this issue, users cannot submit the requisition with correct approver.


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