Results for “common_item_description”

4 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.BOM_OPERATIONAL_ROUTINGS_ERV is an Oracle E-Business Suite reporting view that exposes operational routing header information for manufactured assemblies, enriched with descriptive attributes drawn from adjacent master data entities. The "_ERV" suffix denotes an "Entity Relationship View" — a denormalized, read-only projection intended to spare report developers and integrators from writing the multi-table joins that the routing data model otherwise requires. It is defined in the APPS schema and is available in both the 12.1.1 and 12.2.2 releases, where the documented underlying objects and column list are identical.

The view sits in the Oracle Manufacturing (BOM) module domain. Its driving entity is BOM_OPERATIONAL_ROUTINGS, the table that stores routing headers — one row per assembly, organization, alternate routing designator, and routing sequence. The view decorates each of those rows with organization codes and names, item concatenated segments and descriptions, primary unit of measure, revision, completion subinventory and locator, line code, common-item information, and the standard WHO audit columns. It is therefore a convenient single source for functional reports, concurrent program extracts, and inbound/outbound interface staging that need routing context without navigating the full relational schema.

Underlying Base Objects

The documented base objects referenced by the view are BOM_OPERATIONAL_ROUTINGS, HR_ALL_ORGANIZATION_UNITS_TL, MTL_ITEM_FLEXFIELDS, MTL_ITEM_LOCATIONS_KFV, MTL_PARAMETERS, MTL_RTG_ITEM_REVISIONS, MTL_SECONDARY_INVENTORIES, MTL_SYSTEM_ITEMS_VL, and WIP_LINES. BOM_OPERATIONAL_ROUTINGS is the primary table and supplies all routing-specific columns. HR_ALL_ORGANIZATION_UNITS_TL provides the translated organization name (aliased ORG1.NAME), while MTL_PARAMETERS supplies the short ORGANIZATION_CODE (ORG2). MTL_SYSTEM_ITEMS_VL appears twice — once as the assembly item and once as the common routing item — yielding concatenated segment values, descriptions, UOM, product family reference, and EAM item type. MTL_ITEM_FLEXFIELDS supplies the FLEX.ITEM_NUMBER values. MTL_SECONDARY_INVENTORIES and MTL_ITEM_LOCATIONS_KFV resolve the completion subinventory and locator descriptions. MTL_RTG_ITEM_REVISIONS provides PROCESS_REVISION, and WIP_LINES supplies LINE_CODE. MTL_SYSTEM_ITEMS_VL also contributes the NVL(MSI.LOCATOR_TYPE,1) expression that drives the SUB_LOCATOR_CONTROL column.

Key Columns

Common Use Cases and Queries

Typical scenarios include producing routings listings for shop-floor documentation, extracting routing headers for conversion or migration loads, replicating routing data into a data warehouse, and cross-referencing routings to completion locators and production lines. A representative query that lists active routings by organization and assembly is:

SELECT ORGANIZATION_CODE, CONCATENATED_SEGMENTS, DESCRIPTION,
       ALTERNATE_ROUTING_DESIGNATOR, PROCESS_REVISION,
       COMPLETION_SUBINVENTORY, LOCATOR, LINE_CODE, TOTAL_PRODUCT_CYCLE_TIME
  FROM APPS.BOM_OPERATIONAL_ROUTINGS_ERV
 WHERE ORGANIZATION_CODE = :p_org_code
   AND ASSEMBLY_ITEM_ID  = :p_assembly_item_id
 ORDER BY ALTERNATE_ROUTING_DESIGNATOR, ROUTING_SEQUENCE_ID;

Note that this view exposes routing headers only; operation-level detail such as operation sequence, department, and resource requirements must be obtained from BOM_OPERATION_SEQUENCES and related tables. Reports requiring operation detail should join the view to those entities on ROUTING_SEQUENCE_ID and ORGANIZATION_ID. Because the view joins several translation and key flexfield views, performance-sensitive extracts should filter by ORGANIZATION_ID and ASSEMBLY_ITEM_ID rather than relying on descriptive columns alone.