Results for “process_activity”

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

Overview

WF_ITEM_ACTIVITY_STATUSES is the runtime status table for Oracle Workflow work items. Owned by the APPLSYS schema and shipped with FND — Application Object Library, it records the state of every activity instance executed within a workflow process. Where WF_ITEMS captures the overall work item, WF_ITEM_ACTIVITY_STATUSES captures the granular, per-activity execution history: which activities have been entered, their status, results, assignments, timing, and any error diagnostics generated at runtime. In Oracle EBS 12.1.1 and 12.2.2 the table remains a core component of the Workflow engine, and its contents are heavily exercised by the Notification System, the Workflow Monitor, the background Workflow Agent listeners, and the Business Event System.

From a dimensional modeling perspective, the documented foreign-key footprint supports classifying this object as a link (associative) table. It connects work items (WF_ITEMS), process activity definitions (WF_PROCESS_ACTIVITIES), notifications (WF_NOTIFICATIONS), and security groups (FND_SECURITY_GROUPS). This is a heuristic suggestion rather than a fixed ETRM classification.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains 19 columns. The primary key is a composite business key rather than a surrogate: WF_ITEM_ACTIVITY_STATUSES_PK is defined on (ITEM_TYPE, ITEM_KEY, PROCESS_ACTIVITY). The most significant columns are:

• ITEM_TYPE, ITEM_KEY — Identify the work item this activity row belongs to; together with PROCESS_ACTIVITY they form the primary key.
• PROCESS_ACTIVITY — The specific activity instance within the process; the third primary key component.
• ACTIVITY_STATUS — Current state of the activity (for example active, complete, error, or notified).
• ACTIVITY_RESULT_CODE — The result returned by the activity when it completed.
• ASSIGNED_USER — The user to whom the activity or its notification is currently assigned.
• NOTIFICATION_ID — Foreign key to WF_NOTIFICATIONS; links the activity to its notification row.
• BEGIN_DATE, END_DATE — Timestamps marking when the activity started and finished.
• EXECUTION_TIME — Elapsed time recorded for the activity.
• DUE_DATE — Deadline associated with the activity or notification.
• ERROR_NAME, ERROR_MESSAGE, ERROR_STACK — Diagnostic information captured when ACTIVITY_STATUS indicates an error.
• OUTBOUND_QUEUE_ID — Identifies the outbound agent queue used for deferred processing.
• ACTION, PERFORMED_BY — The action taken on the activity and the user who performed it.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing data security grouping.

Notification and diagnostic columns are typically sparsely populated; ACTIVITY_STATUS, ASSIGNED_USER, and the timing columns are dense and most frequently queried.

Common Use Cases and Queries

Typical operational scenarios include troubleshooting stalled or errored workflows, auditing notification assignments, and reporting on cycle times between workflow steps. A common pattern retrieves currently active or errored activities for a given item type:

SELECT item_key, process_activity, activity_status, assigned_user, begin_date FROM wf_item_activity_statuses WHERE item_type = :p_item_type AND activity_status IN ('ACTIVE','ERROR');

Joining to WF_NOTIFICATIONS via NOTIFICATION_ID returns the notification subject and status; joining to WF_ITEMS via ITEM_TYPE and ITEM_KEY yields the parent work item context. Reporting uses include aging of pending approvals (DUE_DATE versus SYSDATE), throughput analysis using BEGIN_DATE, END_DATE, and EXECUTION_TIME, and error trending grouped by ERROR_NAME. Because the table can be large, queries should filter by ITEM_TYPE and use indexes on the primary key columns.

Related Objects

• WF_ITEMS — Parent work item; joined on ITEM_TYPE and ITEM_KEY.
• WF_PROCESS_ACTIVITIES — Activity definition; joined on PROCESS_ACTIVITY.
• WF_NOTIFICATIONS — Notification detail; joined on NOTIFICATION_ID.
• FND_SECURITY_GROUPS — Security grouping; joined on SECURITY_GROUP_ID.
• WF_ITEM_ACTIVITY_STATUSES_PK — The unique index enforcing the (ITEM_TYPE, ITEM_KEY, PROCESS_ACTIVITY) business key.
• Workflow Monitor / Workflow APIs — The primary application and PL/SQL interfaces that read and update this table at runtime.