Search Results gme_batch_step_items_pk




Overview
Explore in AI Chat

Overview

The GME_BATCH_STEP_ITEMS table resides in the GME schema and forms part of the Process Manufacturing Process Execution module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to define the relationship between batch steps and batch lines. Where a batch step performs consumption, production, or transfer activity against specific material lines, the association is persisted here. A representative case documented in the ETRM metadata is an ingredient consumed during a particular step: if the third ingredient in a batch is consumed in the second step, the linkage is recorded in this table rather than on the batch line itself. This makes GME_BATCH_STEP_ITEMS the junction that binds material activity to the discrete steps of a batch execution, supporting step-level costing, material issue timing, and process scheduling.

From a dimensional modeling perspective, the ETRM heuristic Data Vault classification for this object is standalone, mined from its foreign key structure. That classification should be treated as a suggestion rather than a definitive architectural assignment; the table behaves operationally as an associative or link-style entity joining batch headers, batch steps, and batch material lines.

Key Information Stored

The table carries 43 documented columns, dominated by the standard Oracle attribute flexfield set (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30, with the documented list omitting some numbering). The operationally significant columns are:

  • MATERIAL_DETAIL_ID — the primary key column, enforced by the unique index GME_BATCH_STEP_ITEMS_PK. It is a surrogate identifier for the step-to-line association.
  • BATCH_ID — identifies the batch (batch header) to which this step item belongs.
  • BATCHSTEP_ID — identifies the specific step within the batch that the material line participates in.
  • TEXT_CODE — a code field associated with the step item record, typically used for instruction or step text reference.
  • MAXIMUM_DELAY and MINIMUM_DELAY — delay tolerances applied to the step item, relevant to process timing and step sequencing.
  • MINIMUM_TRANSFER_QTY — the minimum quantity that must be transferred for the step item, used in transfer and yield validation.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the descriptive flexfield segments available for customer-specific extensions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording row provenance.

Only MATERIAL_DETAIL_ID is documented as a unique index and therefore the only explicit business-key candidate. Note that the documented column list does not include a separate batch line identifier beyond BATCH_ID, BATCHSTEP_ID, and MATERIAL_DETAIL_ID, so step-to-line resolution relies on the combination of these keys.

Common Use Cases and Queries

Typical reporting scenarios include determining which material lines are consumed or produced at each step, validating delay and transfer minimums against actual execution, and reconciling batch step activity for costing. A representative query joins step items to their owning batch:

  • Retrieve all step items for a batch: SELECT MATERIAL_DETAIL_ID, BATCH_ID, BATCHSTEP_ID, MINIMUM_TRANSFER_QTY FROM GME.GME_BATCH_STEP_ITEMS WHERE BATCH_ID = :batch_id;
  • Filter by step: ... WHERE BATCHSTEP_ID = :step_id;
  • Detect configured minimums: ... WHERE MINIMUM_TRANSFER_QTY > 0;
  • Audit recent changes: ... WHERE LAST_UPDATE_DATE >= :cutoff_date;

Because the table is classified as standalone with a single-column key, queries are most efficient when driven by BATCH_ID or BATCHSTEP_ID, and reporting models should treat it as a link between batch and step granularity.

Related Objects

The following objects are the most significant related tables and views, joining on the documented key columns:

Additional dependency exists on the GME_BATCH_STEP_ITEMS_PK index and on standard WHO audit lookups. Confirm join cardinality against the current ETRM data model before building production extracts.