Results for “enhanced_pi_ind”

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

Overview

GME_BATCH_HEADER_MIG is a table in the GME schema belonging to the Oracle Process Manufacturing Process Execution (OPM PE) module. It appears in both Oracle EBS 12.1.1 and 12.2.2 and stores staging and migration-related batch header records used when process batches are converted, migrated, or transferred between systems, organizations, or legacy data structures. Unlike the operational GME_BATCH_HEADER table that drives live production execution, GME_BATCH_HEADER_MIG serves as a migration-oriented counterpart that preserves batch header information together with flags indicating whether a record has been migrated. It carries an extensive set of descriptive and control columns, including the full ATTRIBUTE1 through ATTRIBUTE40 flexfield set, which is characteristic of OPM migration and interface tables.

From a Data Vault modeling perspective, the documented FK relationship (RECIPE_VALIDITY_RULE_ID referencing GMD_RECIPE_VALIDITY_RULES) and the unique index GME_BATCH_HEADER_MIG_N1 on (BATCH_ID, MIGRATED_BATCH_IND) suggest this table behaves primarily as a satellite attached to a batch hub keyed by BATCH_ID, with MIGRATED_BATCH_IND acting as a status or driving-key discriminator. Because the mined classification is standalone, the table is best treated as a self-contained staging satellite rather than a shared hub or link.

Key Information Stored

The most significant columns capture batch identity, product, source recipe/routing, dates, and status:

• BATCH_ID — surrogate/operational key identifying the batch; part of the unique index GME_BATCH_HEADER_MIG_N1.
• MIGRATED_BATCH_IND — migration flag; the second component of the unique index, distinguishing migrated versus non-migrated batch header rows.
• BATCH_NO — user-facing batch number.
• BATCH_TYPE — classification of the batch (e.g., production, planning).
• PROD_ID / PROD_SEQUENCE — the product produced and its sequence.
• ORGANIZATION_ID / PLANT_CODE — the owning organization and plant.
• FORMULA_ID / ROUTING_ID / RECIPE_VALIDITY_RULE_ID — the formulation, routing, and recipe validity rule (FK to GMD_RECIPE_VALIDITY_RULES) governing the batch.
• PLAN_START_DATE / ACTUAL_START_DATE / DUE_DATE / PLAN_CMPLT_DATE / ACTUAL_CMPLT_DATE — planned and actual execution dates.
• BATCH_STATUS / BATCH_CLOSE_DATE — current status and close date of the batch.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE40 — the OPM descriptive flexfield columns used to carry customer-specific migration data.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, DELETE_MARK) are also present.

Common Use Cases and Queries

Typical usage involves identifying which batches have been migrated, validating migration completeness, and reconciling migrated headers against the live batch table. Representative patterns include:

• Listing migrated batches for an organization: SELECT BATCH_NO, PROD_ID, BATCH_STATUS FROM GME_BATCH_HEADER_MIG WHERE ORGANIZATION_ID = :org AND MIGRATED_BATCH_IND = 'Y';
• Detecting migration gaps by comparing BATCH_ID values against GME_BATCH_HEADER.
• Reporting batch dates and status for migration cutover analysis using PLAN_START_DATE, ACTUAL_START_DATE, and BATCH_STATUS.
• Joining to GMD_RECIPE_VALIDITY_RULES on RECIPE_VALIDITY_RULE_ID to validate recipe rule references during conversion.

Related Objects

• GMD_RECIPE_VALIDITY_RULES — referenced by RECIPE_VALIDITY_RULE_ID; join on RECIPE_VALIDITY_RULE_ID to the rule's primary key.
• GME_BATCH_HEADER — the live operational batch header; reconcile on BATCH_ID.
• GME_BATCH_STEPS / GME_BATCH_HEADER_MIG step tables — batch detail counterparts linked via BATCH_ID.
• GM_FORMULAS / GMD_FORMULAS — referenced by FORMULA_ID.
• GMD_ROUTINGS — referenced by ROUTING_ID.
• MTL_SYSTEM_ITEMS_B — referenced by PROD_ID for product validation.
• ORG_ORGANIZATION_DEFINITIONS — referenced by ORGANIZATION_ID for plant validation.