Results for “plan_start_date”

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

Overview

GME_BATCH_STEP_RSRC_SUMMARY is a Process Manufacturing Process Execution (GME) table that stores batch step resource usages for Pending and WIP batch steps. In Oracle EBS 12.1.1 and 12.2.2, it functions as a summarization and planning store consumed by the batch step scheduling and resource capacity logic: rather than holding every transactional resource assignment movement, it aggregates planned resource consumption per batch step activity so that the scheduling engine and batch step workbench can evaluate resource loading without traversing the full detail of batch step resource transactions.

The ETRM relationship data classifies this object heuristically as standalone under a Data Vault lens, meaning it does not sit inside a dense foreign-key hierarchy of dependent child tables. The heuristic nevertheless identifies one documented outward reference, BATCHSTEP_ACTIVITY_ID pointing to GME_BATCH_STEP_ACTIVITIES. From a modeling suggestion standpoint, the table behaves most like a satellite: its primary key (BATCHSTEP_RESOURCE_ID) is a surrogate identifier, while the contextual descriptors — batch, batch step, activity, resource, and planned timing and quantity — are the durable attributes that would naturally attach to a parent batch-step-activity key.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

• BATCHSTEP_RESOURCE_ID — the surrogate primary key, defined by the unique index GME_BATCH_STEP_RSRC_SUMMARY_PK. This is the column referenced when a user searches for "batchstep_resource_id" and is the only documented business-key candidate.
• BATCHSTEP_ACTIVITY_ID — the foreign key to GME_BATCH_STEP_ACTIVITIES, anchoring each row to a specific activity within a batch step.
• BATCHSTEP_ID — identifies the parent batch step whose resource usage is being summarized.
• BATCH_ID — identifies the batch, enabling batch-level resource rollups without joining through the step hierarchy.
• RESOURCE_ID — the resource (equipment, labor, or resource instance) whose consumption is planned.
• PLAN_START_DATE and PLAN_CMPLT_DATE — the planned window during which the resource is consumed, driving capacity and scheduling calculations.
• PLAN_RSRC_COUNT — the planned quantity or count of the resource; the principal numeric measure in the summary.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — the standard EBS audit columns.

There is no documented business-key unique index beyond the surrogate primary key, so uniqueness of a (batch step activity, resource) pairing is enforced by application logic rather than by a database constraint.

Common Use Cases and Queries

Typical reporting scenarios include batch step resource loading by planning window, resource capacity utilization across open batches, and reconciliation of summarized plan quantities against actual resource consumption. Because PLAN_START_DATE and PLAN_CMPLT_DATE are stored directly, date-bounded resource capacity reports can be produced without joining to activity detail.

A representative query joining the documented foreign key:

• SELECT r.BATCH_ID, r.BATCHSTEP_ID, r.RESOURCE_ID, r.PLAN_START_DATE, r.PLAN_CMPLT_DATE, r.PLAN_RSRC_COUNT FROM GME.GME_BATCH_STEP_RSRC_SUMMARY r WHERE r.BATCHSTEP_ACTIVITY_ID = :activity_id ORDER BY r.PLAN_START_DATE;
• A resource loading query groups PLAN_RSRC_COUNT by RESOURCE_ID and plan date window for Pending and WIP batch steps only, which is the table's documented scope.
• To trace the activity context, join GME_BATCH_STEP_RSRC_SUMMARY.BATCHSTEP_ACTIVITY_ID = GME_BATCH_STEP_ACTIVITIES.BATCHSTEP_ACTIVITY_ID.

Related Objects

The documented relationships and the batch step object family indicate the following significant related objects:

• GME_BATCH_STEP_ACTIVITIES — referenced by BATCHSTEP_ACTIVITY_ID; the immediate parent activity record.
• GME_BATCH_STEPS — joined via BATCHSTEP_ID to resolve step sequence and step definition.
• GME_BATCH_HEADERS — joined via BATCH_ID for batch-level reporting.
• GME_BATCH_STEP_RESOURCES — the detail resource assignment record that this summary aggregates.
• GME_RESOURCES and GME_RESOURCE_INSTANCES — resolve RESOURCE_ID to resource descriptions and instances.
• GME_BATCH_STEP_ACTIVITIES_PK relationships and the GME batch step workbench/process execution APIs, which insert and update summary rows as batches move from Pending to WIP.