Search Results workflow_process

Overview

The view APPS.ENGFV_WORKFLOW_PROCESSES is an Oracle E-Business Suite database object owned by the APPS schema and registered against the Engineering (ENG) product. Within the ETRM metadata it is classified as a VIEW with a status of VALID and is annotated with the descriptor "- Retrofitted," indicating that the object was introduced or regenerated to preserve compatibility with an earlier release line during an upgrade or a multi-release support effort. Its functional purpose is to expose the set of Oracle Workflow process definitions that are relevant to Engineering-related business flows, presenting each process in both its internal identifier form and a human-readable form.

The view is a thin projection layer. Rather than storing data itself, it selects from an underlying Engineering workflow process view and renames the projected columns so that consumers see the aliases PROCESS_NAME and DISPLAY_NAME (the second column carries the internal alias WORKFLOW_PROCESS). This conforming wrapper pattern is common in EBS where external interfaces, concurrent programs, and reports are written against a stable public name while the physical implementation can change beneath it.

Because it is a reporting-oriented object, ENGFV_WORKFLOW_PROCESSES carries no transaction data and is effectively read-only. It contains no DML logic and no table storage of its own.

Underlying Base Objects

The only documented referenced base object is ENG_WF_PROCESS_V, itself a VIEW. The dependency chain is therefore view-on-view: APPS.ENG_WF_PROCESSES or ENG_WF_PROCESS_V sits beneath ENGFV_WORKFLOW_PROCESSES, and the base view resolves down to the Oracle Workflow definition tables (WF_PROCESS_ACTIVITIES, WF_ITEM_TYPES, and related metadata) that hold process, activity, and item type definitions. The ETRM excerpt does not enumerate further base tables, so the deeper physical lineage is inherited from the Workflow schema rather than declared on this object.

Because the parent is a view, ENGFV_WORKFLOW_PROCESSES cannot be updated through the view stack and is not a candidate for index creation. Any tuning must be applied at the Workflow layer or by materializing the results in a custom table.

Key Columns

• PROCESS_NAME — the internal Workflow process identifier. In Oracle Workflow this corresponds to the internal name of the process definition (the value held in the process name column of the workflow definition tables) and is the key used when launching or querying a process programmatically.
• DISPLAY_NAME — the user-facing label for the process. In the view text this column is aliased as WORKFLOW_PROCESS. It is the value suitable for presentation in reports, LOVs, and portal listings, where the internal name would be opaque to end users.

No other columns are documented for this object in the ETRM metadata.

Common Use Cases and Queries

Typical scenarios for this view include validating that an expected Engineering workflow process is present after a patch or upgrade, populating a value set or LOV with available processes, and driving integration code that must resolve a display label to an internal process name.

A basic listing of all available processes:

• SELECT process_name, display_name FROM apps.engfv_workflow_processes ORDER BY display_name;

Resolving a display label to its internal name for a process launch:

• SELECT process_name FROM apps.engfv_workflow_processes WHERE display_name = :p_display_name;

Verifying existence of a specific process after an upgrade:

• SELECT COUNT(*) FROM apps.engfv_workflow_processes WHERE process_name = :p_process_name;

Because the object is a simple view, queries should be executed under an APPS-authenticated session or a login with the appropriate synonym and grants. In 12.1.1 and 12.2.2 the view behaves identically; the "Retrofitted" annotation confirms it is maintained across both release lines for backward compatibility.