Results for “step_qty_uom”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GME_BATCH_STEPS is a core table in the Oracle EBS Process Manufacturing Process Execution (GME) module. It stores one row for every step (operation) that belongs to a process manufacturing batch. A batch typically represents a production run governed by a routing, and each routing operation is instantiated as a batch step. This table therefore records the operational state of each step, including its planned and actual quantities, scheduling dates, and status transitions through release, execution, and close-out.

The object is owned by the GME schema and is classified as VALID in the ETRM documentation. It is physically implemented as a table with 74 documented columns in ETRM 12.2.2, and the structure is consistent across 12.1.1 and 12.2.2. Under a heuristic Data Vault classification derived from its foreign key structure, GME_BATCH_STEPS models as a standalone object rather than a classic hub, link, or satellite. In practice it behaves as a detail-level entity anchored to the batch header, with its routing-step reference serving as a link back to the routing definition.

Key Information Stored

The surrogate primary key is BATCHSTEP_ID, enforced by the GME_BATCH_STEPS_PK index. A secondary unique index, GME_BATCH_STEPS_U1, enforces the business-key combination of BATCH_ID and BATCHSTEP_NO, guaranteeing that step numbers are unique within a batch. The most operationally significant columns are:

• BATCH_ID — the parent batch to which the step belongs.
• BATCHSTEP_NO — the step sequence number within the batch.
• ROUTINGSTEP_ID — reference to the routing detail (FM_ROUT_DTL) that defines the step.
• OPRN_ID — the operation identifier associated with the step.
• STEP_STATUS — the current lifecycle state of the step.
• PLAN_START_DATE, ACTUAL_START_DATE, DUE_DATE, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE, STEP_CLOSE_DATE — the scheduling and execution timeline.
• PLAN_STEP_QTY, ACTUAL_STEP_QTY, STEP_QTY_UOM (or STEP_QTY_UM) — planned versus actual step quantities and their unit of measure.
• BACKFLUSH_QTY — quantity consumed through backflush processing.
• PRIORITY_CODE and PRIORITY_VALUE — scheduling and sequencing priority.
• QUALITY_STATUS — quality disposition of the step.
• TERMINATED_IND — flag indicating a step terminated before normal completion.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the ATTRIBUTE1–ATTRIBUTE30 flexfield columns.

Common Use Cases and Queries

GME_BATCH_STEPS is commonly queried for shop-floor reporting, batch status monitoring, and variance analysis between planned and actual execution. A typical query retrieves all active steps for a batch:

• SELECT BATCHSTEP_NO, OPRN_ID, STEP_STATUS, PLAN_START_DATE, ACTUAL_START_DATE, ACTUAL_CMPLT_DATE FROM GME_BATCH_STEPS WHERE BATCH_ID = :p_batch_id ORDER BY BATCHSTEP_NO;
• Reporting on steps not yet closed: filter where STEP_STATUS indicates open and ACTUAL_CMPLT_DATE IS NULL.
• Quantity variance analysis comparing PLAN_STEP_QTY against ACTUAL_STEP_QTY and BACKFLUSH_QTY.
• Exception reporting on TERMINATED_IND = 'Y' or failing QUALITY_STATUS.

Related Objects

The primary documented relationship is ROUTINGSTEP_ID referencing FM_ROUT_DTL, linking each batch step to its routing definition. GME_BATCH_STEPS also relates by BATCH_ID to the batch header table GME_BATCH_HEADER, which is the natural parent in the batch hierarchy. Downstream, step-level transactions and material movements (such as GME_BATCH_STEP_ITEMS and related consumption tables) depend on BATCHSTEP_ID. Reporting views in the GME schema frequently join GME_BATCH_STEPS to GME_BATCH_HEADER and FM_ROUT_DTL to present planned versus actual step performance in a single result set.