Search Results wfa_proc




Overview

APPS.ENG_WF_PROCESS_V is a reporting view in the Oracle E-Business Suite Applications (APPS) schema that exposes the activity-level structure of the Oracle Workflow process associated with Oracle Engineering (ECO) change management. The view returns a simple two-column result set: the internal workflow activity name and its user-facing display name. Its role is to provide a stable, pre-joined projection over the underlying Workflow repository tables so that Oracle Engineering forms, concurrent programs, and custom reports can enumerate the activities that make up the root Engineering Change Order process without writing the multi-table join themselves.

The view is effectively a filtered lens over the Workflow process definition identified by the item type ECO_APP and the process name ROOT. Because it restricts its results to the current, non-obsolete definitions (through END_DATE IS NULL predicates on both the process activity records and the activity definitions), it reflects the active state of the workflow as configured in the instance. This makes it suitable for reporting and light integration rather than for transactional processing.

Underlying Base Objects

Per the documented view metadata, ENG_WF_PROCESS_V is defined over two referenced base objects:

The join path is: WF_ACTIVITIES_VL (WFA_PROC, the ROOT process) → WF_PROCESS_ACTIVITIES (matching item type, process name, and version) → WF_ACTIVITIES_VL (WFA_ACT, the child activity). The double self-join on the activities view is the mechanism that isolates activities belonging specifically to the ECO_APP / ROOT process.

Key Columns

  • PROCESS_NAME — aliased from WFA_ACT.NAME. Despite the column label, this is the internal name of the child workflow activity returned for the Engineering Change Order process, not the process itself.
  • DISPLAY_NAME — aliased from WFA_ACT.DISPLAY_NAME. This is the translatable, user-visible label for the activity, drawn from the _VL (translated) view so that it honors the session language.

Because the view projects only these two columns, it is narrow by design. Selection is entirely constrained by the fixed literals 'ROOT' and 'ECO_APP', so callers cannot retrieve activities for other workflows through this view.

Common Use Cases and Queries

The view is typically used to drive activities pickers, to validate that a named activity exists in the Engineering Change Order workflow, or to render friendly activity labels in custom reports and concurrent output. A representative query is:

  • SELECT process_name, display_name FROM apps.eng_wf_process_v ORDER BY display_name; — returns the full list of active activities for the ECO_APP ROOT process, sorted for presentation.
  • SELECT display_name FROM apps.eng_wf_process_v WHERE process_name = 'ENG_CHANGE_ORDER'; — resolves the display label for a specific activity by its internal name.
  • SELECT COUNT(*) FROM apps.eng_wf_process_v; — a quick health check confirming that workflow definitions have been loaded and are not end-dated.

Because the object is a view, it is read-only; it should not be used as a target for DML. Queries should be aware that the results depend on the active ECO_APP workflow version and on the language setting governing WF_ACTIVITIES_VL.