Results for “default_subinventory”

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

Overview

BOM_STANDARD_OPERATIONS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and shipped with the Bills of Material (BOM) product family. It exposes the master definition of standard operations — the reusable operation templates that are copied into routing sequences when manufacturing bills of material and routings are built. In Oracle EBS 12.1.1 and 12.2.2 the view presents one row per standard operation, enriched with the owning department description and code, the WIP line code, and the decoded shutdown type meaning.

The view is commonly used in reporting, data extraction, and integration layers where a denormalized read-only projection of standard operations is preferable to joining the underlying base tables directly. Because it resolves department and lookup information through outer and inner joins, consumers obtain human-readable values without replicating the join logic. The LOWEST_ACCEPTABLE_YIELD column, which motivates many searches against this object, is exposed here alongside YIELD and OPERATION_YIELD_ENABLED, making the view the natural entry point for yield-related analysis.

Underlying Base Objects

The view is defined over four documented base objects:

• BOM_STANDARD_OPERATIONS (synonym) — the driving table, supplying the identifier, sequence, yield, count point, backflush, WMS, and descriptive flexfield attribute columns.
• BOM_DEPARTMENTS (synonym) — joined on DEPARTMENT_ID to supply DEPARTMENT_CODE and DEPARTMENT_DESCRIPTION.
• WIP_LINES (synonym) — outer-joined on LINE_ID to supply LINE_CODE.
• MFG_LOOKUPS (view) — outer-joined on SHUTDOWN_TYPE restricted to lookup type BOM_EAM_SHUTDOWN_TYPE, yielding SHUTDOWN_TYPE_VALUE.

Because BOM_DEPARTMENTS is joined without the outer operator, standard operations that are not associated with a valid department are not returned — a behavior worth noting when reconciling row counts against the base table.

Key Columns

• STANDARD_OPERATION_ID — primary key of the standard operation; the join key to routing and WIP operation tables.
• OPERATION_CODE, OPERATION_DESCRIPTION, SEQUENCE_NUM, OPERATION_TYPE — identification and ordering attributes.
• ORGANIZATION_ID, DEPARTMENT_ID, DEPARTMENT_CODE, DEPARTMENT_DESCRIPTION, LOCATION_ID — organizational and departmental context.
• OPERATION_YIELD_ENABLED, YIELD, LOWEST_ACCEPTABLE_YIELD — yield control parameters governing scrap tolerance at the operation.
• COUNT_POINT_TYPE with derived COUNT_POINT_FLAG and AUTOCHARGE_FLAG — backflush and charging behavior.
• BACKFLUSH_FLAG, MINIMUM_TRANSFER_QUANTITY, WMS_TASK_TYPE — material movement overrides.
• SHUTDOWN_TYPE and SHUTDOWN_TYPE_VALUE — EAM shutdown classification.
• USE_ORG_SETTINGS, CRITICAL_TO_QUALITY, CHECK_SKILL, and the mandatory flags — quality and scheduling controls.
• *_WHO columns plus ATTRIBUTE1 through ATTRIBUTE15 — audit and descriptive flexfield data.

Common Use Cases and Queries

The view supports yield auditing, department-level operation inventories, and integration extracts. A typical query listing visible yield constraints is:

• SELECT operation_code, department_code, yield, lowest_acceptable_yield FROM bom_standard_operations_v WHERE operation_yield_enabled = 1 AND lowest_acceptable_yield < 100 ORDER BY organization_id, operation_code;
• Retrieving all operations for a department: SELECT standard_operation_id, operation_code, count_point_flag FROM bom_standard_operations_v WHERE department_code = :dept;
• Building extracts for EAM shutdown reporting by filtering on shutdown_type_value.
• Reconciling routings against master templates by joining STANDARD_OPERATION_ID to BOM_OPERATION_SEQUENCES.

Because the object is a view, it should be queried rather than modified; all maintenance is performed through the Bills of Material forms or the base table API.