Search Results scrap_factor




Overview
Explore in AI Chat

Overview

GME_MATERIAL_DETAILS_V1 is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite, residing in the GME (Process Manufacturing Process Execution) product family. Its purpose is to expose batch and FPO (Firm Planned Order) material detail data in a legacy-compatible column layout, ensuring that customizations, reports, and integrations written against earlier releases of Oracle Process Manufacturing continue to function after upgrade. The view presents one row per material line associated with a batch or FPO, covering products, ingredients, and by-products, and includes both planned and actual quantity information. Because the view is defined as a simple projection over a single base table with no filtering or join predicates, it behaves as a lightweight compatibility shim rather than a transformation layer. All columns map directly to columns of the same name in the underlying table, with the exception of two positional placeholders that surface as PLAN_QTY2 and ACTUAL_QTY2 in the column dictionary but carry no data (they are defined as NULL in the view text). The view's status is VALID and it is documented in ETRM 12.2.2 with the same structure as in 12.1.1.

Underlying Base Objects

The view is defined over a single referenced base object, GME_MATERIAL_DETAILS, accessed through its APPS synonym. The ETRM metadata lists the referenced base object as GME_MATERIAL_DETAILS (SYNONYM), confirming that the view is a thin wrapper around that table. The view text is a straightforward SELECT of every column from GME_MATERIAL_DETAILS, with no WHERE clause, GROUP BY, DISTINCT, or UNION, and no joins to any other GME or inventory table. This means row cardinality, data type, and semantics are identical to the base table, and any DML against the base table is immediately reflected in the view. Because no other objects are referenced, the view does not introduce additional security or performance overhead beyond a standard dictionary lookup; the optimizer generally collapses the view into the base table access path unless the view is referenced in a context requiring materialization.

Key Columns

The identifier columns anchor each material line. BATCH_ID links the row to the parent batch or FPO, while MATERIAL_DETAIL_ID (exposed in the dictionary as LINE_ID) is the unique material detail line identifier. FORMULALINE_ID and LINE_NO tie the material back to its formula definition and line sequence. ITEM_ID identifies the product, ingredient, or by-product.

  • LINE_TYPE — classifies the material line (for example, product, ingredient, or by-product).
  • PLAN_QTY — the planned quantity for the material line, expressed in ITEM_UM; the secondary PLAN_QTY2 placeholder is NULL.
  • ACTUAL_QTY — the actual quantity consumed or produced for the material line; this is the column most frequently searched for reporting and reconciliation. The ACTUAL_QTY2 placeholder is NULL.
  • ITEM_UM / ITEM_UM2 — primary and secondary units of measure.
  • RELEASE_TYPE, SCRAP_FACTOR, SCALE_TYPE, PHANTOM_TYPE — control attributes governing material release, scrap allowance, batch scaling, and phantom handling.
  • COST, COST_ALLOC, ALLOC_IND — cost allocation values and indicators for the material line.
  • PHANTOM_ID, TEXT_CODE — phantom reference and text/template code.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
  • ATTRIBUTE1 through ATTRIBUTE30, ATTRIBUTE_CATEGORY — the DFF (descriptive flexfield) columns available for user-defined extensions.
  • IN_USE — exposed as a NULL placeholder for compatibility and is not populated from the base table.

Common Use Cases and Queries

Typical usage centers on comparing planned versus actual material consumption for a batch or FPO, particularly where legacy code expects the V1 column layout. A representative query to retrieve actual quantities for all materials in a batch is:

  • SELECT batch_id, line_id, item_id, line_type, plan_qty, actual_qty, item_um FROM apps.gme_material_details_v1 WHERE batch_id = :p_batch_id ORDER BY line_no;

To find variances between planned and actual quantities by item, the view can be aggregated directly:

  • SELECT item_id, SUM(plan_qty) planned, SUM(actual_qty) actual, SUM(actual_qty) - SUM(plan_qty) variance FROM apps.gme_material_details_v1 WHERE batch_id = :p_batch_id GROUP BY item_id;

Because the view is unfiltered, queries against ACTUAL_QTY should always include a selective predicate such as BATCH_ID or a date range on CREATION_DATE to avoid full-table scans on a high-volume table. When the DFF attributes are required, the ATTRIBUTE_CATEGORY combined with ATTRIBUTE1–30 columns can be selected in the same statement. For new development, Oracle recommends using the base table GME_MATERIAL_DETAILS or the current-generation GME views; GME_MATERIAL_DETAILS_V1 should be reserved for maintaining backward compatibility with existing customizations and interfaces.