Search Results assigned_user_display_name

Overview

APPS.WF_ITEM_ACTIVITY_STATUSES_V is the public, supported view for accessing Oracle Workflow runtime status information in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the APPS schema and belongs to the FND — Application Object Library product. Rather than querying the underlying runtime tables directly, developers, DBAs, and reporting tools use this view to retrieve the current and historical status of workflow activities associated with running and completed workflow items.

The view consolidates workflow item data, process activity data, activity definitions, and lookup-derived code meanings into a single denormalized result set. It performs this by joining WF_ITEM_ACTIVITY_STATUSES (current activity runtime rows) with WF_ITEMS, WF_ITEM_TYPES_VL, WF_PROCESS_ACTIVITIES, WF_ACTIVITIES_VL, and two WF_LOOKUPS instances that decode activity type and activity status. Its role in EBS reporting and integration is that of the canonical read interface for workflow status: it shields consumers from the internal structure of the workflow engine and from version-specific table changes.

Underlying Base Objects

The documented base objects referenced by the view are WF_ACTIVITIES_VL (view), WF_CORE (package), WF_DIRECTORY (package), WF_ITEMS (synonym), WF_ITEM_ACTIVITY_STATUSES (synonym), WF_ITEM_ACTIVITY_STATUSES_H (synonym), WF_ITEM_TYPES_VL (view), WF_LOOKUPS (view), and WF_PROCESS_ACTIVITIES (synonym).

Although the external synonym list identifies WF_ITEM_ACTIVITY_STATUSES and WF_ITEM_ACTIVITY_STATUSES_H separately, the view definition is a UNION ALL of two branches that share an identical column projection. The first branch returns rows flagged 'R' from the runtime activity status table, and the second returns rows flagged 'H' from the history table, thereby exposing both live and archived workflow activity states through one interface. WF_CORE.ACTIVITY_RESULT resolves the activity result type and code into a meaningful result, while WF_DIRECTORY.GETROLEDISPLAYNAME translates the assigned user or role into a directory display name.

Key Columns

• ITEM_TYPE, ITEM_KEY, USER_KEY — identify the workflow item and its business-facing key.
• ITEM_TYPE display name and description from WF_ITEM_TYPES_VL, plus BEGIN_DATE and END_DATE of the item.
• PROCESS_ACTIVITY and INSTANCE_LABEL — the running process activity and its label.
• NAME, DISPLAY_NAME, DESCRIPTION, TYPE — activity definition attributes from WF_ACTIVITIES_VL.
• ACTIVITY_STATUS and its decoded MEANING from the WFENG_STATUS lookup.
• ACTIVITY_RESULT_CODE and the derived activity result.
• ASSIGNED_USER — the user or role to which the activity is assigned, with a companion directory display name. This column is the target of the "assigned_user" search and is central to notification and worklist analysis.
• NOTIFICATION_ID, OUTBOUND_QUEUE_ID — notification and queue linkage.
• ERROR_NAME, ERROR_MESSAGE, ERROR_STACK — error detail for failed or errored activities.
• EXECUTION_TIME, BEGIN_DATE, END_DATE — timing of the activity execution.

Common Use Cases and Queries

The view supports worklist reporting, notification auditing, and troubleshooting of stalled or errored workflow processes. A typical query for open activities assigned to a specific user is:

SELECT item_type, item_key, process_activity,
       display_name, activity_status, assigned_user
FROM   apps.wf_item_activity_statuses_v
WHERE  assigned_user = :p_user
AND    activity_status NOT IN ('COMPLETE','CANCEL');

To locate errored activities with diagnostic detail:

SELECT item_type, item_key, display_name,
       error_name, error_message
FROM   apps.wf_item_activity_statuses_v
WHERE  error_name IS NOT NULL;

A third common pattern aggregates activity status by item type to monitor workload:

SELECT item_type, activity_status, COUNT(*)
FROM   apps.wf_item_activity_statuses_v
GROUP  BY item_type, activity_status;

Because the view exposes the full activity lifecycle, these queries return both active and historical rows, making it suitable for both operational monitoring and audit reporting against workflow runtime data.