Why The Thread Id Not Created For The Default Approver When We Add The Adhoc Approver To The Requisition
(Doc ID 2521253.1)
Last updated on NOVEMBER 08, 2019
Applies to:PeopleSoft Enterprise SCM eProcurement - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Question -1: Thread Id did not create for default approver when we add the Adhoc Approvers while creating the Requisition. EOAW_USERINST table does not have any row until workflow hits the default approver step but only adhoc approvers.
In Ad-hoc approver scenario how the thread id is getting created for those approvers who are added before and after to the default approver and not for the default approver?
Question-2: How there was ad-hoc approver’s row for EOAWSTEP_INSTANCE ID on EOAW_USERINST table, even though workflow was not routed for ad-hoc approver who is added after the default approver?
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