Search Results wf_items




Overview
Explore in AI Chat

Overview

The WF_ITEMS table is the core runtime table for the Oracle Workflow engine within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Owned by the APPLSYS schema and part of the Application Object Library (FND) product, it serves as the master repository for every active and completed workflow process instance. Each row in this table represents a single, unique execution of a workflow, known as a "workflow item." It is the primary table for tracking the lifecycle, status, and key attributes of a workflow process from initiation to completion.

Key Information Stored

The table's structure is centered on uniquely identifying a workflow item and capturing its essential runtime state. The primary key is a composite of ITEM_TYPE and ITEM_KEY. The ITEM_TYPE references a defined workflow process definition from the WF_ITEM_TYPES table, while the ITEM_KEY is a unique identifier, often derived from business data like a transaction ID. Other critical columns include ROOT_ACTIVITY and ROOT_ACTIVITY_VERSION, which identify the specific version of the top-level process that was launched. The table also tracks the item's status (e.g., ACTIVE, COMPLETE, ERROR), start and end dates, and parent-child relationships via PARENT_ITEM_TYPE and PARENT_ITEM_KEY, enabling the modeling of complex, hierarchical workflow structures.

Common Use Cases and Queries

This table is fundamental for workflow monitoring, troubleshooting, and reporting. Common administrative queries include identifying long-running or errored processes, analyzing workflow volume, and tracing the lineage of nested workflows. A typical query to find active workflows for a specific item type would be:

  • SELECT item_key, begin_date, end_date, user_key FROM applsys.wf_items WHERE item_type = '<POAPPRV>' AND end_date IS NULL;

Another frequent use case is linking a workflow instance to its originating business transaction by joining on the ITEM_KEY, which often corresponds to a column in an application table (e.g., a Purchase Order header ID). Developers and administrators also query this table to understand workflow dependencies before performing data purges or archiving operations using the provided Workflow APIs.

Related Objects

WF_ITEMS has extensive relationships with other core Workflow tables, forming the backbone of the runtime engine. It is referenced by tables storing activity statuses (WF_ITEM_ACTIVITY_STATUSES), attribute values (WF_ITEM_ATTRIBUTE_VALUES), and notification details. As shown in the metadata, it maintains foreign key relationships to WF_ITEM_TYPES for the item definition and to itself (a self-referential key) for parent-child workflow links. Furthermore, it is referenced by several application-specific tables, such as OKE_K_COMMUNICATIONS (Oracle Contracts) and JTF_UM_SUBSCRIPTION_REG (User Management), demonstrating how workflow processes are integrated across EBS modules to manage business transactions.