Search Results gme_batch_step_resources_mig

Overview

The GME_BATCH_STEP_RESOURCES_MIG table is a Process Manufacturing Process Execution (GME) object owned by the GME schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its naming convention (_MIG) suggests, it functions as a migration or interface staging table used to load batch step resource definitions from external systems, legacy applications, or conversion programs into the Oracle Process Manufacturing (OPM) model. It holds resource-level information tied to a specific batch step activity within a batch, capturing planned and actual resource usage, capacity, cost analysis, and descriptive flexfield attributes.

The table contains 80 documented columns. Based on heuristic Data Vault classification mined from its foreign key structure, the object is characterized as standalone. In modeling terms, this suggests the table is not positioned as a classic hub, link, or satellite but rather as an operational staging or detail table whose identity is largely derived from parent batch step activity records. The sole documented foreign key points from BATCHSTEP_ACTIVITY_ID to the GME_BATCH_STEP_ACTIVITIES table.

Key Information Stored

The most significant columns capture the identity, quantity, timing, and costing context of a batch step resource:

• BATCHSTEP_RESOURCE_ID — unique identifier for the batch step resource record; the primary key candidate.
• BATCHSTEP_ACTIVITY_ID — foreign key to GME_BATCH_STEP_ACTIVITIES, linking the resource to its parent activity.
• BATCHSTEP_ID and BATCH_ID — business key candidates identifying the owning step and batch.
• RESOURCES — the resource name or code being consumed or applied.
• ORGANIZATION_ID — the inventory organization context for the record.
• PLAN_RSRC_QTY, ACTUAL_RSRC_QTY, ORIGINAL_RSRC_QTY — planned, actual, and original resource quantities.
• PLAN_RSRC_USAGE, ACTUAL_RSRC_USAGE, ORIGINAL_RSRC_USAGE — corresponding usage values.
• RESOURCE_QTY_UM, USAGE_UM, CAPACITY_UM — units of measure for quantity, usage, and capacity.
• PLAN_START_DATE, PLAN_CMPLT_DATE, ACTUAL_START_DATE, ACTUAL_CMPLT_DATE — scheduling windows.
• MIN_CAPACITY, MAX_CAPACITY, CAPACITY_TOLERANCE — capacity thresholds.
• COST_ANALYSIS_CODE, COST_CMPNTCLS_ID — costing classification.
• PRIM_RSRC_IND — indicates whether the resource is primary.
• SEQUENCE_DEPENDENT_ID, SEQUENCE_DEPENDENT_USAGE — sequence-dependent behavior.
• ATTRIBUTE1–ATTRIBUTE30, ATTRIBUTE_CATEGORY — descriptive flexfield storage.

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

Common Use Cases and Queries

Typical usage centers on migration validation and operational reporting. A conversion analyst might verify that staged resources loaded correctly by comparing planned versus original quantities:

• Identifying unbalanced migration rows where PLAN_RSRC_QTY differs from ORIGINAL_RSRC_QTY.
• Joining to GME_BATCH_STEP_ACTIVITIES to reconcile every activity with its resources.
• Reporting capacity exceptions where actual usage exceeds MAX_CAPACITY.
• Cost analysis extracts grouped by COST_ANALYSIS_CODE and COST_CMPNTCLS_ID.

A representative query pattern:

SELECT m.BATCH_ID, m.BATCHSTEP_ID, m.RESOURCES, m.PLAN_RSRC_QTY, m.ACTUAL_RSRC_QTY FROM GME.GME_BATCH_STEP_RESOURCES_MIG m JOIN GME.GME_BATCH_STEP_ACTIVITIES a ON a.BATCHSTEP_ACTIVITY_ID = m.BATCHSTEP_ACTIVITY_ID WHERE m.ORGANIZATION_ID = :org;

Related Objects

• GME_BATCH_STEP_ACTIVITIES — parent table; join on BATCHSTEP_ACTIVITY_ID.
• GME_BATCH_STEPS — parent step; join on BATCHSTEP_ID.
• GME_BATCH_HEADERS — batch header; join on BATCH_ID.
• GME_RESOURCE_TYPES / GME_RESOURCES — resource master definitions referenced via RESOURCES.
• CM_CMPNTCLS_B — costing component classes referenced via COST_CMPNTCLS_ID.
• GME_BATCH_STEP_RESOURCES — the target production table populated by migration programs.