ORA-20002: User Does Not Have Access to BSA Notification Details After Delegating
(Doc ID 453406.1)
Last updated on FEBRUARY 13, 2019
Applies to:Oracle Order Management - Version 126.96.36.199 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
When a Blanket Sales Agreement is being approved and the approver delegates and/or transfers the approval to another user, the person that creates the BSA can no longer view the approval history. No one can see the approval history except the designated Workflow administrator.
In the Workflow Administrator Web Applications responsibility, the user can change the Workflow System
Administrator to *. However, this is not a viable workaround because all customer service responsibilities
can now see the notification details.
The requirement is to have the user who created the BSA be able to see all the approval notification details. This works fine if the approval was not delegated or transferred.
The issue can be reproduced at will with the following steps:
1. User A creates a new BSA using the Order Management Super User responsibility. BSA status is 'Draft'.
2. User A clicks on the Submit Draft button.
BSA status changes to 'Pending Internal Approval'.
User A can see the notification details at this point by clicking on the Actions > View Notification Details. The BSA creator can see the entire approval sequence through rejection and approval as long as there is no transfer or delegations performed in the approval sequence.
3. User B receives the notification and determines that another user C needs to approve the notification.
4. User B then delegates or transfers the notification to User C. It is at this point where the creator User A can no longer see the notification details. Neither the supervisor or creator can tell who has approved the BSA.
The following error is received when trying to view the details:
ORA-20002: 3207: User 'A' does not have access to notification 107789.
ORA-06512: at 'APPS.WF_ADVANCED_WORKLIST' , line 82 ORA-06512: at line 1
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