Procurement Contracts Alert Workflow (CS_CNTRCT_WF) - How to Prevent Multiple Worklist and Email Notifications From Being Generated For the Same Contract
(Doc ID 2613459.1)
Last updated on MAY 10, 2021
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
*** checked for relevancy 07-MAY-2021 ***
Procurement Contracts Alert Workflow (CS_CNTRCT_WF) is generating multiple Worklist entries and email notifications for the same PO contract. How to prevent multiple Worklist and email notifications from being generated for the same PO contract?
Step to replicate:
1. Verify the email address in the User Profile.
2. Verify in the User Profile's Workflow, Routing Preferences, that both Worklist and Email are selected.
3A) Validate the Contract Expire Date for a contract. Contract should be expired or near expiring.
3B) Verify the Contract has met its Maximum Contract Amount.
4. Set up the Contract Thresholds and Notifications so that a notification will be sent based on Date and Amount.
5. Run the Contract Alert Workflow process (CS_CNTRCT_WF) so that a contract expiration alert entry gets populated in the user's Worklist.
6. Logged in as the user, click on the 'Mark Worked' button for the entry on the Worklist page; see that the contract expiration alert entry gets removed from the user's Worklist.
7. Again run the Contract Alert Workflow process (CS_CNTRCT_WF); see that the same contract expiration alert entry gets added to the user's Worklist plus another email notification is sent to the user.
8. If the user does not click on the 'Mark Worked' button for the entry on the Worklist page, see that when the process (CS_CNTRCT_WF) is run any number of times, there is no new Worklist entry and no new email notification generated.
9. If the user does click on it, then each time the Contract Alert Workflow process (CS_CNTRCT_WF) is run it will trigger another expiration alert entry to the user's Worklist plus another expiration alert email notification to the user.
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