Results for “bombv_mfg_operations”

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

Overview

BOMBV_MFG_OPERATIONS is an APPS-owned, VALID view in the Oracle E-Business Suite Bills of Material (BOM) module. It is documented as a retrofitted object, meaning it was introduced or carried forward to expose a denormalized, business-facing representation of manufacturing routing operations that older Oracle EBS reporting interfaces (notably Oracle Business Views and the 11i-era BOM Business Views) expected to find. Rather than requiring report authors to join the routing, operation sequence, organization, and item tables manually, the view pre-joins them and applies column aliases that match the naming conventions of the legacy business view layer, alongside Oracle Application Object Library descriptive flexfield and lookup references expressed as _KF: and _LA: tokens.

In the 12.1.1 and 12.2.2 environments, the view serves as a read-only reporting and integration surface over the manufacturing routing definition. It is particularly relevant to searches for operation_lead_time_percent, because that attribute is exposed directly on the view (sourced from BOM_OPERATION_SEQUENCES.OPERATION_LEAD_TIME_PERCENT) without the caller needing to know the underlying table structure. The view is schema-qualified as APPS.BOMBV_MFG_OPERATIONS and is granted through the standard APPS synonym mechanism.

Underlying Base Objects

The ETRM metadata documents the following base objects, all referenced through APPS synonyms:

• BOM_OPERATIONAL_ROUTINGS — the routing header, aliased OP; supplies the alternate routing designator, routing sequence identifier, organization, and assembly item.
• BOM_OPERATION_SEQUENCES — the routing operation lines, aliased PR; supplies operation sequence number, description, lead time percent, yield, cumulative yield, disable date, and the calculated/entered labor, machine, and elapsed times.
• HR_ALL_ORGANIZATION_UNITS — aliased AL; supplies the organization name.
• MTL_PARAMETERS — aliased PA; supplies the organization code.
• MTL_SYSTEM_ITEMS — aliased SY; supplies the inventory item used to identify the routing assembly.

The join path is: BOM_OPERATIONAL_ROUTINGS.ORGANIZATION_ID equals MTL_PARAMETERS.ORGANIZATION_ID and HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID; the assembly item matches MTL_SYSTEM_ITEMS on INVENTORY_ITEM_ID and ORGANIZATION_ID; and BOM_OPERATION_SEQUENCES.ROUTING_SEQUENCE_ID equals BOM_OPERATIONAL_ROUTINGS.COMMON_ROUTING_SEQUENCE_ID. Row-level security is enforced through the organization ID predicate.

Key Columns

• SEQUENCE_NUMBER — operation sequence number within the routing.
• ALTERNATE_ROUTING_CODE and ROUTING_SEQUENCE_ID — identify the routing and its alternate designator.
• ORGANIZATION_CODE / ORGANIZATION_NAME — reporting-friendly organization identifiers.
• OPERATION_LEAD_TIME_PERCENT — the percentage of operation lead time applied to scheduling; the column most frequently targeted in searches.
• OPERATION_YIELD, OPERATION_CUMULATIVE_YIELD, REVERSE_CUMULATIVE_YIELD — yield metrics for the operation and rolled-up routing position.
• CALCULATED_LABOR_TIME, CALCULATED_MACHINE_TIME, CALCULATED_ELAPSED_TIME — system-computed times from BOM_OPERATION_SEQUENCES.
• ENTERED_LABOR_TIME, ENTERED_MACHINE_TIME, USER_ELAPSED_TIME — user-maintained time values.
• NET_PLANNING_PERCENT, MINIMUM_TRANSFER_QUANTITY — planning and transfer attributes.
• START_EFFECTIVE_DATE / END_EFFECTIVITY_DATE — routing operation effective window (EFFECTIVITY_DATE and DISABLE_DATE).
• UPDATED_ON, UPDATED_BY, CREATED_ON, CREATED_BY — audit columns.

Common Use Cases and Queries

Typical uses include routing operation listings for shop floor documentation, lead time and yield analysis, and migration of data from legacy BOM reports. A representative query for the lead time attribute is:

SELECT organization_code, alternate_routing_code, sequence_number, description,
operation_lead_time_percent, operation_yield, calculated_elapsed_time
FROM apps.bombv_mfg_operations
WHERE organization_code = :org
AND operation_lead_time_percent IS NOT NULL
ORDER BY alternate_routing_code, sequence_number;

Because the view enforces organization-level security, callers must initialize the APPS environment (for example via FND_GLOBAL) or otherwise ensure the organization context is set before querying. It is a reporting construct only; it should not be used for insert, update, or delete operations against routing data.