Search Results operation_no




Overview
Explore in AI Chat

Overview

APPS.GME_BATCH_STEP_ACTIVITIES_V is a reporting and inquiry view within the Oracle E-Business Suite Process Manufacturing (OPM/GME) schema. It exposes batch step activity records—the individual activities executed as part of a batch step—joined with their parent batch step attributes and the descriptive text of the associated activity. The view presents both the raw date columns and timezone-converted display variants, which allows Forms, OAF pages, and concurrent programs to render dates consistently against the server timezone.

The view belongs to the family of GME_BATCH_STEP_* objects and is frequently used in batch execution, work-in-process (WIP), and shop-floor reporting where the sequence of activities performed at each operation must be reconstructed. Because it is a view, it imposes no additional storage and inherits the transactional behavior of the underlying base table. The operation_vers column, surfaced from GME_BATCH_STEPS_V, makes this view particularly relevant when activity records must be correlated to a specific routing operation and version combination.

Underlying Base Objects

The view is defined over three source objects joined on common keys, plus supporting packages:

The join conditions are: GBSA.BATCHSTEP_ID = GBS.BATCHSTEP_ID and FAM.ACTIVITY = GBSA.ACTIVITY.

Key Columns

Common Use Cases and Queries

Typical scenarios include shop-floor dashboards showing activities per operation version, variance analysis between planned and actual activity dates, and integration extracts correlating batch activities to operation lines.

  • List activities for a batch, including operation version: 
    SELECT batch_id, batchstep_no, operation_no, operation_vers,
       activity, activity_desc, actual_start_date, actual_cmplt_date
FROM   apps.gme_batch_step_activities_v
WHERE  batch_id = :p_batch_id
ORDER  BY batchstep_no, activity;
  • Find activities for a specific operation and version: 
    SELECT batch_id, batchstep_activity_id, activity, plan_activity_factor
FROM   apps.gme_batch_step_activities_v
WHERE  operation_no = :p_opno AND operation_vers = :p_vers;
  • Compare planned versus actual completion: 
    SELECT batch_id, activity, plan_cmplt_date, actual_cmplt_date
FROM   apps.gme_batch_step_activities_v
WHERE  actual_cmplt_date > plan_cmplt_date;

Because DELETE_MARK is exposed, queries should typically filter NVL(delete_mark,0)=0 to exclude logically deleted activity rows.