Search Results gme_batch_step_items_v1

Overview

GME_BATCH_STEP_ITEMS_V1 is an APPS-owned reporting view within the Oracle E-Business Suite Process Manufacturing (GME) module, specifically the Process Execution product area. The view presents the association between batch step items and material definitions, exposing a single denormalized record for each linkage between a batch step and the material details that apply to that step. In ETRM 12.1.1 and 12.2.2 the object carries a VALID status and is catalogued under the Process Manufacturing Process Execution product family.

Because batch steps and their associated material requirements are physically distributed across two base objects, the view serves as the standard join point for operational reporting, integration extracts, and custom concurrent programs that need to read step-level material quantities, yield contributions, and scaling attributes without reconstructing the underlying join. The name suffix "_V1" indicates this is the first released version of the view in the ETRM data model.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as SYNONYMs resolved through the APPS schema:

• GME_BATCH_STEP_ITEMS — supplies the batch step association, principally BATCHSTEP_ID, and the batch identifier used for correlation.
• GME_MATERIAL_DETAILS — supplies the material definition rows, including quantities, units of measure, scaling attributes, cost allocation, phantom handling, and the descriptive flexfield ATTRIBUTE1 through ATTRIBUTE30 columns.

The view text joins the two sources on BATCH_ID and MATERIAL_DETAIL_ID, so each row represents one material detail line as it applies to a specific batch step. All columns are projected from GME_MATERIAL_DETAILS except BATCHSTEP_ID, which originates in GME_BATCH_STEP_ITEMS; BATCH_ID and MATERIAL_DETAIL_ID are carried from both sides of the join and remain available for further correlation.

Key Columns

• BATCHSTEP_ID — identifier of the batch step to which the material detail applies; the principal key supplied by GME_BATCH_STEP_ITEMS.
• MATERIAL_DETAIL_ID, BATCH_ID, FORMULALINE_ID, LINE_NO — identifiers linking the row to the material detail, the batch, the originating formula line, and the line sequence.
• ITEM_ID, LINE_TYPE, ITEM_UM, ITEM_UM2 — the item consumed or produced, its line classification, and primary/secondary units of measure.
• PLAN_QTY, ACTUAL_QTY, WIP_PLAN_QTY, ORIGINAL_QTY — planned, actual, WIP-planned, and original quantities for the material line.
• CONTRIBUTE_YIELD_IND, CONTRIBUTE_STEP_QTY_IND — the indicator the user searched for, CONTRIBUTE_YIELD_IND, determines whether the material line contributes to the yield calculation of the batch step. CONTRIBUTE_STEP_QTY_IND controls whether the line contributes to the step quantity.
• SCALE_TYPE, SCALE_MULTIPLE, SCALE_ROUNDING_VARIANCE, ROUNDING_DIRECTION — scaling behaviour applied when the batch quantity differs from the formula quantity.
• SCRAP_FACTOR, COST_ALLOC, ALLOC_IND, COST, PHANTOM_TYPE, PHANTOM_ID, RELEASE_TYPE, TEXT_CODE — scrap, cost allocation, phantom, release, and note attributes.
• Audit and flexfield columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE30.

Common Use Cases and Queries

Typical usage includes batch yield analysis, step-level material availability reports, integration extracts feeding MES or shop-floor systems, and reconciliation of planned versus actual material consumption. Because CONTRIBUTE_YIELD_IND sits on the step-item association, the view is the natural source for identifying which lines are included in yield roll-ups.

SELECT batchstep_id,
       batch_id,
       item_id,
       line_no,
       plan_qty,
       actual_qty,
       contribute_yield_ind
FROM   apps.gme_batch_step_items_v1
WHERE  batch_id = :p_batch_id
AND    contribute_yield_ind = 'Y'
ORDER  BY line_no;

A second common pattern aggregates yield-contributing quantities by item across a batch for variance reporting:

SELECT item_id,
       item_um,
       SUM(plan_qty)   plan_total,
       SUM(actual_qty) actual_total
FROM   apps.gme_batch_step_items_v1
WHERE  batch_id = :p_batch_id
AND    contribute_yield_ind = 'Y'
GROUP  BY item_id, item_um;

Reports that must distinguish yield-affecting lines from purely informational step items filter directly on CONTRIBUTE_YIELD_IND, while cost-related extracts join ITEM_ID to the item master and use COST_ALLOC and ALLOC_IND to resolve allocation treatment.