Search Results bombv_routing_revisions




Overview
Explore in AI Chat

Overview

BOMBV_ROUTING_REVISIONS is a read-only Oracle EBS view owned by the APPS schema within the Bills of Material (BOM) product family. It exposes routing revision information for inventory items across organizations, presenting a denormalized, business-friendly projection of routing revision records that would otherwise require multiple joins against MTL_RTG_ITEM_REVISIONS and related master data tables. In Oracle EBS 12.1.1 and 12.2.2, the view carries a "Retrofitted" designation, indicating that it was introduced or regenerated to preserve backward compatibility with earlier forms, reports, or integration interfaces that depended on the legacy object definition.

The view is defined WITH READ ONLY, meaning it cannot be used as a DML target; it serves purely as a query surface for reporting, data extraction, and downstream integration. The user search term "eco_initiation_date" corresponds directly to the ECO_INITIATION_DATE column, which maps to the underlying RT.ECN_INITIATION_DATE attribute in MTL_RTG_ITEM_REVISIONS. This column records the date on which an Engineering Change Notice (ECN) associated with a routing revision was initiated, making the view a convenient source for ECO and change-management reporting.

Underlying Base Objects

The view is constructed by joining four base objects via the APPS schema's synonyms:

The join predicates require all four objects to share the same ORGANIZATION_ID and that the inventory item exists in MTL_SYSTEM_ITEMS_B for that organization. A security predicate, '_SEC:RT.ORGANIZATION_ID' IS NOT NULL, is embedded to enforce organization-level (MOAC) access controls, restricting visible rows to organizations the querying responsibility is authorized to access.

Key Columns

  • REVISION — the routing process revision (RT.PROCESS_REVISION).
  • ORGANIZATION_CODE / ORGANIZATION_NAME — the organization short code and descriptive name.
  • _KF:ROUTING_ITEM_NAME — a descriptive flexfield key reference column; the literal value is the descriptive flexfield segment reference _KF:INV:MSTK:SY.
  • ECO_INITIATION_DATE — the ECN initiation date (RT.ECN_INITIATION_DATE), the column most relevant to the ECO search.
  • IMPLEMENTATION_DATE — the date the revision was implemented.
  • START_EFFECTIVITY_DATE — aliased from RT.EFFECTIVITY_DATE; the date the revision takes effect.
  • CHANGE_NOTICE — the associated ECN or change notice reference.
  • ALTERNATE_DESIGNATOR — exposed as a NULL placeholder in the view text.
  • ORGANIZATION_ID, INVENTORY_ITEM_ID — key identifiers for organizational and item context.
  • UPDATED_ON, UPDATED_BY, CREATED_ON, CREATED_BY — standard audit columns from the base table.

Common Use Cases and Queries

Typical uses include ECO/ECN change-history reporting, routing revision audits, and integration extracts feeding downstream MES or PLM systems. Because the view resolves organization names and item context, it is well suited to ad hoc reporting without manual joins.

Sample query returning ECO-initiated routing revisions for a specific item:

SELECT organization_code,
       organization_name,
       revision,
       eco_initiation_date,
       implementation_date,
       start_effective_date,
       change_notice
  FROM apps.bombv_routing_revisions
 WHERE inventory_item_id = :p_item_id
   AND organization_id   = :p_org_id
 ORDER BY eco_initiation_date DESC;

Sample query filtering by ECO initiation date range across organizations:

SELECT organization_code, revision, change_notice, eco_initiation_date
  FROM apps.bombv_routing_revisions
 WHERE eco_initiation_date BETWEEN :p_from_date AND :p_to_date;

As the view is read-only and MOAC-secured, queries automatically respect the organization access of the active responsibility.