Notification Titles For Base Requisition and Amendment Displayed Incorrectly In Approvers Notification (Doc ID 1934060.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Contract Lifecycle Management for Public Sector - Version 12.2.2 to 12.2.4 [Release 12.2]
Oracle Purchasing - Version 12.2.4 to 12.2.4 [Release 12.2]
Information in this document applies to any platform.

Symptoms

In Oracle iProcurement with Oracle Contract Lifecycle Management, Release 12.2.3, the title of the requisition approval notification received by the approver user shows "Purchase Requisition Amendment" when there is not an amendment made to the requisition.

It is expected that the notification show "Purchase Requisition" instead of "Purchase Requisition Amendment" for a new requisition that has yet to be approved.


Steps To Reproduce

The issue can be reproduced at will with the following steps, using CLM iProcurement responsibility:
1. As the requestor, create a new requisition and submit for approval.
The confirmation page shows "Requisition HDTRA1413936 has been submitted to (user) for approval."
2. The approver logs in, and sees the notification in the Worklist with title "Purchase Requisition Amendment HDTRA1413936 for (user)".
3. The approver clicks the notification link, and the title is still displayed "Purchase Requisition Amendment HDTRA1413936 for (user)".
4. The approver clicks the Approve button to approve the requisition. The page "Sign Notification: Purchase Requisition Amendment HDTRA1413936 for (user)" appears.
The approver clicks the Sign button to sign the notification.
5. The requestor logs in again, and the worklist shows the notification title correctly - "Purchase Requisition HDTRA1413936 has been approved". The word "Amendment" does not appear in the notification title (which is correct since there are no amendments on the requisition).


The reverse case is also occurring. If a user creates a requisition amendment, the approver's notification is seen as a base notification "Purchase Requisition" instead of "Purchase Requisition Amendment".



Business Impact

Due to this issue, approver users are confused by the misleading notification titles and it leads to unnecessary follow-up with the requestors and/or having to check the Requisitions page to determine the actual document type.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms