Search Results priority_description

Overview

ENG_CHANGE_TYPE_PROCESSES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the ENG (Engineering) product family and exposes the configuration of engineering change type processes — the intersection of an engineering change order type, an engineering change priority, and a specific process name. The view is a denormalized presentation layer: rather than forcing consumers to join the change type process table to the change priorities table manually, it pre-joins the two and surfaces the human-readable priority description alongside the priority code.

The view plays a supporting role in reporting and integration. Change order types in Engineering define which processes (workflows and process definitions) are valid for a given class of engineering change order, and the priority code governs the urgency level at which those changes are routed. Downstream integrations and concurrent programs frequently need the descriptive text rather than the coded value, which is precisely what the PRIORITY_DESCRIPTION column supplies. Because the view is defined in the APPS schema and owned by that schema, it is reachable by any session with standard APPS connectivity and appropriate grants.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed as synonyms in the APPS schema:

• ENG_CHANGE_TYPE_PROCESSES (SYNONYM) — the primary driver table. It stores one row per combination of change order type, engineering change priority code, organization, and process name.
• ENG_CHANGE_PRIORITIES (SYNONYM) — the lookup table providing the descriptive text for a priority code.

The join is an outer join: the definition uses ECP.ENG_CHANGE_PRIORITY_CODE(+) and ECP.ORGANIZATION_ID(+) = -1, meaning rows in ENG_CHANGE_TYPE_PROCESSES are retained even when no matching priority description exists. Both sides are constrained to ORGANIZATION_ID = -1, the conventional "global" or seed organization value used for shared reference configuration in Engineering. The view therefore does not expose organization-specific overrides; it reflects the seeded, globally applicable change type process definitions.

Key Columns

• ROW_ID — the ROWID of the underlying ENG_CHANGE_TYPE_PROCESSES row, useful as a surrogate identifier.
• CHANGE_ORDER_TYPE_ID — foreign key to the engineering change order type. This is the primary grouping key.
• ENG_CHANGE_PRIORITY_CODE — the coded priority value.
• PRIORITY_DESCRIPTION — the descriptive text sourced from ENG_CHANGE_PRIORITIES. This is the column users most often search for; it is the readable counterpart to the priority code.
• ORGANIZATION_ID — always -1 in this view, reflecting the global seed organization.
• PROCESS_NAME — the workflow process associated with the change type and priority combination.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard DFF/descriptive flexfield columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns.

Common Use Cases and Queries

Typical uses include validating that a change order type has a process defined for a given priority, generating setup reports, and joining to order type definitions to build complete change configuration extracts.

SELECT change_order_type_id,
       eng_change_priority_code,
       priority_description,
       process_name
FROM   apps.eng_change_type_processes_v
WHERE  priority_description IS NOT NULL
ORDER  BY change_order_type_id, eng_change_priority_code;

To list all processes available for a specific change order type:

SELECT process_name, priority_description
FROM   apps.eng_change_type_processes_v
WHERE  change_order_type_id = :p_change_order_type_id;

Because the view filters to ORGANIZATION_ID = -1 and applies an outer join to priorities, consumers should treat PRIORITY_DESCRIPTION as nullable and avoid inner-join assumptions when reconciling against the base tables.