Search Results quantity_related




Overview
Explore in AI Chat

Overview

ENG_COMPONENT_VIEW is a VALID Oracle E-Business Suite view owned by the APPS schema and delivered as part of the ENG (Engineering) product family. Its documented purpose is to join BOM_INVENTORY_COMPONENTS and ENG_REVISED_COMPONENTS so that the view can display all revised components belonging to a revised item. In practice, the view presents a consolidated, read-only picture of component lines as they exist across the engineering change and bill-of-material domains, allowing concurrent programs, forms, and custom reports to query a single object rather than navigating the two underlying sources separately.

Within the EBS reporting and integration layer, ENG_COMPONENT_VIEW functions as a semantic union of component data. Because it exposes engineering attributes such as change notices, effectivity dates, implementation and disable dates, and supply types alongside standard BOM component attributes, it is a natural access point for Engineering Change Order (ECO) reporting, revision comparison, and downstream integration extracts.

Underlying Base Objects

The ETRM metadata for 12.2.2 identifies two referenced base objects: BOM_INVENTORY_COMPONENTS, itself implemented as a VIEW, and ENG_REVISED_COMPONENTS, exposed as a SYNONYM. The view text confirms this by selecting its first block of columns from ENG_REVISED_COMPONENTS with alias A, then combining that result set by way of a UNION with a second block sourced from BOM_INVENTORY_COMPONENTS.

The union structure means the view surfaces both revised component records (those tied to an engineering revision, carrying REVISED_ITEM_SEQUENCE_ID) and standard inventory component records (carrying OLD_COMPONENT_SEQUENCE_ID and a TO_DATE conversion that nulls the cancellation date). Column positions are aligned across both branches so that consumers see a uniform shape regardless of which source produced a given row.

Key Columns

Note that in the BOM_INVENTORY_COMPONENTS branch, CANCELLATION_DATE is derived as TO_DATE('', 'DD-MON-YY') and CANCEL_COMMENTS resolves to NULL, so these two columns are effectively populated only for revised component rows.

Common Use Cases and Queries

Typical scenarios include listing every component associated with a revised item, comparing revised versus standard component lines, and extracting engineering attributes for ECO or cost analysis. A basic query filtering on the revised item sequence is shown below.

  • Retrieve all components for a revised item:
    SELECT component_sequence_id, component_item_id, item_num, change_notice, revised_item_sequence_id FROM apps.eng_component_view WHERE revised_item_sequence_id = :p_revised_item_seq_id;
  • List components with effectivity and disable dates for a change notice:
    SELECT component_item_id, item_num, effectivity_date, disable_date FROM apps.eng_component_view WHERE change_notice = :p_change_notice ORDER BY effectivity_date;
  • Identify configurable or optional components:
    SELECT component_sequence_id, item_num, optional, mutually_exclusive_options FROM apps.eng_component_view WHERE SO_BASIS IS NOT NULL OR optional = 1;
  • Extract components contributing to cost rollup:
    SELECT component_item_id, item_num, component_quantity, cost_factor FROM apps.eng_component_view WHERE include_in_cost_rollup = 1;

Because the view unites two branches, queries should be tuned against the discriminator columns (REVISED_ITEM_SEQUENCE_ID, CHANGE_NOTICE, OLD_COMPONENT_SEQUENCE_ID) rather than applying broad full-table scans, and consumers should be aware that date and comment fields are populated differently depending on the originating branch.