Results for “eng_revised_components”

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

Overview

The ENG_REVISED_COMPONENTS table, owned by the ENG schema within the Oracle E-Business Suite Engineering (ENG) module, stores the implemented and cancelled revised components that arise from engineering change management activities. It functions as the historical and staging record for component-level revisions applied to bills of material (BOMs), capturing both the pending engineering change order (ECO) state and the finalized implementation outcome for each affected component line.

From a Data Vault modeling perspective, the metadata heuristic classifies this table as satellite-leaning. Its structure, anchored by a surrogate primary key and referencing a parent item-revision object, is consistent with a satellite entity that records descriptive and contextual attributes for a driving business key. This classification is offered as a modeling suggestion rather than a prescriptive directive.

Key Information Stored

The table contains 83 documented columns in the 12.2.2 physical schema. The surrogate primary key, ENG_REVISED_COMPONENTS_PK, is defined on COMPONENT_SEQUENCE_ID. A unique index, ENG_REVISED_COMPONENTS_U1, also covers COMPONENT_SEQUENCE_ID, making it the business-key candidate for the row.

• COMPONENT_SEQUENCE_ID — Surrogate primary key uniquely identifying each revised component row.
• REVISED_ITEM_SEQUENCE_ID — Foreign key to ENG_REVISED_ITEMS, tying the component revision to its parent revised item.
• COMPONENT_ITEM_ID / ITEM_NUM — The component item being added, changed, or removed.
• BILL_SEQUENCE_ID — Reference to the bill of material line affected by the revision.
• OLD_COMPONENT_SEQUENCE_ID — Links the new revision back to the previously implemented component line.
• CHANGE_NOTICE / ECO_FOR_PRODUCTION — The engineering change order context driving the revision.
• IMPLEMENTATION_DATE / CANCELLATION_DATE / CANCEL_COMMENTS — Lifecycle timestamps distinguishing implemented from cancelled components.
• COMPONENT_QUANTITY / COMPONENT_YIELD_FACTOR / PLANNING_FACTOR — Quantity and planning attributes for the component line.
• EFFECTIVITY_DATE / DISABLE_DATE — Date effectivity window governing when the component is active.
• FROM_OBJECT_REVISION_ID / TO_OBJECT_REVISION_ID — The from/to revision transition for the parent object.
• OPERATION_SEQUENCE_NUM — Routing operation the component is associated with.
• REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID — Concurrent program audit columns.

Common Use Cases and Queries

Engineering and manufacturing teams query this table to audit which components were implemented or cancelled under a given ECO, to report pending versus applied revisions, and to reconstruct prior BOM states. A typical query joins the parent revised item to enumerate changes within an ECO:

SELECT erc.COMPONENT_SEQUENCE_ID, erc.ITEM_NUM,
       erc.COMPONENT_QUANTITY, erc.CHANGE_NOTICE,
       erc.IMPLEMENTATION_DATE, erc.CANCELLATION_DATE
FROM   ENG.ENG_REVISED_COMPONENTS erc,
       ENG.ENG_REVISED_ITEMS      eri
WHERE  erc.REVISED_ITEM_SEQUENCE_ID = eri.REVISED_ITEM_SEQUENCE_ID
AND    erc.CHANGE_NOTICE = :p_eco
ORDER  BY erc.COMPONENT_SEQUENCE_ID;

Reporting scenarios include reconciling implemented components against the live BOM, identifying cancelled components by CANCELLATION_DATE, and tracing effectivity windows using EFFECTIVITY_DATE and DISABLE_DATE. Concurrent program audits rely on REQUEST_ID and PROGRAM_ID.

Related Objects

• ENG_REVISED_ITEMS — Parent table joined via REVISED_ITEM_SEQUENCE_ID; supplies the revised item header.
• ENG_REVISED_COMPONENT_REFS — Reference designators attached to revised components.
• BOM_BILL_OF_MATERIALS / BOM_COMPONENTS — Target structures updated upon implementation.
• ENG_ECN_ASSIGNMENTS / ENG_CHANGE_ORDERS — ECO context for CHANGE_NOTICE.
• MTL_SYSTEM_ITEMS_B — Item master joined via COMPONENT_ITEM_ID for descriptions.
• BOM_STRUCTURES_B / BOM_COMPONENTS_B — Final BOM tables receiving implemented revisions.