Search Results bom_sub_operation_resources_u1




Overview

BOM.BOM_SUB_OPERATION_RESOURCES is an Oracle EBS Bills of Material (BOM) table that stores substitute resources defined for a resource assigned to a routing operation. In discrete and process manufacturing environments, a single operation resource may have one or more alternates that can be used when the primary resource is unavailable, constrained, or more expensive. This table captures those alternates, their usage rates, basis types, scheduling behavior, and shop floor charging attributes. The object resides in the BOM schema, carries the FND design data reference BOM.BOM_SUB_OPERATION_RESOURCES, and is stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10. In ETRM 12.2.2 the table is documented with 44 columns and status VALID.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as standalone. It functions primarily as a detail or satellite-style record keyed to an operation sequence and resource combination, rather than acting as a central hub or a pure link between two independent business keys.

Key Information Stored

The primary key, BOM_SUB_OPERATION_RESOURCES_PK, is composed of OPERATION_SEQUENCE_ID, SUBSTITUTE_GROUP_NUM, and RESOURCE_ID. This surrogate composite identifies each substitute resource line uniquely within the operation context.

A separate unique index, BOM_SUB_OPERATION_RESOURCES_U1, is defined on the column set OPERATION_SEQUENCE_ID, RESOURCE_ID, SUBSTITUTE_GROUP_NUM, REPLACEMENT_GROUP_NUM, BASIS_TYPE, and SCHEDULE_FLAG. This six-column uniqueness constraint represents the strongest documented business-key candidate, distinguishing substitute entries that share the same operation, resource, and group but differ in basis or scheduling characteristics.

The most significant columns include:

Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), concurrent Who columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE15 provide auditing and descriptive flexfield extensibility.

Common Use Cases and Queries

Typical scenarios include identifying all substitute resources for a given operation, comparing usage rates between primary and substitute resources, and enforcing the unique business rule expressed by BOM_SUB_OPERATION_RESOURCES_U1 during data migration or interface loads.

  • Retrieve substitutes by operation: SELECT resource_id, substitute_group_num, usage_rate_or_amount FROM bom_sub_operation_resources WHERE operation_sequence_id = :p_seq;
  • Validate duplicate business keys before loading: query on the U1 column set to detect collisions.
  • Report scheduled substitutes only, filtering schedule_flag = 1.
  • Join to BOM_SETUP_TYPES via SETUP_ID to enrich shop floor charging reports.
  • Audit change control using CHANGE_NOTICE and the concurrent Who columns.

Related Objects

The documented foreign key links SETUP_ID to BOM_SETUP_TYPES. Beyond that, the table is logically associated with the following significant objects:

  • BOM_SETUP_TYPES — joined on SETUP_ID for setup definition.
  • BOM_OPERATION_RESOURCES — the parent resource assignment for the operation; shares the operation and resource context.
  • BOM_OPERATION_SEQUENCES — provides the operation identified by OPERATION_SEQUENCE_ID.
  • BOM_RESOURCES — source of RESOURCE_ID and related resource attributes.
  • BOM_ROUTINGS / BOM_DEPARTMENTS — structural parents of the routing operation.
  • WIP and costing views — consume substitute resource rates and assigned units during shop floor transactions and cost rollups.