Search Results ecg_action

Overview

APPS.ENG_WEB_REVISED_COMPS_V is an Oracle E-Business Suite engineering change management view that exposes revised bill of material (BOM) component details for the Engineering Web (ENG WEB) user interface and related reporting. It is owned by the APPS schema and supplies a flattened, presentation-ready record set of revised components associated with an engineering change order (ECO). The view distinguishes between the legacy component position (the pre-change BOM_INVENTORY_COMPONENTS row identified through OLD_COMPONENT_SEQUENCE_ID) and the current revised component position captured in ENG_REVISED_COMPONENTS.

In the context of Oracle EBS 12.1.1 and 12.2.2, the view serves as a reporting and integration layer over the engineering revisions data model. It resolves item identifiers to their concatenated key flexfield segments, translates action codes into user-facing meaning text, and derives organization codes and effectivity information, so that the caller does not have to navigate the underlying join across revision headers, revised components, base BOM components, item master flexfields, lookups, and parameters. As a database view (not a table), it introduces no storage of its own and reflects the real-time state of the underlying objects.

Underlying Base Objects

• ENG_REVISED_COMPONENTS (synonym) — supplies the revised component rows, including action type, quantity, effectivity date, component sequence, and the reference to the old component sequence.
• ENG_REVISED_ITEMS (synonym) — supplies the revision header context, including revised item identifier, organization, and change notice.
• BOM_INVENTORY_COMPONENTS (view) — provides the legacy component rows joined via the old component sequence identifier, including the prior operation sequence number.
• MTL_SYSTEM_ITEMS_KFV (synonym) — the key flexfield view over items, supplying concatenated and padded concatenated segments, description, engineering item flag, and primary unit of measure for both the component and the revised parent item.
• MFG_LOOKUPS (view) — resolves the action code (ACD_TYPE) against the ECG_ACTION lookup type to produce the meaningful ACTION description.
• MTL_PARAMETERS (synonym) — supplies the organization code for the revision organization.

The documented definition is a UNION of two SELECT branches. The first branch joins through BOM_INVENTORY_COMPONENTS (aliased A2) using A.OLD_COMPONENT_SEQUENCE_ID to recover legacy operation sequence data. The second branch filters the revised BOM rows with IMPLEMENTATION_DATE IS NULL, isolating components that have not yet been implemented, and aligns them to the revised item context.

Key Columns

• REVISED_ITEM_SEQUENCE_ID — foreign reference to the engineering revised item header; the primary grouping key.
• ITEM_NUM — the revised component item number carried on the revised component row.
• PADDED_CONCATENATED_SEGMENTS / CONCATENATED_SEGMENTS — flexfield-based item identifiers; the padded form supports fixed-width display.
• REVISED_ITEM — concatenated segments of the parent revised item (MSI2).
• COMPONENT_ITEM — concatenated segments of the component item (MSI).
• ACTION — decoded meaning of ACD_TYPE via the ECG_ACTION lookup.
• OLD_OP_SEQ_NUM / OPERATION_SEQUENCE_NUM — the prior and current operation sequence numbers, supporting operation reassignment analysis.
• EFFECTIVITY_DATE / EFFECTIVITY_TIME — the date and a derived hh24:mi:ss time component of the component effectivity.
• COMPONENT_QUANTITY — the quantity of the revised component.
• CHANGE_NOTICE — the ECO identifier associated with the revision.
• ORGANIZATION_CODE / ORGANIZATION_ID — the inventory organization context of the revision.
• COMPONENT_ITEM_ID, COMPONENT_SEQUENCE_ID, ENG_ITEM_FLAG, PRIMARY_UOM_CODE, DESCRIPTION — component identifiers, the engineering item flag, unit of measure, and item description.

Common Use Cases and Queries

The view is typically used to report pending and historical component changes on an ECO, to audit operation sequence reassignment, and to feed external integration or extract routines without reimplementing the multi-table join. A representative query retrieves revised components for a given change notice:

• SELECT REVISED_ITEM, COMPONENT_ITEM, ACTION, COMPONENT_QUANTITY, OLD_OP_SEQ_NUM, OPERATION_SEQUENCE_NUM, EFFECTIVITY_DATE FROM APPS.ENG_WEB_REVISED_COMPS_V WHERE CHANGE_NOTICE = :p_change_notice ORDER BY REVISED_ITEM, COMPONENT_SEQUENCE_ID;
• SELECT ORGANIZATION_CODE, ITEM_NUM, ACTION, EFFECTIVITY_DATE, EFFECTIVITY_TIME FROM APPS.ENG_WEB_REVISED_COMPS_V WHERE REVISED_ITEM_SEQUENCE_ID = :p_revised_item_seq_id;
• SELECT COMPONENT_ITEM, PRIMARY_UOM_CODE, DESCRIPTION, ENG_ITEM_FLAG FROM APPS.ENG_WEB_REVISED_COMPS_V WHERE ACTION = 'Add' AND ORGANIZATION_ID = :p_org_id;

Because the view is a UNION over revision and base component structures, queries should always constrain by organization or revision identifiers to limit the row set appropriately, and callers should note that the second branch is restricted to rows with a null implementation date.