Contract Expiration Notification Is Not Triggered for Specific Internal Party Contacts Assigned to The Contracts

(Doc ID 2340106.1)

Last updated on DECEMBER 16, 2017

Applies to:

Oracle Procurement Contracts - Version 12.1.3 and later
Information in this document applies to any platform.


On : 12.1.3 version, Contracts Repository

Repository Contracts Expiry Notifications are not generated and sent to some specific Internal Party Contacts associated to the Repository contracts prior to the Expiration as per the setup in the Controls Tab

Expect the Repository Contract Expiry notifications to be generated and sent to all the Internal Party Contacts

The issue can be reproduced at will with the following steps:

1) Contracts Workbench Administrator(R)
2) For a Repository Contract in Signed status setup the Send before Expiration date and the Send to Contact Role from the Controls Tab
3) Run the concurrent - Contract Repository Expiration Notification and also the Workflow Background Process
4) Contract Expiration Notifications not sent to contacts as per the setup




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