Search Results product_family_item_id

Overview

BOM_OPERATIONAL_ROUTINGS_V is an APPS-owned database view that presents operational routing header information for manufactured assemblies in Oracle E-Business Suite release 12.1.1 and 12.2.2. It is defined in the BOM (Bills of Material) product module and is registered as a VALID object in the ETRM repository. The view consolidates the routing header record from BOM_OPERATIONAL_ROUTINGS with descriptive and control attributes drawn from inventory, item, line, and flexfield sources, producing a denormalized read model suitable for reporting, concurrent programs, and integration extracts.

The view is particularly relevant to completion and backflush analysis because it exposes SUB_LOCATOR_CONTROL, a derived column that indicates whether locator (subinventory location) control is enabled for the routing completion subinventory. This is computed as NVL(MSI.LOCATOR_TYPE, 1) from MTL_SECONDARY_INVENTORIES, so a routing whose completion subinventory has no matching secondary inventory record defaults to a locator type of 1. Because the join to MTL_SECONDARY_INVENTORIES is outer (+), routings with no valid completion subinventory still appear with this default value, which preserves row completeness at the cost of masking missing setup.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

• BOM_OPERATIONAL_ROUTINGS (SYNONYM) — the driving table, supplying routing identity and header attributes.
• MTL_SYSTEM_ITEMS (SYNONYM) — supplies assembly item attributes including description, UOM, product family, and EAM item type.
• MTL_ITEM_FLEXFIELDS (VIEW) — supplies the concatenated ITEM_NUMBER via the key flexfield.
• MTL_SECONDARY_INVENTORIES (SYNONYM) — supplies LOCATOR_TYPE, from which SUB_LOCATOR_CONTROL is derived.
• WIP_LINES (SYNONYM) — supplies LINE_CODE for the routing line association.

All joins except the assembly item join are outer joins, keyed on ORGANIZATION_ID and the appropriate identifier. The assembly item join to MTL_SYSTEM_ITEMS is an inner join, so a routing whose assembly item is missing from the item master will not be returned.

Key Columns

• ROUTING_SEQUENCE_ID, ASSEMBLY_ITEM_ID, ORGANIZATION_ID — primary routing identity and multi-org context.
• ALTERNATE_ROUTING_DESIGNATOR, ROUTING_TYPE, PRIORITY — routing selection and precedence attributes.
• COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID, SUB_LOCATOR_CONTROL — completion destination and locator control behavior.
• ITEM_NUMBER, DESCRIPTION, UOM, PRODUCT_FAMILY_ITEM_ID, EAM_ITEM_TYPE — item identification and classification.
• LINE_CODE — manufacturing line association from WIP_LINES.
• CFM_ROUTING_FLAG, MIXED_MODEL_MAP_FLAG, CTP_FLAG, SERIALIZATION_START_OP, TOTAL_PRODUCT_CYCLE_TIME — planning and execution flags, several defaulted via NVL.
• ATTRIBUTE1 through ATTRIBUTE15, REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — DFF and concurrent program audit columns.

Common Use Cases and Queries

Typical uses include listing routings by organization and assembly, validating completion subinventory and locator control setup, and feeding routing data into planning or shop floor integrations.

• Routings for an item and org: SELECT routing_sequence_id, alternate_routing_designator, item_number, completion_subinventory, sub_locator_control FROM bom_operational_routings_v WHERE organization_id = :org AND assembly_item_id = :item;
• Locator-control audit: SELECT organization_id, assembly_item_id, completion_subinventory, sub_locator_control FROM bom_operational_routings_v WHERE sub_locator_control = 1;
• Routings by manufacturing line: SELECT line_code, COUNT(*) FROM bom_operational_routings_v GROUP BY line_code;

Because SUB_LOCATOR_CONTROL is NVL-defaulted, queries intended to detect missing subinventory setup should join MTL_SECONDARY_INVENTORIES directly rather than relying on this column alone.