How To Diagnose Issues Related To Purge Of Purchasing Workflow Data That Remain Even After Running The 'Purge Obsolete Workflow Runtime Data' Concurrent Program? (Doc ID 458886.1)

Last updated on DECEMBER 10, 2024

Applies to:

Oracle Purchasing - Version 11.5.10.2 to 12.2.10 [Release 11.5 to 12.2]
Information in this document applies to any platform.

Goal

How can we diagnose issues related to purge of workflow data (workflow items, notifications) related to purchasing, that remain in the database even after running / scheduling the 'Purge Obsolete Workflow Runtime Data' concurrent program?

Solution

	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

Goal

Solution

Step 1: Run the 'Purge Obsolete Workflow Runtime Data'

Step 2: Purging Purchasing Workflows

Step 3: Analyzing Workflow Runtime Data That Have Not Been Purged

Step 4: Retrying The Workflow With Error

Step 5: Closing Open Notifications Tied To The Workflow

Still Have Questions

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How To Diagnose Issues Related To Purge Of Purchasing Workflow Data That Remain Even After Running The 'Purge Obsolete Workflow Runtime Data' Concurrent Program? (Doc ID 458886.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

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