Results for “actual_cost_ind”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GME_BATCH_HEADER is the primary header table within the Oracle Process Manufacturing (OPM) Process Execution module, owned by the GME schema. It stores header-level information for both Firm Planned Orders (FPOs) and Batches, capturing the plant location, the validity rules applied, and the formula and routing upon which each batch is based, together with planned and actual start and completion dates. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the central transactional anchor for batch execution, batch costing, inventory consumption, and shop-floor reporting.

From a Data Vault modeling perspective, the ETRM metadata classifies GME_BATCH_HEADER heuristically as standalone. This suggests the table behaves primarily as a hub-and-satellite source rather than a link: BATCH_ID serves as a durable business key, while the descriptive columns (status, dates, flags) act as satellite attributes. The only documented foreign key is RECIPE_VALIDITY_RULE_ID referencing GMD_RECIPE_VALIDITY_RULES, indicating that most relationships to other GME entities are enforced logically or through views rather than declaratively.

Key Information Stored

The documented physical schema contains 89 columns in the 12.2.2 ETRM model. The surrogate primary key is BATCH_ID, enforced by the GME_BATCH_HEADER_PK unique index; BATCH_ID is the sole business-key candidate documented.

• BATCH_ID — surrogate primary key uniquely identifying each batch or FPO.
• BATCH_NO — user-facing batch number used in shop-floor and inventory transactions.
• PLANT_CODE / ORGANIZATION_ID — the manufacturing plant or inventory organization context.
• PROD_ID / PROD_SEQUENCE — the product produced and its sequence within co-product output.
• FORMULA_ID / ROUTING_ID — the formula and routing master versions used to generate the batch.
• RECIPE_VALIDITY_RULE_ID — the validity rule governing formula/routing selection; the sole documented FK to GMD_RECIPE_VALIDITY_RULES.
• BATCH_TYPE / BATCH_STATUS — classification and lifecycle state (e.g., released, WIP, closed).
• PLAN_START_DATE / ACTUAL_START_DATE / DUE_DATE / PLAN_CMPLT_DATE / ACTUAL_CMPLT_DATE — the scheduling and execution timeline.
• BATCH_CLOSE_DATE / BATCH_CLOSE_DATE indicators — batch closure and GL posting flags (GL_POSTED_IND, ACTUAL_COST_IND).
• FIRMED_IND / FINITE_SCHEDULED_IND — scheduling firmness for FPOs.
• FPO_ID / PARENTLINE_ID — linkage to parent FPO and line relationships.
• WIP_WHSE_CODE — the work-in-process warehouse for material staging.
• DELETE_MARK — logical deletion flag used across OPM tables.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–40 — the standard EBS descriptive flexfield segments.
• LAST_UPDATE_DATE / CREATED_BY / LAST_UPDATED_BY — the standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include batch status reporting, production throughput analysis, WIP valuation, and integration extracts for MES or data-warehouse consumers. A common query retrieves all open batches for a plant:

• SELECT batch_id, batch_no, prod_id, batch_status, plan_start_date, actual_start_date FROM gme_batch_header WHERE plant_code = :plant AND batch_status <> 'CLOSED' AND delete_mark = 0;
• Joining to GMD_RECIPE_VALIDITY_RULES on RECIPE_VALIDITY_RULE_ID to confirm the rule version applied.
• Aggregating actual versus planned completion variance for OEE and schedule adherence metrics.
• Filtering on FIRMED_IND or FINITE_SCHEDULED_IND to isolate FPOs for planning reports.
• Querying GL_POSTED_IND to identify batches awaiting cost and GL posting.

Related Objects

The following objects are most significant in relation to GME_BATCH_HEADER:

• GMD_RECIPE_VALIDITY_RULES — referenced by RECIPE_VALIDITY_RULE_ID; defines the validity rule controlling formula and routing selection.
• GME_BATCH_STEPS — batch step detail keyed by BATCH_ID.
• GME_BATCH_MATERIALS — material consumption lines for the batch.
• GME_BATCH_HEADER_PK — the primary key constraint enforcing uniqueness on BATCH_ID.
• GMD_FORMULA_HEADERS — source master for FORMULA_ID.
• GMD_ROUTINGS_HEADERS — source master for ROUTING_ID.
• GME_PROCESS_EXECUTION views — packaged views that expose batch header data to OPM cost and inventory processes.