Contract Repository Expiry Notifications is Sending Second Notification for a Contract
Last updated on MARCH 08, 2017
Applies to:Oracle Procurement Contracts - Version 12.1.3 and later
Information in this document applies to any platform.
***Checked for relevance on 13-Oct-2014***
On 12.1.3 version, Contracts Repository expiry notification for contracts is sending unnecessary second notification for a contract in some circumstances.
Suppose V2 is the second version, the Application is sending a second expiry notification for the immediate previous version V1, when a new version V2 that is either in DRAFT status or SIGNED and expiring in the future is created (date greater than current date + Notification period ).
While creating a new version for the contracts, in table okc_rep_contract_vers, the flag "wf_exp_ntf_item_key" is blanked (NULLified).
Expected notifications to be sent out ONCE only for any contract version.
Steps to Reproduce
1. Create a contract (V1) eligible for a notification, sign it.
2. run the expiry notification program: user receive the notification.
3. Create a draft ( V2) . Run the program again: Find that an other notification is sent out for V1 again (even with some data from V2)
The issue has the following business impact: Due to this issue, users are confused by notifications.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms