Results for “bom_routing_alternates_v”

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

Overview

The BOM_ROUTING_ALTERNATES_V view is a reporting and integration object owned by the APPS schema within the Oracle Bills of Material (BOM) module. Its documented purpose is to resolve all foreign key references defined on the base table BOM_ROUTING_ALTERNATES, presenting the routing alternate data in a denormalized, human-readable form. Rather than exposing raw identifier values alone, the view joins the operational routing records to their alternate designator definitions so that descriptive text accompanies the key routing attributes.

In Oracle EBS 12.1.1 and 12.2.2, this view is typically consumed by reports, concurrent programs, and custom integrations that need to enumerate alternate routings for an assembly without performing the same join logic repeatedly. Because it is a view rather than a table, it carries no storage of its own and inherits the security and access characteristics of the APPS schema. Status is documented as VALID, confirming that the view compiles cleanly against the referenced base objects in the target release.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through APPS synonyms:

• BOM_OPERATIONAL_ROUTINGS (aliased BOR) — supplies the core routing records, including the assembly, organization, routing sequence, and the alternate routing designator.
• BOM_ALTERNATE_DESIGNATORS (aliased BAD) — supplies the descriptive text that resolves the alternate routing designator code.

The join condition in the view text handles two distinct cases. When the alternate routing designator is null, the view matches the null designator code with an ORGANIZATION_ID of -1 in BOM_ALTERNATE_DESIGNATORS, which represents the seeded global or null-designator row. Otherwise, it matches the routing's ALTERNATE_ROUTING_DESIGNATOR to the designator code and enforces that ORGANIZATION_ID values agree between the two tables. This dual-branch predicate ensures that primary (non-alternate) routings and explicitly named alternates are both returned without losing records to outer-join ambiguity.

Key Columns

• ASSEMBLY_ITEM_ID — Inventory item identifier of the assembly whose routing is described.
• ORGANIZATION_ID — Operating unit or inventory organization owning the routing record.
• ALTERNATE_ROUTING_DESIGNATOR — Code identifying the alternate routing; null for the primary routing.
• ROUTING_SEQUENCE_ID — Surrogate key of the routing sequence row in BOM_OPERATIONAL_ROUTINGS.
• COMMON_ROUTING_SEQUENCE_ID — Reference to a shared/common routing sequence where applicable.
• COMPLETION_SUBINVENTORY — Default subinventory into which the assembly is completed.
• COMPLETION_LOCATOR_ID — Default locator within the completion subinventory.
• ROUTING_TYPE — Classifies the routing (for example, primary versus alternate), and is the attribute most frequently used as a filtering predicate by callers.
• DESCRIPTION — Descriptive text obtained from BOM_ALTERNATE_DESIGNATORS, resolving the alternate designator code.
• CFM_ROUTING_FLAG — Indicates whether the routing participates in flow (CFM) manufacturing.
• PENDING_FROM_ECN — Engineering change order reference pending against the routing.

Common Use Cases and Queries

Typical scenarios include validating alternate routing setup for an assembly, feeding routing data into shop floor or scheduling interfaces, and reporting on completion defaults by alternate. A representative query filtering on routing type and organization follows:

• SELECT assembly_item_id, organization_id, alternate_routing_designator, routing_type, description FROM bom_routing_alternates_v WHERE organization_id = :org_id AND routing_type = :routing_type;
• SELECT alternate_routing_designator, description, completion_subinventory FROM bom_routing_alternates_v WHERE assembly_item_id = :item_id AND organization_id = :org_id ORDER BY alternate_routing_designator;

Because the view resolves the alternate designator description internally, consumers avoid re-implementing the BOM_ALTERNATE_DESIGNATORS join, including the special null-designator handling. Applications should treat the view as read-only and, for performance-sensitive joins, add predicates on ORGANIZATION_ID and ASSEMBLY_ITEM_ID to leverage the underlying indexed columns.