Users Are Not Receiving Expiration Notifications For Repository Contracts
Last updated on MARCH 08, 2017
Applies to:Oracle Procurement Contracts - Version 11.5.10 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 16-Jul-2014***
Find that user has set Contract Expiration Notification to be sent to a specific role when authoring the contract. However, the notifications are not getting sent to the specified Role even though the "Contract Repository Expiry Notifications" concurrent program is scheduled and run along with the Workflow background process.
Expect the contract expiration notification to be sent to the specified role when set.
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