Results for “wf_purge”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.WF_PURGE package body is a core administration utility within the Oracle Workflow (WF) schema. Its principal business function is to purge obsolete runtime data generated as workflow processes execute. Over time, the workflow runtime tables accumulate completed item activity statuses, notifications, attribute values, and related transactional rows. Without periodic housekeeping these tables grow indefinitely, degrading runtime performance and consuming tablespace. WF_PURGE provides the programmatic mechanism that the "Purge Obsolete Workflow Runtime Data" concurrent program and related administrative interfaces invoke to remove or archive this data according to user-supplied retention criteria. It additionally supports the archival of purge-eligible records by moving selected rows into companion history tables, thereby preserving an audit trail of workflow activity while releasing active runtime storage.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions. Their names indicate distinct responsibilities within the purge cycle:

• MOVE_TO_HISTORY — Relocates purge-eligible runtime rows into their corresponding history tables before deletion, preserving audit information.
• ITEM_ACTIVITY_STATUSES — Targets the item activity status records that represent individual workflow step executions.
• ITEMS — Addresses the workflow item master rows to be purged.
• ACTIVITIES — Handles purge logic relating to activity definitions and related data.
• NOTIFICATIONS and ITEM_NOTIFICATIONS — Manage the removal or archival of workflow notification records.
• ENTITY_CHANGES — Removes entity change tracking rows associated with purged items.
• TOTAL, TOTALPERM, and TOTALCONCURRENT — Provide count and aggregate reporting used to determine purge volumes and to present processing statistics.
• DIRECTORY and ADHOCDIRECTORY — Generate directory-path references used for purge or archival output locations.
• GETPURGEABLECOUNT — Returns the number of records eligible for purging, supporting pre-execution sizing and user reporting.
• ABORTERRORPROCESS — Handles error conditions and aborts the purge process gracefully when exceptions occur.

No parameter lists are documented, and none should be assumed.

Tables Accessed

The package operates across the principal workflow runtime and definition tables, resolved through APPS synonyms. Core runtime tables include WF_ITEMS and WF_ITEM_ACTIVITY_STATUSES, with the history table WF_ITEM_ACTIVITY_STATUSES_H populated during archival. Notification data is handled via WF_NOTIFICATIONS and WF_NOTIFICATION_ATTRIBUTES. Item-level attribute storage is read from WF_ITEM_ATTRIBUTE_VALUES. Supporting definition and structural tables include WF_ACTIVITIES, WF_ACTIVITIES_TL, WF_ACTIVITY_ATTRIBUTES, WF_ACTIVITY_ATTRIBUTES_TL, WF_ACTIVITY_ATTR_VALUES, WF_ACTIVITY_TRANSITIONS, WF_PROCESS_ACTIVITIES, and WF_ITEM_TYPES. Role-related data is maintained through WF_LOCAL_ROLES, WF_LOCAL_USER_ROLES, WF_ROLE_HIERARCHIES, and WF_USER_ROLE_ASSIGNMENTS. Additional purge targets include WF_COMMENTS, WF_DIG_SIGS, and WF_ENTITY_CHANGES. FND_CONCURRENT is referenced for concurrent program integration.

Usage Notes

WF_PURGE is not intended for direct ad-hoc invocation by end users. It is typically called by the Oracle Workflow administration concurrent programs and by the Workflow Purge administrative forms within Oracle EBS 12.1.1 and 12.2.2. The package depends on WF_CORE, WF_ENGINE, WF_ENTITY_MGR, WF_ITEM, and WF_ACTIVITY, and is referenced by 44 other database objects, confirming its role as a shared infrastructure component. Releases 12.1.1 and 12.2.2 share essentially the same package structure, so the documented procedures and dependencies apply to both. Administrators should schedule purges during low-activity periods, confirm retention criteria through GETPURGEABLECOUNT, and ensure adequate history tablespace when archival (MOVE_TO_HISTORY) is enabled.