Search Results gme_batch_step_resources

Overview

GME_BATCH_STEP_RESOURCES is a transactional table in the GME schema, belonging to the Oracle Process Manufacturing (OPM) Process Execution module. It stores the resource-level details associated with each activity performed within a batch step. In OPM terms, a batch step is broken down into one or more activities, and each activity consumes or produces resources—such as equipment, labor, utilities, or time—that are planned and subsequently recorded against the batch. This table captures that per-resource information, making it the most granular operational layer below GME_BATCH_STEP_ACTIVITIES and GME_BATCH_STEPS.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. In practice, however, the table behaves as a satellite attached to the batch step activity hub/link: BATCHSTEP_RESOURCE_ID is the surrogate primary key, and BATCHSTEP_ACTIVITY_ID links each resource row back to its parent activity. When modeling this source in a Data Vault, the resource row would typically be treated as a satellite keyed on the activity, with the resource identifier carried as a descriptive attribute.

Key Information Stored

The table contains 80 documented columns. The most operationally significant include:

• BATCHSTEP_RESOURCE_ID — surrogate primary key (GME_BATCH_STEP_RESOURCES_PK), uniquely identifying each resource line.
• BATCHSTEP_ACTIVITY_ID — foreign key to GME_BATCH_STEP_ACTIVITIES; the parent activity for the resource. This is the primary business-key relationship candidate.
• RESOURCES — the resource identifier or code assigned to the activity.
• BATCHSTEP_ID, BATCH_ID — denormalized pointers to the parent step and batch.
• PLAN_RSRC_COUNT, ACTUAL_RSRC_COUNT — planned versus actual number of resource units consumed.
• PLAN_RSRC_USAGE, ACTUAL_RSRC_USAGE, PLAN_RSRC_QTY, ACTUAL_RSRC_QTY — planned and actual usage and quantity values, with corresponding UOM columns (RESOURCE_QTY_UOM, USAGE_UOM, CAPACITY_UOM).
• PLAN_START_DATE, PLAN_CMPLT_DATE, ACTUAL_START_DATE, ACTUAL_CMPLT_DATE — scheduled and executed timing for the resource.
• MIN_CAPACITY, MAX_CAPACITY, CAPACITY_TOLERANCE — allowable capacity thresholds for the resource assignment.
• COST_CMPNTCLS_ID, CALCULATE_CHARGES — cost component class and charge calculation flag linking resource usage to costing.
• ORGANIZATION_ID — the OPM organization owning the batch and its resource activity.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, CREATION_DATE — standard audit columns present on all OPM transactional tables.

Common Use Cases and Queries

This table supports batch execution reporting, resource consumption analysis, capacity management, and cost roll-up. Typical queries join resources to their parent activity and step to produce a full batch genealogy view:

• Resource consumption vs. plan variance reporting — comparing PLAN_RSRC_QTY and ACTUAL_RSRC_QTY by resource across a batch.
• Capacity bottleneck analysis — reviewing MIN_CAPACITY and MAX_CAPACITY against ACTUAL_RSRC_USAGE to detect over/under-utilization.
• Costing extraction — joining COST_CMPNTCLS_ID to cost component classes to compute resource-driven batch charges.
• Batch schedule adherence — comparing ACTUAL_START_DATE/ACTUAL_CMPLT_DATE with PLAN_START_DATE/PLAN_CMPLT_DATE.

A representative pattern joins this table to its activity parent via BATCHSTEP_ACTIVITY_ID, and filters by BATCH_ID or ORGANIZATION_ID to report resource usage for a specific batch or site.

Related Objects

• GME_BATCH_STEP_ACTIVITIES — parent activity table; joined on BATCHSTEP_ACTIVITY_ID (documented FK).
• GME_BATCH_STEPS — parent step table; joined on BATCHSTEP_ID.
• GME_BATCH_HEADERS — batch master record; joined on BATCH_ID.
• GME_RESOURCES / GME_RESOURCE_BY_PRODUCT — resource master definitions referenced by RESOURCES.
• CM_CMPNTCLS_B — cost component class lookup referenced by COST_CMPNTCLS_ID.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — organizational context via ORGANIZATION_ID.
• GME_BATCH_STEP_RESOURCES_PK — the unique index enforcing the surrogate primary key.

Because the table sits at the leaf of the batch step hierarchy, it is most frequently accessed through the batch step and batch header parents rather than queried in isolation.