Search Results engbv_eco_revised_items




Overview
Explore in AI Chat

Overview

ENGBV_ECO_REVISED_ITEMS is an APPS-owned, read-only view in the Oracle E-Business Suite Engineering (ENG) module. It presents the revised item lines associated with Engineering Change Orders (ECOs) so that engineers, planners, and reporting tools can review the effect of an ECO on individual items without querying the underlying transactional tables directly. The view is registered as VALID and is available in both Oracle EBS 12.1.1 and 12.2.2.

The view is a business view (the "BV" in the name) rather than a pure table join. Its SELECT list contains OAF-style symbolic column aliases such as _KF:REVISED_ITEM_NAME, _LA:STATUS_TYPE, and _SEC:RE.ORGANIZATION_ID. These markers are consumed by the Oracle Applications Framework based Engineering workbench and are not exposed to end users as literal text. The view is defined WITH READ ONLY, so it cannot be used for DML.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both accessed through APPS synonyms:

  • ENG_REVISED_ITEMS — the primary source (aliased RE). It supplies the revised item identifier, revision, ECO relationship, scheduling and implementation dates, cancellation data, dispositions, and the USE_UP_PLAN_NAME.
  • MTL_SYSTEM_ITEMS_B — the item master (aliased SY), used to supply the revised item name and to validate organization/item context.

Joins are made on RE.ORGANIZATION_ID = SY.ORGANIZATION_ID and RE.REVISED_ITEM_ID = SY.INVENTORY_ITEM_ID. An additional organization security predicate (_SEC:RE.ORGANIZATION_ID IS NOT NULL) enforces multi-org access filtering at the framework layer.

Key Columns

The view exposes the following columns of note:

Common Use Cases and Queries

Typical reporting scenarios include impact analysis of an ECO on a given item, identifying which revised items carry a use-up plan, and reconciling ECO implementation status with inventory planning. A representative query is:

SELECT eco_name, _kf_revised_item_name, new_item_revision, start_effective_date, use_up_plan_name, implementation_date FROM apps.engbv_eco_revised_items WHERE organization_id = :org_id AND use_up_plan_name IS NOT NULL ORDER BY eco_name, start_effective_date;

A second query retrieves all revisions tied to a specific ECO:

SELECT eco_name, new_item_revision, status_type, disposition_type, mrp_active, update_wip FROM apps.engbv_eco_revised_items WHERE eco_name = :eco;

Because the view is read-only and includes organization security predicates, it is suitable for BI Publisher reports, OAF-based engineering dashboards, and integration extracts that must respect multi-org access. Direct DML against the view is not supported; updates must be performed against ENG_REVISED_ITEMS.