Results for “promote_status_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ENG_ENGINEERING_CHANGES is the master table in the Oracle E-Business Suite Engineering (ENG) module that stores engineering change orders (ECOs), also referred to as engineering change notices (ECNs). Each row represents a controlled change to a manufactured item, bill of materials, routing, or related engineering artifact, and acts as the transactional anchor that governs how design modifications are approved, scheduled, and implemented across the enterprise. The table resides in the ENG schema and is present in both 12.1.1 and 12.2.2, with 73 documented columns in the ETRM 12.2.2 physical schema.

From a dimensional modeling perspective, the mined Data Vault classification for this table is hub. This is a heuristic suggestion: the primary key (CHANGE_NOTICE, ORGANIZATION_ID) and the two unique indexes make ENG_ENGINEERING_CHANGES a natural business-key hub, while its descriptive attributes (dates, status, costs, approvals) would typically be split into one or more satellites in a Data Vault design.

Key Information Stored

The composite primary key is ENG_ENGINEERING_CHANGES_PK, defined on (CHANGE_NOTICE, ORGANIZATION_ID). Two additional unique indexes serve as business-key candidates: ENG_ENGINEERING_CHANGES_U1 (ORGANIZATION_ID, CHANGE_NOTICE) and ENG_ENGINEERING_CHANGES_U2 (CHANGE_MGMT_TYPE_CODE, ORGANIZATION_ID, CHANGE_NOTICE). The most significant columns include:

• CHANGE_NOTICE and ORGANIZATION_ID — the composite business key identifying each ECO within an inventory organization.
• CHANGE_NAME, CHANGE_NOTICE_PREFIX, CHANGE_NOTICE_NUMBER — user-facing identifiers and naming metadata.
• STATUS_TYPE, STATUS_CODE, APPROVAL_STATUS_TYPE, PROMOTE_STATUS_CODE — lifecycle and approval state indicators.
• INITIATION_DATE, APPROVAL_DATE, NEED_BY_DATE, IMPLEMENTATION_DATE, COMPLETION_DATE, CANCELLATION_DATE, EXPIRATION_DATE — the principal milestone dates driving scheduling and reporting.
• PRIORITY_CODE, REASON_CODE, CHANGE_ORDER_TYPE_ID, APPROVAL_LIST_ID — classification and workflow foreign keys.
• ESTIMATED_ENG_COST, ESTIMATED_MFG_COST, EFFORT — cost and effort estimates used by change-impact reporting.
• REQUESTOR_ID, ASSIGNEE_ID, RESPONSIBLE_ORGANIZATION_ID — ownership and accountability references.

Common Use Cases and Queries

Typical usage centers on ECO status tracking, approval-cycle reporting, and impact analysis against affected items and BOMs. A common query lists open ECOs by organization and status:

• SELECT CHANGE_NOTICE, CHANGE_NAME, STATUS_TYPE, PRIORITY_CODE, NEED_BY_DATE FROM ENG.ENG_ENGINEERING_CHANGES WHERE ORGANIZATION_ID = :org_id AND STATUS_TYPE IN ('OPEN','PENDING') ORDER BY NEED_BY_DATE;
• Join to ENG_REVISED_ITEMS on (CHANGE_NOTICE, ORGANIZATION_ID) to enumerate items affected by a given ECO.
• Join to MTL_SYSTEM_ITEMS_B via ENGINEERING_ECN_CODE to find items whose current revision is governed by an ECO.
• Join to BOM_BILL_OF_MATERIALS or BOM_STRUCTURES_B on PENDING_FROM_ECN to identify structures awaiting implementation.
• Aggregate ESTIMATED_ENG_COST and ESTIMATED_MFG_COST by STATUS_TYPE for cost-of-change dashboards.

Related Objects

ENG_ENGINEERING_CHANGES is referenced by numerous downstream tables, and it in turn references several lookup and setup tables.

• ENG_REVISED_ITEMS — joins on (CHANGE_NOTICE, ORGANIZATION_ID); lists items impacted by each ECO.
• ENG_CHANGE_ORDER_REVISIONS — joins on (CHANGE_NOTICE, ORGANIZATION_ID); tracks ECO revisions.
• BOM_BILL_OF_MATERIALS and BOM_STRUCTURES_B — join via PENDING_FROM_ECN plus ORGANIZATION_ID.
• MTL_ITEM_REVISIONS_B and MTL_RTG_ITEM_REVISIONS — join on (CHANGE_NOTICE, ORGANIZATION_ID) for item and routing revision history.
• MTL_SYSTEM_ITEMS_B — references via ENGINEERING_ECN_CODE and ORGANIZATION_ID.
• MRP_PENDING_ENG_CHANGES — joins on (CHANGE_NOTICE, ORGANIZATION_ID) to feed planning.
• ENG_CHANGE_PRIORITIES, ENG_CHANGE_REASONS, ENG_CHANGE_ORDER_TYPES, ENG_ECN_APPROVAL_LISTS — referenced lookup tables via PRIORITY_CODE, REASON_CODE, CHANGE_ORDER_TYPE_ID, and APPROVAL_LIST_ID.
• MTL_PARAMETERS — parent organization reference via ORGANIZATION_ID.