Search Results gme_step_status

Overview

GME_BATCH_STEPS_V is a supplementary view owned by the APPS schema within the GME - Process Manufacturing Process Execution product. It is defined over the GME_BATCH_STEPS table and presents batch step (operation-level) execution data in a reporting-ready format. The view joins each batch step to its operation definition in GMD_OPERATIONS and to the GEM_LOOKUPS lookup view to decode the step status into a user-facing meaning. It also invokes several FND utility packages to render date columns in the session server time zone and to translate the terminated indicator into a message string.

The view is intended to serve Oracle EBS reporting and integration needs where consumers require denormalized operation numbers, versions, status descriptions, and display-formatted dates without writing the underlying joins or time zone conversion logic themselves. Because it is a supplementary view, it does not introduce new business logic beyond the join, decode, and format transformations shown in its definition.

Underlying Base Objects

The view is defined over three primary data sources plus several FND utility packages documented in the metadata:

• GME_BATCH_STEPS (synonym) — the base table aliased GBS, supplying batch step quantities, dates, status, priority, charges, mass/volume quantities, and unit-of-measure attributes.
• GMD_OPERATIONS (synonym) — aliased GO, joined on GBS.OPRN_ID = GO.OPRN_ID, supplying OPERATION_NO (OPRN_NO) and OPERATION_VERS (OPRN_VERS).
• GEM_LOOKUPS (view) — aliased LKUP, filtered by LOOKUP_TYPE = 'GME_STEP_STATUS' and joined on GBS.STEP_STATUS = LKUP.LOOKUP_CODE, supplying MEANING as the decoded status text.
• FND_DATE — DATE_TO_DISPLAYDT used to convert each date column to a display date for the server time zone.
• FND_TIMEZONES — GET_SERVER_TIMEZONE_CODE supplies the time zone used in the date conversions.
• FND_MESSAGE — GET_STRING translates the terminated indicator (TERMINATED_IND = 1) into the GME_TERMINATED message text.

Key Columns

• BATCH_ID, BATCHSTEP_ID, ROUTINGSTEP_ID, BATCHSTEP_NO — identify the batch, the specific step, its routing step source, and its sequence number.
• OPRN_ID, OPERATION_NO, OPERATION_VERS — the operation identifier plus its number and version from GMD_OPERATIONS.
• PLAN_STEP_QTY, ACTUAL_STEP_QTY, BACKFLUSH_QTY — the planned and actual step quantities and the backflush quantity; PLAN_STEP_QTY is the column most commonly searched by users.
• PLAN_START_DATE, ACTUAL_START_DATE, DUE_DATE, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE, STEP_CLOSE_DATE — date columns, each exposed both in native form and as a display-formatted value via FND_DATE.
• STEP_STATUS, MEANING — the status code and its decoded lookup meaning.
• PRIORITY_CODE, PRIORITY_VALUE, STEPRELEASE_TYPE, MAX_STEP_CAPACITY, MAX_STEP_CAPACITY_UM — scheduling and capacity attributes.
• PLAN_CHARGES, ACTUAL_CHARGES, PLAN_MASS_QTY, ACTUAL_MASS_QTY, PLAN_VOLUME_QTY, ACTUAL_VOLUME_QTY — charge, mass, and volume quantities for planning and actuals.
• STEP_QTY_UM, MASS_REF_UM, VOLUME_REF_UM, MINIMUM_TRANSFER_QTY, TEXT_CODE, QUALITY_STATUS, DELETE_MARK, TERMINATED_IND, TERMINATED — units of measure, transfer threshold, quality state, and termination indicators.

Common Use Cases and Queries

Typical uses include batch step quantity reporting, operation-level progress tracking, and integration extracts that require decoded statuses and time-zone-adjusted dates. A common query filters or projects PLAN_STEP_QTY, which is the term the user searched for:

• List planned versus actual step quantities for a batch:

  SELECT batch_id, batchstep_no, operation_no,
         plan_step_qty, actual_step_qty, backflush_qty
    FROM apps.gme_batch_steps_v
   WHERE batch_id = :p_batch_id
   ORDER BY batchstep_no;

• Track open step statuses with display dates:

  SELECT batch_id, batchstep_no, meaning,
         plan_step_qty, plan_start_date, due_date
    FROM apps.gme_batch_steps_v
   WHERE step_status NOT IN ('C','X');

• Aggregate plan quantity by operation:

  SELECT operation_no, SUM(plan_step_qty) total_plan_qty
    FROM apps.gme_batch_steps_v
   GROUP BY operation_no;

Because the view performs joins to GMD_OPERATIONS and GEM_LOOKUPS, it is most efficient when filtered by BATCH_ID or BATCHSTEP_ID, ensuring the underlying indexes on GME_BATCH_STEPS are used.