Results for “line_type_meaning”

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

Overview

GME_MATERIAL_DETAILS_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite, belonging to the GME – Process Manufacturing Process Execution product family. It is defined over the base table GME_MATERIAL_DETAILS and enriches the stored material detail rows with descriptive and decoded information drawn from multiple system views, batch headers, and lookup tables. In Oracle EBS 12.1.1 and 12.2.2, the view functions primarily as a reporting and integration layer, presenting batch material line data in a form that is directly consumable by concurrent programs, Oracle Reports, BI Publisher templates, and external interfaces without requiring callers to resolve foreign keys or decode lookup codes themselves.

The view is especially relevant to users searching for the PHANTOM_LINE_ID column, which it exposes directly from the underlying GME_MATERIAL_DETAILS table. This column links material lines to phantom (co-product, by-product, or intermediate) component structures within a batch, supporting traceability of phantom material relationships during process execution.

Underlying Base Objects

The documented base objects referenced by the view are:

• GME_MATERIAL_DETAILS (SYNONYM) — the primary table supplying all material line attributes.
• GME_BATCH_HEADER (SYNONYM) — joined to retrieve BATCH_NO as PHANTOM_BATCH_NO.
• MTL_SYSTEM_ITEMS_VL (VIEW) — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID to provide item concatenated segments and description.
• MTL_ITEM_LOCATIONS_KFV (VIEW) — supplies the concatenated locator value.
• GEM_LOOKUPS (VIEW) — joined multiple times to decode LINE_TYPE, RELEASE_TYPE, BY_PRODUCT_TYPE, and the yes/no indicator columns such as CONTRIBUTE_YIELD_IND, CONTRIBUTE_STEP_QTY_IND, and DISPENSE_IND.
• FND_DATE (PACKAGE) and FND_TIMEZONES (PACKAGE) — used to convert MATERIAL_REQUIREMENT_DATE into a server-timezone display date.

All joins are keyed on organization, item, or lookup type and code, ensuring the view returns one row per material detail line with all descriptive context resolved.

Key Columns

Identity and structural columns include ORGANIZATION_ID, MATERIAL_DETAIL_ID, BATCH_ID, FORMULALINE_ID, PHANTOM_ID, and PHANTOM_LINE_ID. Quantity and planning attributes include PLAN_QTY, WIP_PLAN_QTY, ACTUAL_QTY, BACKORDERED_QTY, ORIGINAL_QTY, and BACKORDERED_QTY. Descriptive columns include ITEM_NO and ITEM_DESC (from MTL_SYSTEM_ITEMS_VL), LOCATOR (from MTL_ITEM_LOCATIONS_KFV), and PHANTOM_BATCH_NO (from GME_BATCH_HEADER).

Decoded meaning columns include MEANING (for LINE_TYPE via lookup GMD_FORMULA_ITEM_TYPE), RELEASE_TYPE_MEANING, BY_PRODUCT_TYPE_MEANING, and the yes/no MEANING pairs for CONTRIBUTE_YIELD_IND_MEANING, CONTRIBUTE_STEP_QTY_MEANING, and DISPENSE_IND_MEANING. Date handling is provided through MATERIAL_REQUIREMENT_DSPLY_DT, which applies FND_DATE.DATE_TO_DISPLAYDT with the server timezone code.

Common Use Cases and Queries

The view is typically used to report batch material requirements and consumption, trace phantom component lines, and feed downstream integration. A representative query locating phantom lines for a batch is:

SELECT material_detail_id, batch_id, phantom_id, phantom_line_id,item_no, plan_qty, actual_qty, phantom_batch_no FROM apps.gme_material_details_v WHERE batch_id = :p_batch_id AND phantom_line_id IS NOT NULL;

A second common pattern retrieves detailed line information with decoded types and requirement dates:

SELECT line_no, item_no, item_desc, meaning, plan_qty, actual_qty, material_requirement_dsply_dt, locator FROM apps.gme_material_details_v WHERE organization_id = :p_org AND batch_id = :p_batch_id ORDER BY line_no;

Because the view resolves item, locator, batch, and lookup descriptions in a single query, it reduces the number of joins required in custom reports and interfaces while remaining consistent with standard Oracle Process Manufacturing data structures.