Results for “gmo_disp_config_id”

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

Overview

APPS.GMD_MBR_STEP_MATERIAL_V1 is an Oracle E-Business Suite view belonging to the Process Manufacturing (OPM/GMD) module. It consolidates recipe step material information into a single queryable structure, joining recipes, routings, operations, routing steps, formula material effectivities, and inventory item attributes. The view is predominantly used to expose the materials that make up each step of a process recipe, including their quantities, scaling parameters, yield contributions, and by-product behavior.

Its principal reporting role involves the SAMPLE_PLAN_ID column, which is generated at query time rather than being stored on a base table. This makes the view the primary source for identifying the sampling plan associated with a given step material in a recipe. Quality and process engineering teams reference this view when determining what sampling activities apply to a material within a specific recipe context.

Underlying Base Objects

The view is defined over the following documented base objects: FM_FORM_MST (SYNONYM), FM_ROUT_DTL (SYNONYM), GEM_LOOKUPS (VIEW), GMDFMVAL_PUB (PACKAGE), GMD_MATERIAL_EFFECTIVITIES_VW (VIEW), GMD_MBR_UTIL_PKG (PACKAGE), GMD_OPERATIONS_B (SYNONYM), GMD_RECIPES_B (SYNONYM), GMD_RECIPE_STEP_MATERIALS (SYNONYM), GMD_ROUTINGS_B (SYNONYM), GMO_MBR_UTIL (PACKAGE), and MTL_SYSTEM_ITEMS_VL (VIEW).

The FROM clause draws primarily from GMD_RECIPES_B (alias rcp), GMD_RECIPE_STEP_MATERIALS (smatl), GMD_ROUTINGS_B (rout), GMD_OPERATIONS_B (oprn), FM_ROUT_DTL (rdtl), FM_FORM_MST (frm), MTL_SYSTEM_ITEMS_VL (msi), and GEM_LOOKUPS (lkup). The material source is a derived inline view over GMD_MATERIAL_EFFECTIVITIES_VW, ranked by preference and original_item_flag to select the effective material for the current date. Two PL/SQL packages—GMDFMVAL_PUB and GMD_MBR_UTIL_PKG—are invoked for quantity validation and sampling plan resolution, while GMO_MBR_UTIL supplies dispense configuration data.

Key Columns

• FORMULALINE_ID / FORMULA_ID — Identifies the formula and material line to which the step material belongs.
• LINE_TYPE / MEANING — Lookup code and its decoded meaning, distinguishing material line categories.
• LINE_NO / LINE_ITEM_ID — Position and identity of the material line within the formula.
• QTY — Derived via DECODE on ORIGINAL_ITEM_FLAG; when original, the stored quantity is returned, otherwise GMDFMVAL_PUB.GET_LINE_QTY resolves the effective quantity.
• SAMPLE_PLAN_ID — Returned by GMD_MBR_UTIL_PKG.GET_SAMPLING_PLAN, resolving the sampling plan for the item/recipe/routing/operation combination.
• ITEM_ID (INVENTORY_ITEM_ID), CONCATENATED_SEGMENTS, DESCRIPTION, ORGANIZATION_ID, ITEM_UM — Item identity and descriptive attributes sourced from MTL_SYSTEM_ITEMS_VL.
• RECIPE_ID, RECIPE_NO, RECIPE_VERSION, ROUTING_ID, ROUTINGSTEP_ID, OPRN_ID — Full routing and recipe context for the step.
• GMO_DISP_CONFIG_ID — Dispense configuration resolved by GMO_MBR_UTIL.get_dispense_config.
• RELEASE_TYPE, SCRAP_FACTOR, SCALE_TYPE, COST_ALLOC, PHANTOM_TYPE, BY_PRODUCT_TYPE, BUFFER_IND — Process material and scaling control attributes.
• CONTRIBUTE_STEP_QTY_IND, CONTRIBUTE_YIELD_IND, SCALE_MULTIPLE, SCALE_ROUNDING_VARIANCE, ROUNDING_DIRECTION — Yield and scaling behavior flags.

Common Use Cases and Queries

The most direct use is retrieving sampling plan assignments for a set of step materials. Because SAMPLE_PLAN_ID is computed at runtime, callers can filter by recipe, routing step, or formula to retrieve applicable plans quickly.

SELECT recipe_id, recipe_no, routingstep_id,
       concatenated_segments, description, sample_plan_id
FROM   apps.gmd_mbr_step_material_v1
WHERE  formula_id = :p_formula_id;

Another common pattern joins the view to quality sampling plan tables to enrich plan descriptions, or reports step quantities and dispense configuration per operation for shop-floor documentation. Because quantity resolution depends on the effective material view, teams querying this object for date-sensitive reporting should be aware that the ranked effectivity sub-query reflects the current sysdate, not an arbitrary reporting date.