Search Results workflow_process_name

Overview

ENGFV_ECO_WORKFLOW_RULES is an APPS-owned read-only view in the Oracle E-Business Suite Engineering (ENG) module. Its name reflects its function: it exposes the workflow routing rules that govern Engineering Change Orders (ECOs). For a given combination of change order type, change priority, and inventory organization, the view returns the Oracle Workflow process that the ECO transaction must invoke. The "FV" naming convention indicates a documented, supported view intended for customer and integrator access rather than internal use only.

The object is marked as retrofitted, meaning it was formalized as a published database object during the ETRM documentation effort and carries a stable interface across Oracle EBS 12.1.1 and 12.2.2. It is defined WITH READ ONLY, so it is suitable purely for querying, reporting, and integration lookups; no DML is permitted against it. Because it surfaces the WORKFLOW_PROCESS_NAME column, it is the canonical reference point when a user or integration needs to resolve which workflow process handles a particular ECO configuration without navigating the Engineering responsibility forms.

Underlying Base Objects

The view is constructed as an inner join across four base objects, all referenced through APPS synonyms. ENG_CHANGE_TYPE_PROCESSES (aliased RU) is the driving table and supplies the workflow process name, change order type, organization, priority code, surrogate keys, and audit columns. ENG_CHANGE_ORDER_TYPES (aliased TY) is joined on CHANGE_ORDER_TYPE_ID to translate the numeric type identifier into the CHANGE_TYPE_CODE visible to users. MTL_PARAMETERS (aliased PA) is joined on ORGANIZATION_ID to derive the three-character ORGANIZATION_CODE, and HR_ALL_ORGANIZATION_UNITS (aliased AL) is joined on the same ORGANIZATION_ID to supply the descriptive ORGANIZATION_NAME.

Because every join is an equi-join on NOT NULL keys and the organization predicate is enforced through the secure predicate '_SEC:RU.ORGANIZATION_ID' IS NOT NULL, the view is effectively organization-security filtered and only returns rows where a matching change type, process definition, and valid inventory organization all exist.

Key Columns

• CHANGE_TYPE_CODE — user-facing code of the ECO change order type, sourced from ENG_CHANGE_ORDER_TYPES.
• PRIORITY_CODE — the change priority (ENG_CHANGE_PRIORITY_CODE) for which the workflow rule applies.
• ORGANIZATION_CODE — inventory organization short code from MTL_PARAMETERS, useful for filtering by plant or warehouse.
• ORGANIZATION_NAME — descriptive organization name from HR_ALL_ORGANIZATION_UNITS.
• WORKFLOW_PROCESS_NAME — the Oracle Workflow process invoked for the ECO; this is the column users most often search for.
• CHANGE_ORDER_TYPE_ID, ORGANIZATION_ID — surrogate keys supporting joins back to ENGINEERING base tables.
• UPDATED_ON, UPDATED_BY, CREATED_ON, CREATED_BY — audit columns tracking who defined the rule and when.

Common Use Cases and Queries

Typical scenarios include auditing which workflow processes are configured per organization, troubleshooting an ECO that fails to launch the expected approval workflow, and driving integration logic that must invoke the correct process externally. A representative query listing all rules for a given organization is:

• SELECT CHANGE_TYPE_CODE, PRIORITY_CODE, ORGANIZATION_CODE, WORKFLOW_PROCESS_NAME FROM APPS.ENGFV_ECO_WORKFLOW_RULES WHERE ORGANIZATION_CODE = 'M1' ORDER BY CHANGE_TYPE_CODE, PRIORITY_CODE;
• SELECT DISTINCT WORKFLOW_PROCESS_NAME FROM APPS.ENGFV_ECO_WORKFLOW_RULES; — enumerates all processes referenced by ECO rules.
• SELECT CHANGE_TYPE_CODE, PRIORITY_CODE, WORKFLOW_PROCESS_NAME FROM APPS.ENGFV_ECO_WORKFLOW_RULES WHERE WORKFLOW_PROCESS_NAME LIKE 'ECO%APPROVAL%'; — locates rules bound to a specific approval process.

Because of the read-only definition, these queries are safe for reporting schemas and can be embedded in concurrent programs, BI Publisher data models, or OIC integrations that need to resolve ECO workflow routing.