Results for “phantom_line_id”

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

Overview

GME_MATERIAL_DETAILS is a table owned by the GME schema within Oracle E-Business Suite, supporting the Process Manufacturing Process Execution (GME) module. In Oracle Process Manufacturing, a batch is defined by a recipe or formula, and the material requirements generated for that batch are captured as material detail lines. GME_MATERIAL_DETAILS stores the individual material lines associated with a batch or FPO (Flow Production Order), including planned and actual quantities, item identification, scrap and scale factors, cost allocation attributes, and dispense indicators.

The table exists primarily to track scaled WIP batch quantities. When a WIP batch is scaled, the actual quantity is not updated on the Process Manufacturing (PM) side, so the values must be tracked separately. GME_MATERIAL_DETAILS provides the additional quantity columns required so that actual quantities align between the PM and POC (Process Operation Control) sides of the application. From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone, suggesting it is best modeled as a hub or satellite in its own right rather than as a dependent link, given its self-contained primary key and lack of documented foreign key dependencies.

Key Information Stored

The table contains 75 documented columns. The most significant include:

• MATERIAL_DETAIL_ID — surrogate primary key defined by GME_MATERIAL_DETAILS_PK; uniquely identifies each material detail row.
• BATCH_ID, LINE_NO, LINE_TYPE — together form the business-key candidate GME_MATERIAL_DETAILS_U1, linking each line to its parent batch or FPO.
• ITEM_ID / INVENTORY_ITEM_ID — identifiers for the material item on the line.
• FORMULALINE_ID — reference to the originating formula line.
• PLAN_QTY, ACTUAL_QTY, WIP_PLAN_QTY, ORIGINAL_QTY, ORIGINAL_PRIMARY_QTY — quantity columns supporting planning, actual consumption, WIP scaling, and original values prior to scaling.
• ITEM_UM, ITEM_UM2, DTL_UM — units of measure for the material quantities.
• SCALE_TYPE, SCALE_MULTIPLE, SCALE_ROUNDING_VARIANCE — configuration governing batch scaling behavior.
• SCRAP_FACTOR — expected scrap percentage applied to the line.
• COST, COST_ALLOC, ALLOC_IND — cost and cost allocation attributes.
• RELEASE_TYPE, PHANTOM_TYPE, PHANTOM_ID, PHANTOM_LINE_ID — release and phantom line controls.
• DISPENSE_IND — indicates whether the material line is subject to dispensing.
• CONTRIBUTE_YIELD_IND, CONTRIBUTE_STEP_QTY_IND — flags controlling contribution to yield and step quantity calculations.
• ORGANIZATION_ID, SUBINVENTORY, LOCATOR_ID, REVISION — inventory and warehouse context.
• MATERIAL_REQUIREMENT_DATE, MOVE_ORDER_LINE_ID — scheduling and move order linkage.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, ATTRIBUTE_CATEGORY, ATTRIBUTE1–30 — standard EBS audit and descriptive flexfield columns.

Common Use Cases and Queries

Typical reporting scenarios include reconciling scaled batch quantities between PM and POC, auditing actual versus planned material consumption, and analyzing scrap and cost allocation by batch. A representative query joins the batch header to detail lines:

• Retrieving all material lines for a batch: SELECT * FROM gme.gme_material_details WHERE batch_id = :batch_id;
• Comparing planned against actual quantities where scaling occurred: SELECT batch_id, line_no, plan_qty, actual_qty, wip_plan_qty FROM gme.gme_material_details WHERE scale_type IS NOT NULL;
• Aggregating dispensed materials across batches by item and organization: SELECT organization_id, inventory_item_id, SUM(actual_qty) FROM gme.gme_material_details WHERE dispense_ind = 'Y' GROUP BY organization_id, inventory_item_id;
• Identifying phantom lines: filter on phantom_type or join via phantom_line_id.
• Reporting cost allocation by batch: aggregate cost grouped by batch_id.

These patterns support reconciliation reports, batch cost analysis, and variance tracking for scaled WIP batches.

Related Objects

The most significant related objects include the batch header and formula structures that supply the parent context for each material line:

• GME_BATCH_HEADER — joined on GME_MATERIAL_DETAILS.BATCH_ID = GME_BATCH_HEADER.BATCH_ID, providing batch identity and status.
• GME_FORMULA_LINES (or FM_FORM_MST_LINES) — joined via FORMULALINE_ID to retrieve formula definition.
• GME_BATCH_STEPS — batch step context for line sequencing.
• Mtl_System_Items — joined via INVENTORY_ITEM_ID for item descriptions.
• MTL_ITEM_LOCATIONS / MTL_SECONDARY_INVENTORIES — joined via LOCATOR_ID and SUBINVENTORY.
• MTL_MATERIAL_TRANSACTIONS — actual consumption driven from material detail lines.
• WIP_MOVE_ORDER_LINES — joined via MOVE_ORDER_LINE_ID for move order execution.
• GME_MATERIAL_DETAILS_PK / GME_MATERIAL_DETAILS_U1 — indexes enforcing uniqueness on MATERIAL_DETAIL_ID and (BATCH_ID, LINE_NO, LINE_TYPE) respectively.