Search Results print_count

Overview

GME_BATCH_HEADER_V1 is an APPS-owned compatibility view in the Oracle E-Business Suite Process Manufacturing (GME) module, specifically within Process Execution. Its stated purpose, per the ETRM 12.2.2 metadata, is to "maintain backward compatibility for other dependent modules," exposing a Batch/FPO header structure. The view has a status of VALID and is documented for both EBS 12.1.1 and 12.2.2. It presents one row per batch header record, covering production identity, scheduling, status, warehouse assignment, control class, and a standard set of descriptive flexfield (DFF) attribute columns. Because it retains a stable column list that predates later structural changes to the underlying batch tables, it serves as a reporting and integration contract for customizations, downstream extracts, and dependent GME or third-party components that were written against the earlier interface. Users searching for "batch_close_date" will find that column exposed directly by this view, making it the conventional surface for querying batch closure information.

Underlying Base Objects

The documented base object for this view is the synonym GME_BATCH_HEADER, which resolves to the APPS.GME_BATCH_HEADER table. The view is a straightforward projection: the view text selects a fixed, ordered list of columns from GME_BATCH_HEADER with no joins, aggregations, or filter predicates. Consequently, row cardinality and granularity match the base table exactly—one row per batch/FPO header—and no data transformation occurs beyond column mapping. Notably, the view text maps two positions to literal NULL and a base column rather than exposing the underlying names verbatim: the eighteenth select position returns NULL for what the column list documents as IN_USE, and the nineteenth position returns RECIPE_VALIDITY_RULE_ID for the column documented as FMEFF_ID. Similarly, the column list labels one date column EXPCT_CMPLT_DATE while the view text selects PLAN_CMPLT_DATE, indicating a historical rename preserved through the view layer. These inconsistencies are characteristic of a backward-compatibility shim and should be accounted for when interpreting results.

Key Columns

• BATCH_ID — primary identifier of the batch/FPO header; the recommended join key to other GME tables.
• BATCH_NO and PLANT_CODE — the user-visible batch number and the plant in which it is executed.
• BATCH_TYPE and BATCH_STATUS — classification of the batch and its current lifecycle state (for example, pending, released, or closed).
• PROD_ID and FORMULA_ID / ROUTING_ID — the produced item and the associated formula and routing definitions.
• PLAN_START_DATE, ACTUAL_START_DATE, DUE_DATE, EXPCT_CMPLT_DATE (sourced from PLAN_CMPLT_DATE), ACTUAL_CMPLT_DATE — planned versus actual scheduling and completion dates.
• BATCH_CLOSE_DATE — the date and time the batch was closed; the primary column relevant to closure-oriented reporting.
• FMCONTROL_CLASS and WIP_WHSE_CODE — quality control class and the WIP warehouse associated with the batch.
• IN_USE and FMEFF_ID — documented in the column list but not populated from named base columns (NULL and RECIPE_VALIDITY_RULE_ID respectively).
• DELETE_MARK — soft-delete indicator; a value of 1 marks logically deleted records.
• ATTRIBUTE1–ATTRIBUTE30, ATTRIBUTE_CATEGORY, TEXT_CODE — descriptive flexfield and text reference columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include batch closure reporting, plant-level batch status dashboards, and integrations that must remain compatible with legacy GME interfaces. A common requirement is listing batches closed within a period:

• SELECT batch_id, batch_no, plant_code, batch_status, batch_close_date FROM apps.gme_batch_header_v1 WHERE batch_close_date BETWEEN :from_date AND :to_date AND NVL(delete_mark,0) = 0 ORDER BY batch_close_date;
• Open batch analysis: SELECT batch_no, plant_code, batch_status, plan_cmplt_date FROM apps.gme_batch_header_v1 WHERE actual_cmplt_date IS NULL AND NVL(delete_mark,0) = 0;
• Plant/batch lookup for joins: SELECT batch_id, batch_no, prod_id, formula_id FROM apps.gme_batch_header_v1 WHERE plant_code = :plant_code AND batch_no = :batch_no;

Because the view performs no filtering, callers should always apply their own DELETE_MARK and date predicates. Where attributes 1–30 are surfaced, note that the view text selects columns through ATTRIBUTE30 plus ATTRIBUTE_CATEGORY, matching the documented list.