Search Results eng_change_type_processes_pk

Overview

ENG_CHANGE_TYPE_PROCESSES is a reference and configuration table in the Oracle Engineering (ENG) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the mapping between an engineering change order type, a change priority code, and an organization, and the workflow or business process that governs the change lifecycle for that combination. In practice, the table determines which Oracle Workflow process is invoked when an engineering change order (ECO) of a given type and priority is created or progressed within a specific inventory organization. This makes it a control table rather than a transactional one: its rows are defined during implementation setup and are read at runtime by the change order entry and workflow background engine.

ETRM classifies the object as a standalone table based on its foreign-key topology, and offers a heuristic Data Vault modeling suggestion of an independent hub-like or reference construct rather than a link between two large transactional hubs. The classification is heuristic and should be treated as guidance, not as a prescribed model. Its composite primary key is natural rather than surrogate, which is consistent with a configuration table whose identity is expressed entirely by business attributes.

Key Information Stored

The table contains 29 documented columns. Its primary key, ENG_CHANGE_TYPE_PROCESSES_PK, is composed of three columns — CHANGE_ORDER_TYPE_ID, ENG_CHANGE_PRIORITY_CODE, and ORGANIZATION_ID — and the unique index ENG_CHANGE_TYPE_PROCESSES_U1 enforces the same three-column combination. There is no separately generated surrogate key column; the business key is the primary key. The key columns and their significance are as follows.

• CHANGE_ORDER_TYPE_ID — identifier of the engineering change order type (for example, a standard ECO versus a deviation or a manufacturing change).
• ENG_CHANGE_PRIORITY_CODE — the priority code assigned to the change, used to differentiate handling and urgency.
• ORGANIZATION_ID — the inventory organization in which this type/priority combination is valid, allowing organization-specific process rules.
• PROCESS_NAME — the name of the Oracle Workflow process associated with the type and priority combination; this is the functional payload of the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle Applications who-columns used for auditability.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns, available for customers to capture additional configuration attributes.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns recording the request that last modified the row.

Common Use Cases and Queries

The predominant reporting requirement is to resolve the workflow process governing a change order. A typical join resolves the process for a given organization and priority:

• Determine which workflow process supports a type/priority: SELECT process_name FROM eng.eng_change_type_processes WHERE change_order_type_id = :p_type AND eng_change_priority_code = :p_priority AND organization_id = :p_org;
• Validate configuration completeness — identify type/priority combinations missing a process assignment, so that change order creation does not fail at workflow launch.
• List all priority codes enabled for an organization, filtering on the ENG_CHANGE_PRIORITY_CODE column, which is the exact column users search for when tracing priority-driven behavior.
• Audit recently changed configuration rows via LAST_UPDATE_DATE and LAST_UPDATED_BY, useful during post-implementation verification or release upgrades.

Related Objects

The table is consumed primarily through joins to change order type and organization reference data, and through the Engineering setup layer. The principal related objects and join columns are:

• ENG_ENGINEERING_CHANGE_TYPES — change order type definitions, joined on CHANGE_ORDER_TYPE_ID.
• ENG_CHANGE_ORDER_TYPES_VL / ENG_CHANGE_ORDER_TYPES_B / ENG_CHANGE_ORDER_TYPES_TL — the base, view, and translation objects describing change order types.
• ORG_ORGANIZATION_DEFINITIONS — joined on ORGANIZATION_ID to resolve the organization name for the configuration row.
• ENG_ENGINEERING_CHANGES — the change order header table, linked by change order type and organization to determine the applicable process at runtime.
• WF_PROCESS_ACTIVITIES and WF_ITEM_TYPES — Oracle Workflow definition tables, joined on PROCESS_NAME, used to validate that the assigned process exists and is active.
• FND_FLEX_VALUES / FND_FLEX_VALUES_VL — the source of validated values for the change priority and type, where these are represented as flexfield-based lookups.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID for concurrent-program audit trails on configuration changes.