Search Results eng_change_propagation_maps




Overview
Explore in AI Chat

Overview

ENG_CHANGE_PROPAGATION_MAPS is an Engineering (ENG) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the change propagation mapping between source and destination entities. When an engineering change order (ECO) is released, affected items, bills of material, and routing structures must be propagated to downstream organizations and manufacturing entities. This table captures the linkage between the original revised item context and the resulting target records, allowing the application to track which destination records were generated by, or associated with, a given change propagation event.

The table resides in the ENG schema and is documented as VALID in the ETRM 12.2.2 physical schema with 28 columns. From a heuristic Data Vault modeling perspective, the FK structure indicates this object behaves as a standalone structure, meaning it functions primarily as a detail or mapping table rather than a classic multi-parent link. A single foreign key references ENG_REVISED_ITEMS via REVISED_ITEM_SEQUENCE_ID, anchoring each propagation mapping row to a specific revised item sequence within an engineering change.

Key Information Stored

The surrogate primary key is CHANGE_PROPAGATION_MAP_ID, enforced by the unique index ENG_CHANGE_PROPAGATION_MAPS_U1. This identifier uniquely distinguishes each propagation mapping record and serves as the principal business-key candidate documented for the table.

Common Use Cases and Queries

Typical usage centers on diagnostics and reconciliation of ECO propagation. Engineers and support analysts query the table to confirm that a released change propagated to all intended organizations, and to identify rows where ENTITY_ACTION_STATUS indicates an incomplete or failed action. A representative query joins the mapping to its parent revised item:

SELECT m.CHANGE_PROPAGATION_MAP_ID, m.CHANGE_ID, m.LOCAL_ORGANIZATION_ID, m.ENTITY_NAME, m.ENTITY_ACTION_STATUS
FROM ENG.ENG_CHANGE_PROPAGATION_MAPS m
WHERE m.REVISED_ITEM_SEQUENCE_ID = :sequence_id;

Another common pattern isolates failed or pending propagations for a specific change: filtering on CHANGE_ID and ENTITY_ACTION_STATUS. Reporting use cases include auditing which destination organizations received a given change, tracing the LOCAL_REVISED_LINE_ID values back to their destination entities, and reconciling concurrent request output through REQUEST_ID.

Related Objects

  • ENG_REVISED_ITEMS — Parent table referenced through REVISED_ITEM_SEQUENCE_ID; the primary documented FK relationship.
  • ENG_ENGINEERING_CHANGES — Related through CHANGE_ID and LOCAL_CHANGE_ID, supplying change order context.
  • ENG_REVISED_COMPONENTS — Frequently associated with REVISED_LINE_TYPE and revised line identifiers.
  • ENG_REVISED_OPERATIONS — Related to propagated routing line actions.
  • ENG_CHANGE_ORDER_REVISED_ITEMS — Links the ECO revision context to propagation records.
  • MTL_SYSTEM_ITEMS_B — Destination item definitions referenced through local entity identifiers.
  • FND_CONCURRENT_REQUESTS — Joinable through REQUEST_ID for program and phase status reporting.
  • ENG_CHANGE_PROPAGATION_MAPS public APIs and concurrent programs in the Engineering module generate and update these rows during ECO release processing.