Search Results eng_change_type_processes_u1

Overview

ENG.ENG_CHANGE_TYPE_PROCESSES is an Engineering (ENG) schema table in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that stores the engineering change type processes used to associate change order types with the Oracle Workflow root processes that drive them. In the Oracle EBS Engineering Change Order (ECO) model, an ECO is classified by a change order type and a priority code, and this table provides the mapping that binds that classification, within a specific inventory organization, to the workflow process definition that governs the ECO lifecycle. It is a seed data table, installed in the APPS_TS_SEED tablespace, and its contents are typically maintained during setup rather than through day-to-day transactional activity.

The ETRM metadata classifies this object heuristically as standalone in Data Vault terms, meaning it presents as an independent reference or configuration entity without a documented foreign-key dependency to another hub or link. In a Data Vault modeling exercise it is best treated as a hub or reference table candidate keyed on the change type, priority, and organization combination, with the workflow process name and descriptive flexfield columns carried as satellite-style attributes.

Key Information Stored

The table contains 29 documented columns. The business-key candidate identified by the unique index ENG_CHANGE_TYPE_PROCESSES_U1 is the composite of CHANGE_ORDER_TYPE_ID, ENG_CHANGE_PRIORITY_CODE, and ORGANIZATION_ID; the same three columns form the primary key constraint ENG_CHANGE_TYPE_PROCESSES_PK. There is no separate single-column surrogate key, so the composite business key functions as the row identifier.

• CHANGE_ORDER_TYPE_ID (NUMBER) — identifier of the engineering change order type; first component of the unique business key.
• ENG_CHANGE_PRIORITY_CODE (VARCHAR2, 10) — the ECO priority code; second component of the unique business key.
• ORGANIZATION_ID (NUMBER) — the inventory organization in which the mapping applies; third component of the unique business key.
• PROCESS_NAME (VARCHAR2, 30) — the root process for the 'ECO_APP' item type, i.e. the Oracle Workflow definition invoked for the ECO.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Who columns that record audit and user context.
• ATTRIBUTE_CATEGORY (VARCHAR2, 30) — descriptive flexfield structure defining column.
• ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2, 150 each) — descriptive flexfield segments available for customer-specific extensions.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent Who columns capturing the concurrent program that last modified the row.

Common Use Cases and Queries

Typical usage is diagnostic and setup-oriented. Engineering administrators verify which workflow process is attached to a given change order type and priority within an organization, and support analysts trace unexpected ECO routing back to a missing or incorrect PROCESS_NAME. Because the table is organization-scoped, cross-organization comparison of configured processes is a frequent reporting requirement.

A basic lookup joins the business-key columns:

• SELECT change_order_type_id, eng_change_priority_code, organization_id, process_name FROM eng.eng_change_type_processes WHERE organization_id = :org_id;
• SELECT * FROM eng.eng_change_type_processes WHERE change_order_type_id = :type_id AND eng_change_priority_code = :priority AND organization_id = :org_id; — retrieves a specific mapping using the full unique key, exercising ENG_CHANGE_TYPE_PROCESSES_U1.
• Duplicate detection and coverage analysis: aggregate over process_name to find change type and priority combinations lacking configuration within an organization.

Customers who have populated the descriptive flexfield can query ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for local extensions, while concurrent Who columns support impact analysis after a concurrent program run.

Related Objects

The ETRM relationship data records no formal foreign keys for this table, so related objects are identified by shared business columns rather than enforced constraints. The most significant associations are:

• ENG_ECO_DEFINITION_HEADERS / change order type definitions — joined on CHANGE_ORDER_TYPE_ID to resolve the change type name shown to users.
• Engineering change priority / lookup tables — joined on ENG_CHANGE_PRIORITY_CODE to resolve priority descriptions.
• HR_OPERATING_UNITS / ORG_ORGANIZATION_DEFINITIONS — joined on ORGANIZATION_ID to validate the inventory organization context.
• WF_ITEM_TYPES / WF_PROCESS_ACTIVITIES — joined on PROCESS_NAME to confirm that the configured root process exists and is valid for the ECO_APP item type.
• FND_CONCURRENT_PROGRAMS and FND_APPLICATION — joined on PROGRAM_ID and PROGRAM_APPLICATION_ID to identify the concurrent program recorded in the concurrent Who columns.
• FND_FLEX_VALUES_VL — used with ATTRIBUTE_CATEGORY and the ATTRIBUTE segments when descriptive flexfield values are validated.

Because the object is classified as standalone, no dependent child tables were documented in the ETRM metadata; integrations should treat it as a configuration reference source rather than a transactional hub.