E1: 43E: RSS Is Auto-Approved Instead of Going to Next Approver Level , Even If Authorization Required Flag Is ON
(Doc ID 2398325.1)
Last updated on DECEMBER 01, 2020
Applies to:JD Edwards EnterpriseOne Requisition Self Service - Version 9.1 and later
Information in this document applies to any platform.
The Requisition RSS is auto-approved, instead of going to the next approver level , even if <Authorization Required> flag is ON, when the originator is the first approver in the Approver List and the next level approver is expired (End effective date is less than Requisition date).
STEPS TO REPRODUCE
1.Set P43E094 Approval Authorities Constants on Commodity/Business Unit level.
2.Enter in P01012 Address Book a Parent Approval Route.
3.Set in P0150 the Approval route with more approvers as follow :
-Approver 1 with Threshold 1.00, End Eff Date = 30.07.2021
-Approver 2 with Threshold 10000, End Eff Date = 01.01.2018 = set in the past
-Approver 3 with Threshold 50000, End Eff Date = 30.07.2021
-another multiple approvers
Check ON the <Authorization Required> flag, for the approver list .
4.Set the Approver List in P43E09A (Manage Distribution List) for a specific Commodity item.
5.Approver 1 adds in P43E10 a requisition for Commodity/Business Unit combination with Extended Price of 6000.00 and Submit.
The next level approver for Approver 1 has expired (End effective date is less than Requisition date).
6.Inquiry the requisition in P43E15 (Requisition Inquiry - View Requisitions) application.
The requisition has been auto-approved instead of going to Approver 3 , even if <Authorization Required> flag is ON.
The requisition RSS has to go to be approved by the next available approver level from the Approver Distribution List.
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