Search Results gme_batch_step_activities_v

Overview

The GME_BATCH_STEP_ACTIVITIES_V view belongs to the GME - Process Manufacturing Process Execution product family within Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). It is a supplementary reporting view built on top of the GME_BATCH_STEP_ACTIVITIES base table, exposing batch step activity records together with descriptive context drawn from batch step and activity definition sources. Its principal analytical purpose is to present planned and actual timing information for each activity executed within a batch step, while also surfacing the server-timezone display conversions of those dates for user-facing reporting. The view is owned by the APPS schema and carries a VALID status. Because it joins batch step activities to batch step headers and activity descriptions, it is well suited to reporting scenarios that require batch execution detail at the activity level rather than only at the batch or operation level. This is particularly relevant to users searching for the OFFSET_INTERVAL column, which captures the relative scheduling offset applied to an activity within its batch step.

Underlying Base Objects

The view is defined by joining three primary sources: GME_BATCH_STEP_ACTIVITIES (accessed through a synonym), GME_BATCH_STEPS_V, and GMD_ACTIVITIES_VL. The join conditions bind GBSA.BATCHSTEP_ID to GBS.BATCHSTEP_ID, and GBSA.ACTIVITY to FAM.ACTIVITY, ensuring each activity row is enriched with its parent batch step number, operation number, operation version, and a translated activity description. The date columns are passed through the FND_DATE.DATE_TO_DISPLAYDT function, using FND_TIMEZONES.GET_SERVER_TIMEZONE_CODE to convert stored dates into display-ready values. Supporting package references include FND_DATE, FND_MESSAGE, and FND_TIMEZONES.

Key Columns

• BATCH_ID, BATCHSTEP_ID, BATCHSTEP_ACTIVITY_ID - Identifiers linking the activity to its batch, batch step, and unique activity instance.
• ACTIVITY - The activity code, joined to GMD_ACTIVITIES_VL for its description.
• OFFSET_INTERVAL - The scheduling offset interval for the activity within the batch step.
• OPRN_LINE_ID, OPERATION_NO, OPERATION_VERS - Routing/operation context for the step.
• PLAN_START_DATE, ACTUAL_START_DATE, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE - Raw planned and actual activity timing.
• PLAN_START_DATE_DT, ACTUAL_START_DATE_DT, PLAN_CMPLT_DATE_DT, ACTUAL_CMPLT_DATE_DT - Server-timezone display conversions of the four dates above.
• PLAN_ACTIVITY_FACTOR, ACTUAL_ACTIVITY_FACTOR - Planned versus actual activity scaling factors.
• SEQUENCE_DEPENDENT_IND, MAX_BREAK, BREAK_IND, MATERIAL_IND - Control flags governing activity behavior.
• TEXT_CODE, DELETE_MARK - Standard descriptive and logical-delete indicators.
• BATCHSTEP_NO, ACTIVITY_DESC - Human-readable step number and activity description.

Common Use Cases and Queries

Typical usage centers on batch activity schedule analysis, variance reporting between planned and actual activity dates, and operational dashboards. A representative query selecting activity scheduling detail follows:

SELECT batch_id, batchstep_no, activity, activity_desc,
       operation_no, offset_interval,
       plan_start_date_dt, actual_start_date_dt,
       plan_cmplt_date_dt, actual_cmplt_date_dt,
       plan_activity_factor, actual_activity_factor
FROM   apps.gme_batch_step_activities_v
WHERE  batch_id = :batch_id
AND    NVL(delete_mark, 0) = 0
ORDER  BY batchstep_no, sequence_dependent_ind;

Planners use OFFSET_INTERVAL to evaluate how activities are staggered within steps, while variance analysis compares planned against actual factors and dates to identify schedule slippage. Reports should generally filter DELETE_MARK and prefer the _DT display columns when presenting dates to end users.