Results for “bombv_flow_rtg_line_operations”

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

Overview

BOMBV_FLOW_RTG_LINE_OPERATIONS is an APPS-owned view in the Oracle E-Business Suite Bills of Material (BOM) module, delivered as part of the Flow Manufacturing routing data model. Its name reflects its purpose: it exposes line operations associated with flow routings. In Oracle Flow Manufacturing, a routing can be designated as a flow (or "common") routing, and individual operations are sequenced against it. This view flattens that relationship, joining routing headers, operation sequences, organization definitions, and item master data into a single denormalized row per operation sequence.

The view is marked in ETRM as "Retrofitted," indicating it is a compatibility object maintained so that reports, concurrent programs, or integrations written against an earlier release continue to function. It is not a base table; it does not store data. Each row it returns is derived at query time from its underlying operational tables. The presence of the underscore-prefixed columns (for example, _KF:ROUTING_ITEM_NAME and the _LA: lookup columns) indicates this view is consumed by Oracle's Applications Technology key-flexfield and lookup-resolution framework, typically surfaced through an Oracle Forms or OAF-based inquiry screen rather than as a standalone reporting view. This distinction matters: business logic such as key flexfield display and lookup meaning resolution is applied by the runtime layer, not by plain SQL.

Underlying Base Objects

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

• BOM_OPERATIONAL_ROUTINGS — the routing header, supplying the assembly item, organization, and the common/flow routing sequence identifier.
• BOM_OPERATION_SEQUENCES — the routing detail lines, supplying operation sequence number, description, yield, lead time, and the effectivity and disable dates.
• MTL_PARAMETERS — the organization parameters row, providing the ORGANIZATION_CODE.
• HR_ALL_ORGANIZATION_UNITS — the organization unit, providing the printable NAME.
• MTL_SYSTEM_ITEMS_B — the item master, joined on ASSEMBLY_ITEM_ID and ORGANIZATION_ID to confirm the routed item.

The join path is driven from the routing header: OP.ORGANIZATION_ID is matched to MTL_PARAMETERS, to HR_ALL_ORGANIZATION_UNITS, and to MTL_SYSTEM_ITEMS_B, while SQ.ROUTING_SEQUENCE_ID is matched to OP.COMMON_ROUTING_SEQUENCE_ID. The filter OP.CFM_ROUTING_FLAG = 1 restricts output to flow (CFM) routings, and SQ.OPERATION_TYPE = 3 selects the operation-type category relevant to flow line operations. Row-level security is enforced through the _SEC:OP.ORGANIZATION_ID predicate, and multi-organization filtering via ORG_ID applies through the organization units join.

Key Columns

The view exposes a broad set of routing attributes. Notable columns include:

• SEQUENCE_NUMBER — the operation sequence number from BOM_OPERATION_SEQUENCES.OPERATION_SEQ_NUM.
• ORGANIZATION_CODE, ORGANIZATION_NAME — identifier and display name of the manufacturing organization.
• ALTERNATE_ROUTING_CODE — the alternate routing designator from the routing header.
• START_EFFECTIVE_DATE and END_EFFECTIVE_DATE — mapped from SQ.EFFECTIVITY_DATE and SQ.DISABLE_DATE respectively. Users searching on end_effective_date will find this column carries the date on which the operation ceases to be effective; a null value ordinarily denotes no scheduled end.
• OPERATION_YIELD, OPERATION_CUMULATIVE_YIELD, REVERSE_CUMULATIVE_YIELD — yield metrics at and up to the operation.
• CALCULATED_LABOR_TIME, CALCULATED_MACHINE_TIME, CALCULATED_ELAPSED_TIME — system-derived times, paired with the corresponding *_USER entered values.
• MINIMUM_TRANSFER_QUANTITY, NET_PLANNING_PERCENT, OPERATION_LEAD_TIME_PERCENT — planning and transfer controls.
• Key identifiers ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, STANDARD_OPERATION_ID, DEPARTMENT_ID, plus audit columns.

Lookup-backed flags — count point type, backflush flag, option-dependent flag, and reference flag — are resolved through the BOM_COUNT_POINT_TYPE and SYS_YES_NO lookup types via the framework columns rather than exposed as decoded text.

Common Use Cases and Queries

Typical uses include flow-routing inquiries, effectivity auditing, and yield or time analysis. To retrieve currently active operations and their end dates for an organization:

SELECT SEQUENCE_NUMBER, ORGANIZATION_CODE, ALTERNATE_ROUTING_CODE,
  DESCRIPTION, START_EFFECTIVE_DATE, END_EFFECTIVE_DATE, OPERATION_YIELD
 FROM APPS.BOMBV_FLOW_RTG_LINE_OPERATIONS
 WHERE ORGANIZATION_CODE = :org_code
 AND (END_EFFECTIVE_DATE IS NULL OR END_EFFECTIVE_DATE >= TRUNC(SYSDATE))
 ORDER BY SEQUENCE_NUMBER;

Because the view already joins item and organization data, users can also filter by the routing item key flexfield or report cumulative yields across a routing. In Oracle EBS 12.1.1 and 12.2.2 the definition is materially the same; the 12.2.2 metadata confirms the same five base objects. Note that the view's row-level security and key-flexfield columns are intended for framework consumption, so standalone SQL should rely on the concrete database columns rather than the underscore-prefixed framework columns, which return literal label strings outside that context.