Search Results resource_capacity_uom

Overview

GMD_OPERATION_RESOURCES is a Process Manufacturing Product Development (GMD) table that stores operation resource details within Oracle EBS 12.1.1 and 12.2.2. In the process manufacturing model, an operation defines a step in a routing or recipe, and each operation may consume or require resources such as equipment, labor, or utilities. This table captures the resource-to-operation assignment along with quantitative, capacity, cost, and scheduling attributes needed for both production execution and costing.

Based on the documented foreign key structure, the table can be modeled as hub-leaning in a Data Vault perspective. Its composite primary key (OPRN_LINE_ID, RESOURCES) behaves like a durable business key that is referenced by downstream parameter tables, which is characteristic of a hub or a strongly keyed reference entity rather than a purely descriptive satellite.

Key Information Stored

The table is keyed by GMD_OPERATION_RESOURCES_PK, a composite unique index on OPRN_LINE_ID and RESOURCES. Both columns are business-key candidates. OPRN_LINE_ID identifies the parent operation line, while RESOURCES identifies the specific resource being associated. The documented schema includes 61 columns; the following are the most operationally significant:

• OPRN_LINE_ID — the operation line identifier that links the resource assignment to its parent operation.
• RESOURCES — the resource code or identifier being assigned to the operation.
• RESOURCE_USAGE — the quantity of the resource consumed or required per process quantity.
• RESOURCE_COUNT — the number of resource units involved.
• USAGE_UM and RESOURCE_USAGE_UOM — units of measure governing resource usage.
• PROCESS_QTY and PROCESS_UOM, RESOURCE_PROCESS_UOM — the process basis quantity and its unit of measure.
• PRIM_RSRC_IND — indicates whether this is the primary resource for the operation.
• SCALE_TYPE — how the resource scales with batch size.
• MIN_CAPACITY, MAX_CAPACITY, CAPACITY_UOM, RESOURCE_CAPACITY_UOM — capacity constraints for the resource.
• COST_CMPNTCLS_ID and COST_ANALYSIS_CODE#1 — cost component classification and analysis references.
• OFFSET_INTERVAL — scheduling offset applied to the resource.
• PROCESS_PARAMETER_1 through PROCESS_PARAMETER_5 — flexible process parameter values.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard extensibility (flexfield) columns.
• DELETE_MARK, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit and soft-delete columns.

Common Use Cases and Queries

Typical use cases include resource-load analysis, capacity planning, operation costing, and recipe/routing validation. For example, listing all resources for a given operation line:

• SELECT RESOURCES, RESOURCE_USAGE, USAGE_UM, PRIM_RSRC_IND FROM GMD_OPERATION_RESOURCES WHERE OPRN_LINE_ID = :p_line_id AND NVL(DELETE_MARK,0)=0;
• Identifying primary resources across operations for capacity reporting.
• Joining to parameter tables such as GMD_OPRN_PROCESS_PARAMETERS or GMD_RECIPE_PROCESS_PARAMETERS on (OPRN_LINE_ID, RESOURCES) to correlate resource usage with process parameter values.
• Costing queries that aggregate RESOURCE_USAGE and COST_CMPNTCLS_ID to derive operation cost rollups.

Related Objects

The documented foreign key relationships define the primary dependencies:

• GMD_OPRN_PROCESS_PARAMETERS — references GMD_OPERATION_RESOURCES via OPRN_LINE_ID and RESOURCES.
• GMD_RECIPE_PROCESS_PARAMETERS — also references GMD_OPERATION_RESOURCES via OPRN_LINE_ID and RESOURCES.

These two parameter tables are the most significant dependents, as they extend the resource assignment with process-specific parameter context. Additional joins are typically made to operation and routing/recipe definition tables that own OPRN_LINE_ID, and to resource master tables that own RESOURCES, though those relationships are not enumerated in the supplied ETRM relationship data.