Search Results effectivity_time




Overview

The ENG_WEB_REVISED_COMPS_V view is an Oracle Engineering (ENG) dictionary object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to present "revised component on an ECO" — that is, the component lines attached to an Engineering Change Order (ECO) — formatted specifically for use by Oracle self-service web applications. It exposes component-level detail for revised items under change control, combining manufacturing item attributes with ECO revision data so that web-based pages (such as those in Oracle Self-Service Engineering) can display pending component changes without the user needing direct access to base engineering tables.

Because it is a view rather than a table, it is read-only and derives all of its content from the underlying engineering, bills-of-material, and item master structures. This makes it a reporting and integration surface rather than a transactional object.

Underlying Base Objects

The view is defined over the following documented base objects:

  • BOM_INVENTORY_COMPONENTS (VIEW) — provides the existing (old) component lines used to resolve prior operation sequence and component sequence information.
  • ENG_REVISED_COMPONENTS (SYNONYM) — the staged/revised component rows created by the ECO.
  • ENG_REVISED_ITEMS (SYNONYM) — the parent revised item header for each ECO, supplying the organization, change notice, and revised item reference.
  • MFG_LOOKUPS (VIEW) — resolves the ACD_TYPE lookup code against lookup type ECG_ACTION to yield the human-readable ACTION.
  • MTL_PARAMETERS (SYNONYM) — supplies the organization code context.
  • MTL_SYSTEM_ITEMS_KFV (SYNONYM) — the key-flex item view, joined twice: once for the component item and once for the revised item.

The view text is a UNION of two query branches, both joining revised components to their ECO headers, item master records, and action lookups. The joins align REVISED_ITEM_SEQUENCE_ID, COMPONENT_ITEM_ID, and ORGANIZATION_ID across the relevant objects.

Key Columns

The view exposes a mixture of identifiers, descriptive text, and engineering attributes. Notable columns include:

Common Use Cases and Queries

Typical uses include ECO impact reporting, self-service engineering pages, and integrations that must show pending component revisions. A representative query filtering on the searched flag is:

  • SELECT revised_item, component_item, action, component_quantity, eng_item_flag, effectivity_date FROM apps.eng_web_revised_comps_v WHERE change_notice = :eco AND eng_item_flag = 'Y';
  • Reporting revised components grouped by CHANGE_NOTICE and ORGANIZATION_CODE.
  • Feeding web UI lists that display component actions for a selected ECO.