Search Results gme_batch_header_vw




Overview
Explore in AI Chat

Overview

GME_BATCH_HEADER_VW is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the GME (Process Manufacturing Process Execution) product family. It exposes batch header information from the Process Manufacturing execution model in a denormalized, user-friendly form suitable for concurrent programs, Oracle Reports, OAF pages, and custom SQL-based integrations. The view consolidates the core batch record with descriptive attributes pulled from lookup tables, formula and routing masters, and recipe definitions. A distinguishing feature is that it presents both raw date columns and formatted display dates generated through calls to FND_DATE.DATE_TO_DISPLAYDT, allowing reporting layers to render dates in the session-appropriate format without client-side conversion logic. The view is documented as VALID in ETRM 12.2.2 metadata, and is equally applicable in 12.1.1 environments, where the same column set and underlying objects are present.

Underlying Base Objects

The view is defined over a set of synonyms that ultimately resolve to Process Manufacturing and Oracle Inventory base tables, together with two public packages. The primary driving table is GME_BATCH_HEADER, aliased B, which supplies the batch identity, status, scheduling, cost, and DFF attribute columns. MTL_PARAMETERS (aliased MP) supplies ORGANIZATION_CODE, exposed twice as PLANT_CODE and ORGANIZATION_CODE. FND_LOOKUP_VALUES (aliased FLV1) supplies BATCH_STATUS_DESC through the BATCH_STATUS lookup. FM_FORM_MST (aliased F) contributes formula number, version and description; FM_ROUT_HDR (aliased R) contributes routing number, version and description; and GMD_RECIPES (aliased REC) together with GMD_RECIPE_VALIDITY_RULES link the batch to its governing recipe and validity rule. The FND_DATE package is invoked for display-date conversion, while FND_MESSAGE and MTL_TRANSACTION_REASONS appear as documented referenced objects supporting message and reason resolution paths.

Key Columns

Notably, the view does not expose a column named MOVE_ORDER_HEADER_ID. Users searching for that identifier must query the move-order tables (for example GME_MOVE_ORDER_HEADERS) and join back to this view through BATCH_ID.

Common Use Cases and Queries

The view is typically used for batch status dashboards, shop-floor reporting, and integration extracts where decoded status and display-formatted dates are required. A representative query lists in-process batches by plant:

SELECT batch_no, plant_code, batch_status_desc, plan_start_date_dt
FROM   apps.gme_batch_header_vw
WHERE  batch_status = 3
AND    plant_code = :p_plant;

A second pattern joins the view to move-order or material-line tables on BATCH_ID to obtain batch context for a specific move order header, satisfying the common requirement to locate the batch behind a given move_order_header_id without a direct column on this view. Because the view joins multiple master tables, queries should be filtered on indexed columns such as BATCH_ID or BATCH_NO to avoid unnecessary full scans.