Search Results eng_ref_desig_action

Overview

APPS.ENG_WEB_SUB_COMPS_V is a reporting view in the Oracle E-Business Suite engineering and bills of material schema. It presents substitute component information for engineering revised items, joining the substitution definition in BOM_SUBSTITUTE_COMPONENTS to the parent component line, the revised item context, the substitute inventory item master, and the manufacturing lookup that decodes the substitution action type. The view is primarily consumed by the engineering web user interface and by downstream reporting that needs a flattened, denormalized picture of substitute components attached to an engineering change.

The view name derives from its purpose: a web-facing (WEB) presentation of substitute components (SUB_COMPS) within the engineering (ENG) module. Because the view joins the item master key flexfield view, callers receive the concatenated item segment string, padded variant, unit of measure code, and description without performing those joins themselves.

Underlying Base Objects

The view is defined over five documented base objects: BOM_INVENTORY_COMPONENTS (a view), BOM_SUBSTITUTE_COMPONENTS, ENG_REVISED_ITEMS, MFG_LOOKUPS (a view), and MTL_SYSTEM_ITEMS_KFV, the last three exposed as synonyms in the APPS schema. The joins follow the BOM revision model:

• BIC.COMPONENT_SEQUENCE_ID = BSC.COMPONENT_SEQUENCE_ID links each substitute component record to its parent component line.
• BIC.REVISED_ITEM_SEQUENCE_ID = ERI.REVISED_ITEM_SEQUENCE_ID ties the component line to the revised item.
• BSC.CHANGE_NOTICE = ERI.CHANGE_NOTICE further scopes substitution rows to the specific engineering change notice.
• MSI.INVENTORY_ITEM_ID = BSC.SUBSTITUTE_COMPONENT_ID and MSI.ORGANIZATION_ID = ERI.ORGANIZATION_ID identify the substitute item in the correct inventory organization.
• ML.LOOKUP_CODE = BSC.ACD_TYPE with ML.LOOKUP_TYPE = 'ENG_REF_DESIG_ACTION' resolves the action code to its meaning.

The join to BOM_INVENTORY_COMPONENTS is intrinsic: substitute components exist only in the context of a component line within a bill, so the view effectively restricts its output to substitutions that participate in a valid component/revised-item relationship.

Key Columns

• COMPONENT_SEQUENCE_ID — Identifier of the parent component line, used to correlate a substitute back to its BOM component.
• ACTION — The decoded meaning from MFG_LOOKUPS for the ENG_REF_DESIG_ACTION lookup type, describing the substitution action (for example, reference designator related substitutions).
• SUBSTITUTE_COMPONENT — The concatenated segment string of the substitute item from MTL_SYSTEM_ITEMS_KFV, suitable for display.
• PADDED_CONCATENATED_SEGMENTS — A padded variant of the item segment string, typically used for alignment or sorting.
• SUBSTITUTE_ITEM_QUANTITY — Quantity of the substitute item allowed or required in place of the original component.
• PRIMARY_UOM_CODE — Primary unit of measure of the substitute item.
• DESCRIPTION — Description of the substitute item.

Notably, the view does not expose organization identifier, item identifier, or change notice columns directly, so consumers requiring that granularity must join back to the base substitution tables.

Common Use Cases and Queries

The view supports engineering workbench reporting, substitute component listings on engineering change notices, and integration extracts feeding external PLM or planning systems. A typical query retrieves all substitutions for a given component sequence:

SELECT component_sequence_id, action, substitute_component, substitute_item_quantity, primary_uom_code, description FROM apps.eng_web_sub_comps_v WHERE component_sequence_id = :component_sequence_id ORDER BY substitute_component;

Because the view resolves the ENG_REF_DESIG_ACTION lookup internally, it is convenient for reports that must display the human-readable action rather than the raw ACD_TYPE code. Consumers should be aware that since BOM_SUBSTITUTE_COMPONENTS and ENG_REVISED_ITEMS are joined on CHANGE_NOTICE, rows without a matching change notice context will not appear. For performance, queries should filter on COMPONENT_SEQUENCE_ID or supply equivalent selective predicates, as the view performs multiple joins across the BOM and item master schema. Organizations operating in a multi-org environment should note that the view implicitly carries organization context through ERI.ORGANIZATION_ID rather than exposing it as a selectable column.