Search Results wf_deferred




The APPLSYS.WF_DEFERRED table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 plays a critical role in the Oracle Workflow deferred processing mechanism. This table is part of the Oracle Workflow component, which is integrated into the Oracle Applications Technology Stack (APPLSYS schema). Below is a detailed breakdown of its purpose, structure, and functionality within Oracle EBS.

Purpose of WF_DEFERRED

The WF_DEFERRED table stores deferred workflow notifications and activities that are scheduled for asynchronous execution. Oracle Workflow uses this mechanism to improve performance by offloading time-consuming or non-critical tasks to background processes, ensuring that the main application remains responsive. This is particularly important in high-volume transactional environments where immediate processing could degrade system performance.

Key Columns and Structure

The table contains several key columns that define the deferred items and their processing requirements:
  • DEFERRED_ID: A unique identifier for each deferred item.
  • DEFERRED_TYPE: Specifies whether the item is a notification, activity, or another workflow-related entity.
  • ITEM_TYPE and ITEM_KEY: References the workflow item type and key, linking the deferred item to its parent workflow process.
  • DEFERRED_DATE: The timestamp when the item was deferred.
  • PROCESS_DATE: The scheduled execution time for the deferred item.
  • STATUS: Indicates the current state (e.g., PENDING, PROCESSED, ERROR).
  • ERROR_MESSAGE: Stores error details if processing fails.

Deferred Processing Mechanism

Oracle Workflow's deferred processing relies on the WF_DEFERRED table in conjunction with background engines:
  1. Deferral: When a workflow activity or notification is marked for deferred execution, a record is inserted into WF_DEFERRED with a future PROCESS_DATE.
  2. Polling: The Workflow Background Engine (WFENG) periodically queries this table for items where PROCESS_DATE is less than or equal to the current time.
  3. Execution: Eligible items are processed, and their status is updated to PROCESSED or ERROR.

Integration with Oracle EBS

In EBS 12.1.1 and 12.2.2, deferred processing is commonly used for:
  • Approval Workflows: Delaying notifications until business hours.
  • Batch Operations: Processing high-volume data updates asynchronously.
  • Error Handling: Retrying failed operations after a delay.

Administration and Troubleshooting

System administrators monitor and manage deferred items using:
  • Concurrent Programs: The "Workflow Background Process" (FNDWFPR) handles deferred item processing.
  • Queries: Direct SQL queries against WF_DEFERRED to identify stalled or erroneous items.
  • Purge Scripts: Oracle provides scripts to clean up old records (e.g., wfdepurge.sql).

Performance Considerations

Large volumes of deferred items can impact performance. Best practices include:
  • Regularly purging processed items.
  • Tuning the Workflow Background Engine's polling frequency.
  • Monitoring for long-running deferred tasks.
In summary, the APPLSYS.WF_DEFERRED table is a foundational component of Oracle Workflow's asynchronous processing architecture in EBS 12.1.1 and 12.2.2, enabling scalable and efficient workflow execution while maintaining system responsiveness.