Search Results implemented_flag




Overview
Explore in AI Chat

Overview

The APPS.BOM_BILL_RELEASED_REVISIONS_V view exposes released revision information for inventory items within Oracle E-Business Suite. It provides a consolidated, read-only projection of item revisions that have been formally released through the engineering change order (ECO) process, combining revision definition data with implementation and effectivity details. In the context of EBS 12.1.1 and 12.2.2, this view functions primarily as a reporting and integration artifact rather than a transactional object. It is classified as an internal Oracle view, and the ETRM documentation carries the standard Oracle warning that the object is intended for use by standard Oracle Applications programs only and is not supported for direct customer access. Its FND Design Data identifier is BOM.BOM_BILL_RELEASED_REVISIONS_V, indicating ownership by the Bills of Material product family.

Underlying Base Objects

According to the documented dependency information, BOM_BILL_RELEASED_REVISIONS_V references two base objects within the APPS schema: ENG_REVISED_ITEMS (exposed as a synonym) and MTL_ITEM_REVISIONS_B (also exposed as a synonym). ENG_REVISED_ITEMS supplies the engineering revision and change implementation context, while MTL_ITEM_REVISIONS_B provides the item revision definitions themselves. The view joins these sources to present the set of revisions that have been released, along with their effectivity windows. In the reverse dependency direction, the view is referenced by WIP_WOL_PROCESSOR, a Work in Process work order processing program, confirming that it is consumed by standard Oracle application logic rather than only by ad hoc queries.

Key Columns

  • INVENTORY_ITEM_ID (NUMBER) — Inventory item identifier for the revised item.
  • ORGANIZATION_ID (NUMBER) — Organization identifier, scoping the revision to a specific inventory organization.
  • REVISION (VARCHAR2) — The item revision code.
  • EFFECTIVITY_DATE (DATE) — The date on which the revision becomes effective.
  • IMPLEMENTATION_DATE (DATE) — The ECO implementation date for the revision.
  • HIGH_DATE (DATE) — The last minute before the next higher revision becomes effective, defining the upper bound of the revision's active window.
  • IMPLEMENTED_FLAG (NUMBER) — Indicates whether the revision has been implemented (Yes or No). This is the column most frequently targeted in searches, as it allows filtering to revisions that have completed implementation.

Common Use Cases and Queries

The view is typically used to determine which revisions of an item are released and currently effective, and to distinguish implemented revisions from those that are merely defined. A representative query retrieves the complete released revision set for a given item and organization:

  • SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION, EFFECTIVITY_DATE, IMPLEMENTATION_DATE, HIGH_DATE, IMPLEMENTED_FLAG FROM APPS.BOM_BILL_RELEASED_REVISIONS_V;

To isolate implemented revisions for a specific item organization combination, the IMPLEMENTED_FLAG column can be constrained:

  • SELECT REVISION, EFFECTIVITY_DATE, HIGH_DATE FROM APPS.BOM_BILL_RELEASED_REVISIONS_V WHERE INVENTORY_ITEM_ID = :item_id AND ORGANIZATION_ID = :org_id AND IMPLEMENTED_FLAG = 1;

Because the view is documented as Oracle Internal Use Only, direct customer queries should be treated as unsupported and used only for diagnostic or reporting purposes, with the understanding that the definition may change between releases.