Return For Correction - Cannot Select Initiator when Previous Approver Updated Transaction
(Doc ID 1476515.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Human Resources - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version,
Find that when users want to return a transaction for correction, the 'return for correction' cannot be assigned to the initiator of the transaction
Expect functionality to work as it was working in r11 where return for correction showed ALL actors in the approval flow, including the initiator
The issue can be reproduced at will with the following steps:
1. employee self-service
2. select any SIT function, enter all data
3. and submit the transaction
4. First Approver <Customer> receives approval notification and update the action (the SIT)
5. <Customer> has to add some data so she clicks "Update Action"
6. <Customer> clicks the update button and adds the required information
7. then clicks on "Continue"
8. then Next
9. Then resubmits.
10 Flow goes to next approver; User is now <Customer>.
11 this approver wants a correction to be made on the data.
This correction should come from the flow initiator <Customer>. However, when <Customer> click the Return For Correction Link, <Customer> gets the following screen where he can only return the action to <Customer> (first approver, not initiator)
RESEARCH FROM CUSTOMER : cause of the issue
ReturnForCorrVO.xml with version 120.6.12010000.3; which states a condition:
AND pah.approval_history_id IN
FROM pqh_ss_approval_history p1
WHERE p1.transaction_history_id = :5
AND p1.action <> 'RFC'
the approval _history_id is incremented after an "update action"/"resubmit". Any approver/initiator having a lower approval_history_id cannot be selected for RFC
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