Search Results item_end_date

Overview

APPS.WF_ITEM_ACTIVITY_STATUSES_V is a public Oracle Workflow runtime view shipped in the APPS schema and registered in Oracle E-Business Suite design data as FND.WF_ITEM_ACTIVITY_STATUSES_V. It exposes the current and historical status of every activity instance associated with a workflow item, combining rows from the live runtime table and its history counterpart into a single, query-friendly result set. The view is explicitly documented as a public view that may be useful for custom reporting or other data requirements, which means it is a supported access path for customer-developed reports, extracts, and integration programs.

In Oracle EBS 12.1.1 and 12.2.2 the Workflow engine frequently purges completed activity rows from the transactional table into the history table to control table growth and performance. Because WF_ITEM_ACTIVITY_STATUSES_V unions both sources, it presents a stable, complete picture of workflow progress regardless of whether a given row has been archived. This makes it the preferred reporting entry point over querying WF_ITEM_ACTIVITY_STATUSES or WF_ITEM_ACTIVITY_STATUSES_H directly.

Underlying Base Objects

The documented base objects behind the view are:

• WF_ITEM_ACTIVITY_STATUSES (synonym) and WF_ITEM_ACTIVITY_STATUSES_H (synonym) — the current and history activity status tables that supply the core runtime rows, distinguished by the SOURCE column.
• WF_ITEMS (synonym) — the parent workflow item definition providing ITEM_TYPE and ITEM_KEY context.
• WF_ITEM_TYPES_VL (view) — supplies item type display name and description.
• WF_ACTIVITIES_VL (view) — supplies activity display name, description, and type.
• WF_PROCESS_ACTIVITIES (synonym) — links processes to their child activities.
• WF_LOOKUPS (view) — resolves coded values such as activity status and result codes into display names.
• WF_CORE (package) and WF_DIRECTORY (package) — the Workflow and directory APIs used for runtime resolution of display attributes and role assignments.

Key Columns

The view returns a broad set of item and activity attributes. ITEM_TYPE, ITEM_TYPE_DISPLAY_NAME, and ITEM_TYPE_DESCRIPTION identify the workflow definition; ITEM_KEY and USER_KEY identify the specific item instance. ITEM_BEGIN_DATE records when the item started and ITEM_END_DATE records the date the item finished; this column is the one most often searched when users look for "item_end_date" and is commonly used to measure cycle time or to filter completed workflows. ACTIVITY_ID, ACTIVITY_LABEL, ACTIVITY_NAME, and ACTIVITY_DISPLAY_NAME identify the activity, while ACTIVITY_BEGIN_DATE and ACTIVITY_END_DATE bound its execution. ACTIVITY_STATUS_CODE and ACTIVITY_STATUS_DISPLAY_NAME report current status; ACTIVITY_RESULT_CODE and ACTIVITY_RESULT_DISPLAY_NAME report the outcome. ASSIGNED_USER and ASSIGNED_USER_DISPLAY_NAME show the runtime performer, NOTIFICATION_ID and OUTBOUND_QUEUE_ID support notification and event-queue tracing, and SOURCE indicates whether the row came from the regular table ('R') or the history table ('H').

Common Use Cases and Queries

Typical uses include open-items reporting, approval-cycle-time analysis, stalled-activity monitoring, and audit extracts feeding downstream integration tables.

SELECT item_type
     , item_key
     , activity_display_name
     , activity_status_display_name
     , item_end_date
  FROM apps.wf_item_activity_statuses_v
 WHERE item_type      = :p_item_type
   AND item_end_date IS NULL
 ORDER BY activity_begin_date;

To measure elapsed time for completed workflows:

SELECT item_key
     , item_begin_date
     , item_end_date
     , ROUND(item_end_date - item_begin_date, 2) days_elapsed
  FROM apps.wf_item_activity_statuses_v
 WHERE item_type     = :p_item_type
   AND item_end_date BETWEEN :p_from_date AND :p_to_date;

Because the view centralizes current and historical rows, it is suitable for both real-time status dashboards and retrospective audit reporting within the same query.