Search Results gmd_material_release_type




Overview
Explore in AI Chat

Overview

APPS.GME_MATERIAL_DETAILS_V is an Oracle E-Business Suite view that presents material detail records for process manufacturing batches and formulas. It is defined over the GME_MATERIAL_DETAILS synonym—the operational table that stores the individual material lines associated with a batch (GME_BATCH_HEADER) and formula lines—and enriches those records with descriptive attributes drawn from inventory, location, and lookup sources. Functionally, the view supplies the ingredient and by-product lines of a batch, including planned, WIP-planned, and actual quantities, requirement dates, phantom relationships, scaling parameters, and yield-contribution flags.

Because it consolidates foreign-key values into human-readable meanings (item number, description, line type, release type, locator, batch number), the view is well suited for reporting, ad hoc inquiry, and integration extracts. Its role in Oracle EBS 12.1.1 and 12.2.2 is to provide a denormalized, reporting-friendly projection of the material detail data without requiring the caller to construct the same set of joins manually.

Underlying Base Objects

The documented referenced objects are FND_DATE (PACKAGE), FND_TIMEZONES (PACKAGE), GEM_LOOKUPS (VIEW), GME_BATCH_HEADER (SYNONYM), GME_MATERIAL_DETAILS (SYNONYM), MTL_ITEM_LOCATIONS_KFV (VIEW), and MTL_SYSTEM_ITEMS_VL (VIEW). The primary driving object is GME_MATERIAL_DETAILS (aliased GMD), from which all material line columns originate. MTL_SYSTEM_ITEMS_VL is joined on INVENTORY_ITEM_ID and ORGANIZATION_ID to supply the concatenated item number and item description. MTL_ITEM_LOCATIONS_KFV provides the concatenated locator value. GME_BATCH_HEADER supplies the phantom batch number. GEM_LOOKUPS is joined multiple times to resolve lookup meanings for line type, release type, by-product type, and the yes/no decode flags. The FND_DATE and FND_TIMEZONES packages are used to convert the material requirement date into a display-formatted value using the server time zone.

Key Columns

Common Use Cases and Queries

A frequent requirement is to list all material lines for a given batch with their item descriptions and quantities. For example:

SELECT batch_id, line_no, item_no, item_desc, line_type, meaning,
       plan_qty, actual_qty, dtl_um
FROM   apps.gme_material_details_v
WHERE  batch_id = :p_batch_id
ORDER BY line_no;

Another common scenario is reporting the release type of material lines, which relates directly to the search term “gmd_material_release_type.” The view exposes both the code (RELEASE_TYPE) and its decoded meaning (RELEASE_TYPE_MEANING):

SELECT batch_id, line_no, item_no, release_type, release_type_meaning
FROM   apps.gme_material_details_v
WHERE  release_type IS NOT NULL;

The view also supports analysis of yield and step quantity contribution, phantom material tracing, and by-product reporting. Because it decodes the yes/no indicators and lookups, it is convenient for operational dashboards and integration extracts where readable values are preferred over raw codes.