Results for “root_activity_version”

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

Overview

WF_ITEMS is the core runtime table of the Oracle Workflow engine, owned by the APPLSYS schema and delivered under the FND – Application Object Library product in Oracle E-Business Suite 12.1.1 and 12.2.2. Every workflow process instance — whether generated by an order booking, an approval, a concurrent program notification, or a service contract communication — is represented by exactly one row in WF_ITEMS. The table therefore acts as the operational registry of all "in-flight" and historical workflow items, recording which process (ITEM_TYPE), which instance (ITEM_KEY), and where that instance sits within its possible parent/child hierarchy.

From a Data Vault modeling perspective, the metadata classifies WF_ITEMS as hub-leaning. A modeling suggestion would be to treat (ITEM_TYPE, ITEM_KEY) as a natural business key hub, since this pair uniquely identifies every workflow item and is reused as a foreign key by a broad set of dependent tables. Parent-child self-references within WF_ITEMS represent recursive links rather than satellites.

Key Information Stored

The physical schema in 12.2.2 documents 14 columns. The primary key is WF_ITEMS_PK, composed of the composite unique index on ITEM_TYPE and ITEM_KEY — these two columns are the business-key candidates and form the identity of the workflow instance. ITEM_TYPE references the workflow definition (WF_ITEM_TYPES), and ITEM_KEY is the internal instance identifier assigned at runtime.

Additional columns of operational significance include:

• ROOT_ACTIVITY / ROOT_ACTIVITY_VERSION — identify the starting activity and its version, linking to WF_ACTIVITIES.
• PARENT_ITEM_TYPE / PARENT_ITEM_KEY / PARENT_CONTEXT — establish the self-referencing hierarchy for sub-processes and nested workflow items.
• OWNER_ROLE — the role or user responsible for the item, used by the notification and routing engine.
• BEGIN_DATE / END_DATE — lifecycle timestamps for the item.
• USER_KEY — the human-readable identifier (for example, a PO number or contract ID) surfaced to end users.
• SECURITY_GROUP_ID — restricts visibility across application partitions, referencing FND_SECURITY_GROUPS.
• HA_MIGRATION_FLAG and INST_ID — support high-availability and multi-instance deployments.

Common Use Cases and Queries

Typical use cases include tracking open approvals, diagnosing stalled workflows, and reporting on process throughput. A common pattern joins WF_ITEMS to WF_ITEM_ACTIVITY_STATUSES to find current activity states:

SELECT i.item_type, i.item_key, i.user_key, i.begin_date, s.activity_name, s.activity_result
FROM wf_items i, wf_item_activity_statuses s
WHERE i.item_type = s.item_type AND i.item_key = s.item_key
AND i.end_date IS NULL;

The user's search term, OKE_K_COMMUNICATIONS, is the contracting communications table, which references WF_ITEMS via WF_ITEM_TYPE and WF_ITEM_KEY to associate each contract communication with its driving workflow. A query to surface communications and their owning workflow instance joins these two tables on that pair. Similar joins apply to OKE_CHG_LOGS, JTF_UM_SUBSCRIPTION_REG, and JTF_UM_USERTYPE_REG, which all carry WF_ITEM_TYPE / WF_ITEM_KEY or WF_ITEM_TYPE columns pointing back to WF_ITEMS.

Related Objects

The most significant dependent and referenced objects include:

• WF_ITEM_TYPES — joined on ITEM_TYPE; defines the workflow process header.
• WF_ACTIVITIES — joined on ITEM_TYPE / ROOT_ACTIVITY / ROOT_ACTIVITY_VERSION.
• WF_ITEM_ACTIVITY_STATUSES and its history twin WF_ITEM_ACTIVITY_STATUSES_H — joined on ITEM_TYPE and ITEM_KEY; hold per-activity runtime status.
• WF_ITEM_ATTRIBUTE_VALUES — joined on ITEM_TYPE and ITEM_KEY; stores instance-level attribute values.
• OKE_K_COMMUNICATIONS — joined on WF_ITEM_TYPE and WF_ITEM_KEY; contract communications.
• OKE_CHG_LOGS — joined on WF_ITEM_TYPE and WF_ITEM_KEY; contract change history.
• JTF_UM_SUBSCRIPTION_REG and JTF_UM_USERTYPE_REG — user-management registrations keyed by WF_ITEM_TYPE.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data partitioning.