Search Results gme_step_status

Overview

APPS.GME_BATCH_STEPS_V is a reporting and inquiry view within the Oracle E-Business Suite Process Manufacturing (OPM/GME) module. It presents batch step information—the individual routing operations executed against a production batch—in a form suited for concurrent program output, OAF pages, and ad hoc query tools. The view is a denormalized projection of the GME_BATCH_STEPS base table, joined to operation master data and to the GME_STEP_STATUS lookup, and it performs server-timezone conversion of every date column so that report consumers see display-ready values rather than raw database timestamps.

Its principal practical value is the resolution of two coded values. First, GBS.STEP_STATUS is decoded through GEM_LOOKUPS against the lookup type 'GME_STEP_STATUS' to return lkup.meaning, which is the user-facing description of the step's lifecycle state (for example pending, released, in process, or complete). Second, GBS.TERMINATED_IND is decoded through FND_MESSAGE into a translatable message string. These two decodes are the reason the view is frequently preferred over the base table when a user searches on "gme_step_status" or requires a readable status description without joining the lookup table manually.

Underlying Base Objects

The view is defined over the following documented objects:

• GME_BATCH_STEPS — aliased GBS. The primary driving table, holding one row per batch step with quantities, dates, capacity, charges, and status codes.
• GMD_OPERATIONS — aliased GO. Joined on GBS.OPRN_ID = GO.OPRN_ID, supplying OPRN_NO (rendered as OPERATION_NO) and OPRN_VERS (rendered as OPERATION_VERS).
• GEM_LOOKUPS — aliased lkup. Joined on lookup_type = 'GME_STEP_STATUS' and GBS.STEP_STATUS = lkup.LOOKUP_CODE, supplying the MEANING column.
• FND_DATE — package used via DATE_TO_DISPLAYDT to convert each date to the display timezone.
• FND_TIMEZONES — package supplying GET_SERVER_TIMEZONE_CODE as the conversion source.
• FND_MESSAGE — package supplying the GME_TERMINATED message string.

Because the lookup join is an inner join on a fixed lookup type, a batch step whose STEP_STATUS does not have a corresponding GEM_LOOKUPS row under 'GME_STEP_STATUS' will not appear in the view. This is worth noting when reconciling row counts against GME_BATCH_STEPS.

Key Columns

• BATCH_ID, BATCHSTEP_ID, ROUTINGSTEP_ID, BATCHSTEP_NO — the batch identity, the unique step identifier, its routing origin, and the step sequence within the batch.
• OPRN_ID, OPERATION_NO, OPERATION_VERS — the operation executed at this step, with version.
• PLAN_STEP_QTY, ACTUAL_STEP_QTY, BACKFLUSH_QTY — planned, actual, and backflushed quantities for the step.
• PLAN_START_DATE, ACTUAL_START_DATE, DUE_DATE, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE, STEP_CLOSE_DATE — the scheduling and execution dates. Each is paired with a timezone-converted display value.
• STEP_STATUS and MEANING — the raw status code and its decoded description from the GME_STEP_STATUS lookup.
• PRIORITY_CODE, PRIORITY_VALUE, STEPRELEASE_TYPE — scheduling priority and release characteristics.
• MAX_STEP_CAPACITY, MAX_STEP_CAPACITY_UM — capacity limit and its unit of measure.
• PLAN_CHARGES, ACTUAL_CHARGES — planned and actual step charges.
• PLAN_MASS_QTY, ACTUAL_MASS_QTY, PLAN_VOLUME_QTY, ACTUAL_VOLUME_QTY with MASS_REF_UM and VOLUME_REF_UM — mass and volume measures with reference units.
• STEP_QTY_UM, MINIMUM_TRANSFER_QTY, QUALITY_STATUS, DELETE_MARK, TERMINATED_IND, TERMINATED, TEXT_CODE — unit of measure, transfer threshold, quality disposition, logical delete flag, termination flag and its decoded message.

Common Use Cases and Queries

Typical uses include batch step status reporting, shop-floor work-in-process inquiries, capacity utilization analysis, and feeds into manufacturing execution or quality systems. The following query lists open steps for a batch with readable status:

• SELECT batch_id, batchstep_no, operation_no, meaning, plan_start_date, actual_start_date, plan_step_qty, actual_step_qty
• FROM apps.gme_batch_steps_v
• WHERE batch_id = :p_batch_id
• AND delete_mark = 0
• ORDER BY batchstep_no;

To aggregate step status counts across batches for a period, group on MEANING and restrict on PLAN_START_DATE. To find terminated steps, filter on TERMINATED_IND = 1. Always constrain on BATCH_ID or a date range, since the view is not partitioned and joins three objects. When exact row parity with the base table is required, query GME_BATCH_STEPS directly, as the inner lookup join can exclude orphaned status codes.