Search Results gme_batch_step_activities

Overview

GME_BATCH_STEP_ACTIVITIES is a Process Manufacturing Process Execution (GME) table that stores the activity-level details of a batch operation (step). In Oracle EBS 12.1.1 and 12.2.2, a batch is decomposed into steps (operations), and each step is further decomposed into one or more activities. This table captures the granular execution data for each activity within a batch step, including scheduling, actual performance, and activity factors. It is a core transactional table used by the process execution engine, batch scheduling, and downstream reporting on batch performance.

The ETRM heuristic Data Vault classification for this object is standalone, mined from its foreign key structure. From a modeling perspective, this suggests the table behaves as an independent entity rather than a pure hub, link, or satellite. Its strongest hub-like candidate key is BATCHSTEP_ACTIVITY_ID, while its relationship to parent batch and step records implies link-like semantics. The classification should be treated as a modeling suggestion, not a rigid constraint.

Key Information Stored

The table is documented with 54 columns. The most significant are:

• BATCHSTEP_ACTIVITY_ID — surrogate primary key, defined by the unique index GME_BATCH_STEP_ACTIVITIES_PK. This is the business-key candidate for the activity record.
• BATCH_ID — identifies the parent batch.
• BATCHSTEP_ID — identifies the parent batch step (operation) to which the activity belongs.
• ACTIVITY — the activity identifier or code within the step.
• OPRN_LINE_ID — reference to the operation line associated with the activity.
• PLAN_START_DATE / ACTUAL_START_DATE — planned versus actual start timestamps for the activity.
• PLAN_CMPLT_DATE / ACTUAL_CMPLT_DATE — planned versus actual completion timestamps.
• PLAN_ACTIVITY_FACTOR / ACTUAL_ACTIVITY_FACTOR — planned and actual scaling or activity factors used in process calculations.
• OFFSET_INTERVAL — interval offset used for scheduling the activity relative to its step.
• DELETE_MARK — soft-delete indicator.
• SEQUENCE_DEPENDENT_IND, MAX_BREAK, BREAK_IND, MATERIAL_IND — control flags governing sequencing, break logic, and material handling for the activity.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard Oracle EBS descriptive flexfield (DFF) columns for user-defined attributes.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present for audit purposes.

Common Use Cases and Queries

Typical uses include batch execution tracking, planned-versus-actual variance reporting, and activity-level resource or parameter analysis.

• Retrieve all activities for a given batch step:
  SELECT BATCHSTEP_ACTIVITY_ID, ACTIVITY, PLAN_START_DATE, ACTUAL_START_DATE, ACTUAL_CMPLT_DATE FROM GME.GME_BATCH_STEP_ACTIVITIES WHERE BATCHSTEP_ID = :p_step_id AND NVL(DELETE_MARK,0) = 0 ORDER BY ACTIVITY;
• Compare planned and actual timing across a batch:
  SELECT BATCH_ID, BATCHSTEP_ID, ACTIVITY, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE FROM GME.GME_BATCH_STEP_ACTIVITIES WHERE BATCH_ID = :p_batch_id;
• Join to resources and parameters for cost or yield analysis, using BATCHSTEP_ACTIVITY_ID as the join key.

Reports often combine this table with batch and step headers to produce execution timelines, and with migration tables during data conversion projects.

Related Objects

The following objects reference GME_BATCH_STEP_ACTIVITIES via the BATCHSTEP_ACTIVITY_ID foreign key:

• GME_PROCESS_PARAMETERS and GME_PROCESS_PARAMETERS_MIG — process parameter values captured for each activity.
• GME_BATCH_STEP_RESOURCES and GME_BATCH_STEP_RESOURCES_MIG — resources consumed or produced at the activity level.
• GME_BATCH_STEP_RSRC_SUMMARY — summarized resource usage per activity.
• GME_BATCH_STEP_ACTIV_MIG — migration staging counterpart for activities.

These relationships make the table a central join point for activity-level execution, parameter, and resource data in Process Manufacturing.