Search Results wfa_act

Overview

The view APPS.ENG_WF_PROCESS_V is a reporting object within the Oracle E-Business Suite Engineering (ENG) module. Its documented purpose is to list all root processes associated with the ECO_APP workflow item type. In Oracle EBS, ECO_APP is the workflow item type that governs Engineering Change Order (ECO) approval routing. The view therefore serves as a focused dictionary of the top-level workflow processes defined for the ECO approval cycle.

The view is defined with status VALID in the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2. It does not store data of its own; rather, it is a read-only projection over Oracle Workflow dictionary tables. This makes it suitable for reporting on process configuration, for diagnostic queries during workflow customization, and for integration scripts that must discover which root ECO processes exist before initiating or interrogating them. The name itself reflects its role: an Engineering workflow process view specific to the ECO approval item type. Because it exposes only process names and display names, it is intentionally narrow in scope — a configuration lookup rather than a transactional reporting source.

Underlying Base Objects

According to the documented view text, ENG_WF_PROCESS_V is constructed from two workflow dictionary objects joined through the process-activity mapping table:

• WF_ACTIVITIES_VL — referenced twice, aliased as WFA_PROC (the root process) and WFA_ACT (the activities belonging to that process). This is the Workflow activities view that provides the NAME, DISPLAY_NAME, ITEM_TYPE, and END_DATE attributes.
• WF_PROCESS_ACTIVITIES (referenced in the environment as a synonym) — the mapping table that links a process to its activities, carrying PROCESS_ITEM_TYPE, PROCESS_NAME, PROCESS_VERSION, ACTIVITY_ITEM_TYPE, and ACTIVITY_NAME.

The join logic is fully determined by the view text: the root process is fixed by the predicates WFA_PROC.NAME = 'ROOT' and WFA_PROC.ITEM_TYPE = 'ECO_APP'. The process is then matched to its activities via item type, process name, and process version. Only activities whose END_DATE is null are returned, and the root process row itself must also have a null END_DATE. Consequently, the view returns the currently effective activities of the active ROOT process for the ECO_APP item type.

Key Columns

• PROCESS_NAME — sourced from WFA_ACT.NAME, this is the internal workflow name of the activity under the ECO_APP root process. In the context of the ECO approval flow, these names identify the individual approval or notification steps configured for the item type.
• DISPLAY_NAME — sourced from WFA_ACT.DISPLAY_NAME, this is the user-facing label of the activity. It is the value typically shown to approvers and administrators in workflow status screens and notification headers.

Both columns are character attributes inherited from the Workflow activities view. No keys, dates, or process identifiers beyond these two columns are exposed, which confines the view to name-resolution purposes.

Common Use Cases and Queries

The principal use case is to enumerate the configured names and labels of the ECO_APP root process activities, for example when validating a customization or when building a reference list for administrators. A typical query is:

• SELECT process_name, display_name FROM apps.eng_wf_process_v ORDER BY process_name;
• SELECT display_name FROM apps.eng_wf_process_v WHERE process_name = :activity_name; — to resolve an internal activity name to its display label.
• SELECT COUNT(*) FROM apps.eng_wf_process_v; — to confirm the number of active activities in the ECO_APP root process, useful during post-upgrade or post-patch validation.

Because the view filters on END_DATE IS NULL for both the process and its activities, results reflect only current, non-retired definitions. It is commonly joined to Workflow runtime tables such as WF_ITEM_ACTIVITY_STATUSES or WF_NOTIFICATIONS when generating descriptive reports that translate internal activity names into readable ECO approval step labels. In integration scenarios, the view can be queried to confirm that expected ECO approval steps exist before a workflow-enabled change is submitted, thereby avoiding runtime routing errors caused by missing or end-dated activity definitions.