Search Results gme_batch_header




Overview
Explore in AI Chat

Overview

The GME_BATCH_HEADER table is a core data object within the Oracle E-Business Suite Process Manufacturing Process Execution (GME) module. It serves as the primary header table for manufacturing production orders, storing master information for both Firm Planned Orders (FPOs) and actual production Batches. As the central record for a production request, it establishes the foundational link between the planned recipe (formula and routing) and its physical execution, tracking the order's lifecycle from planning through completion across Oracle EBS versions 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key is the BATCH_ID, a unique system-generated identifier for each batch or FPO. Key columns typically include organizational data such as the PLANT_ID (organization), and references to the defining manufacturing master data: FORMULA_ID, ROUTING_ID, and VALIDITY_RULE_ID. It captures critical timing and status information, including planned and actual start and completion dates, BATCH_STATUS, BATCH_CLOSE_DATE, and BATCH_TYPE (distinguishing between a firm planned order and a batch). Additional columns often store control details like the BATCH_NO (user-facing identifier), priority, and reason codes for batch creation or modification.

Common Use Cases and Queries

This table is essential for operational reporting, process traceability, and integration. Common queries involve joining to related detail tables to get a complete view of a production order. For example, to retrieve basic batch header information for a specific organization, a query might be: SELECT batch_no, batch_status, planned_start_date, actual_start_date FROM gme_batch_header WHERE organization_id = :org_id ORDER BY batch_id DESC;. For performance analysis, reports often join GME_BATCH_HEADER to GME_BATCH_STEPS on BATCH_ID to compare planned versus actual step durations. Integration with cost management or inventory typically involves querying this table to establish the production context for material transactions (GME_MATERIAL_DETAILS) and resource charges.

Related Objects

  • GME_BATCH_STEPS: Stores the detailed routing step operations for each batch/FPO, linked via BATCH_ID.
  • GME_MATERIAL_DETAILS: Holds all material components (ingredients, products, by-products) required or produced by the batch, linked via BATCH_ID.
  • GME_TRANSACTION_HISTORY: Records inventory and resource transactions posted against the batch.
  • GME_BATCH_HEADER_V: A common view built upon GME_BATCH_HEADER, often incorporating descriptive flexfield and translation data for reporting.
  • Key APIs: The GME_BATCH_HEADER table is primarily manipulated through public APIs in the GME_API_PUB package for creating, updating, and closing batches programmatically.