My Oracle Support Banner

PRC:SSP: BPM Task Aggregation Issue During Purchase Order and Requisition Approvals (Doc ID 2441803.1)

Last updated on AUGUST 12, 2022

Applies to:

Oracle Fusion Purchasing Cloud Service - Version 11.13.17.11.0 to 11.13.18.05.0 [Release 1.0]
Oracle Fusion Purchasing - Version 11.13.17.11.0 to 11.13.18.05.0 [Release 1.0]
Oracle Fusion Self Service Procurement Cloud Service - Version 11.13.17.11.0 to 11.13.18.05.0 [Release 1.0]
Oracle Fusion Self Service Procurement - Version 11.13.18.02.0 to 11.13.18.05.0 [Release 1.0]
Information in this document applies to any platform.

Symptoms

Procurement Approval Issues: BPM Task Aggregation Issue during PO and Requisition Approvals

Flows: Purchase Order / Requisition Approval

When a purchase order that has more than one line with requesters, which positions share the
same superior position, is submitted for approval, the approver receives the approval notification
according to the expected behavior (BPM Configuration > Task Agreggation = Once per task),
but once he/she tries to approve, a delay of between a minute or two is produced from the moment of
pressing ‘Approve’ button and an error that brings out with an error message (1).


Then, when opening the Worklist work area, the same approval notification remains like if it wouldn't
have been opened and approved before from the bell.

After clicking on the notification, a window pops up with the PO approval request. The approver clicks
the ‘Approve’ button again and a delay of time produces itself again, but with a different error message
is presented (2).

Finally, after all the process described, the approver refreshes the worklist window but it doesn’t show
any changes. The notification remains.

ERROR
-----------------------

1.
An error occurred. Use the Worklist work area to perform the same action on this notification. (ATK-3315025)

2.
An internal error has occurred. Please contact the administrator or Oracle support for help.


STEPS
-----------------------
1. Create PO that has more than one line with requesters having positions that share the same superior position.
2. Submitted PO for approval.
3. Appprover receives the approval notification
according to the expected behavior (BPM Configuration > Task Agreggation = Once per task),
4. Attempt to approve and observe a delay of between a minute or two
5. Error message (1) is presented.
6. Open the Worklist work area, see the same approval notification (as if it was not actioned)
7. Clicking on the notification.
8. A window pops up with the PO approval request.
9. Click, the ‘Approve’ button, observe a delay and then a different error message is presented (2).
10. Finally, after all the process described, the approver refreshes the worklist window but it doesn’t show
any changes. The notification remains.



 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.