Results for “bombv_work_order_rtg_opratns”

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

Overview

The BOMBV_WORK_ORDER_RTG_OPRATNS view is a read-only, retrofitted database object owned by the APPS schema within the Oracle E-Business Suite Bills of Material (BOM) product module. It presents work order routing operation detail — the discrete operation steps that make up a manufacturing routing for an assembly — in a flattened, reporting-friendly form that joins operation sequence records to their parent routing, organization, and item context.

The view is explicitly defined WITH READ ONLY, confirming it is intended purely for query, reporting, and integration consumption rather than transactional DML. It is a "Business View" (indicated by the BOMBV_ prefix) and is documented as retrofitted, meaning it has been carried forward across EBS releases and remains valid in both 12.1.1 and 12.2.2. Because the view exposes user-oriented names alongside internal identifiers, it is well suited to ad-hoc reporting, custom concurrent programs, and inbound/outbound interfaces that need operation-level routing data without navigating the normalized base tables directly.

Underlying Base Objects

The view is defined over five base objects, all referenced through APPS synonyms:

• BOM_OPERATIONAL_ROUTINGS (OP) — the routing header; supplies the alternate routing designator and the common routing sequence identifier.
• BOM_OPERATION_SEQUENCES (SQ) — the operation lines; supplies sequence number, description, yield, lead time percent, and effectivity dates.
• MTL_PARAMETERS (PA) — the organization parameters table; supplies the organization code.
• MTL_SYSTEM_ITEMS (SY) — the item master; joined on assembly item and organization to anchor the routing to its item.
• HR_ALL_ORGANIZATION_UNITS (AL) — the organization definition; supplies the organization name.

Joins are performed on ORGANIZATION_ID across OP, PA, AL, and SY, and on ROUTING_SEQUENCE_ID = COMMON_ROUTING_SEQUENCE_ID between OP and SQ. Two filters constrain the result set: CFM_ROUTING_FLAG = 2 OR IS NULL (limiting to standard, non-configurable routings) and OPERATION_TYPE = 1 OR IS NULL (standard operations). A security predicate '_SEC:OP.ORGANIZATION_ID' IS NOT NULL enforces organization-level access control through the EBS security framework.

Key Columns

• SEQUENCE_NUMBER — the operation sequence number within the routing.
• OPERATION_YIELD — mapped from SQ.YIELD; the expected percentage yield of the operation. This is the column most directly associated with the user's search term "operation_yield" and is the primary reason this view is queried for yield analysis.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — effectivity window of the operation (from EFFECTIVITY_DATE and DISABLE_DATE).
• ALTERNATE_ROUTING_CODE — the alternate routing designator.
• ORGANIZATION_CODE / ORGANIZATION_NAME — reporting-friendly organization identifiers.
• DESCRIPTION — the operation description.
• MINIMUM_TRANSFER_QUANTITY and OPERATION_LEAD_TIME_PERCENT — planning attributes for the operation.
• ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, STANDARD_OPERATION_ID, DEPARTMENT_ID — internal keys linking to the base routing, department, and standard operation definitions.
• _LA:* columns — lookup translation placeholders (count point type, backflush, option dependent, reference flags) resolved from MFG_LOOKUPS for display.
• UPDATED_ON / UPDATED_BY / CREATED_ON / CREATED_BY — audit columns from the operation sequence record.

Common Use Cases and Queries

Typical uses include operation yield analysis, routing step reporting, and cross-referencing operations to items and organizations. A representative query for the "operation_yield" search:

SELECT ORGANIZATION_CODE,
       "_KF:ROUTING_ITEM_NAME" AS ITEM,
       ALTERNATE_ROUTING_CODE,
       SEQUENCE_NUMBER,
       DESCRIPTION,
       OPERATION_YIELD,
       OPERATION_LEAD_TIME_PERCENT
FROM   APPS.BOMBV_WORK_ORDER_RTG_OPRATNS
WHERE  OPERATION_YIELD < 100
ORDER BY ORGANIZATION_CODE, SEQUENCE_NUMBER;

Because the view filters to standard routings and operations and enforces organization security, queries automatically return only the routings and organizations the user is authorized to see in the current responsibility context.