Search Results variant_sched_start_date

Overview

GMD_QM_E_MATERIAL_SOURCES_V is an APPS-owned reporting view within the Oracle E-Business Suite Process Manufacturing Product Development module (GMD). It consolidates material source definitions captured against Process Manufacturing quality management setups, joining variant, storage, specification, batch, recipe, and formula context into a single denormalized row per material source. The view supports Quality Management sampling and specification reporting, particularly where sampling plans are attached to material sources tied to batches, recipes, and inventory storage locations.

In EBS 12.1.1 and 12.2.2 the object remains VALID under the APPS schema. Because it references MTL_ORGANIZATIONS and MTL_ITEM_LOCATIONS_KFV, users who search for "mtl_organizations" frequently land on this view when attempting to resolve organization-level inventory context for quality sampling records.

Underlying Base Objects

The documented ETRM 12.2.2 metadata lists the base objects referenced by the view:

• GMD_SS_MATERIAL_SOURCES, GMD_SS_VARIANTS, GMD_SS_STORAGE_PACKAGE — the sampling setup tables that supply the material source, variant, and storage package detail.
• GME_BATCH_HEADER — batch context (batch number) joined on batch ID.
• GMD_RECIPES_B — recipe context; the join to recipe ID is outer.
• GMD_SPECIFICATIONS_B — supplies both the storage specification and default specification attributes.
• FM_FORM_MST_B — formula header for formula number and version.
• MTL_ITEM_LOCATIONS_KFV — descriptive flexfield key flexfield view used to expose the concatenated storage locator segments.
• MTL_PARAMETERS — the inventory organization definition table. Note that the view text references MTL_ORGANIZATIONS; in 12.2 this is resolved through organizational synonyms and MTL_PARAMETERS, which is the documented base object.

Joins are predominantly outer joins (for example to GME_BATCH_HEADER, GMD_RECIPES, GMD_SS_STORAGE_PACKAGE, FM_FORM_MST, MTL_ITEM_LOCATIONS_KFV), allowing rows to return even where the batch, recipe, package, formula, or locator is not yet fully defined.

Key Columns

• PLANT_CODE — organization code from MTL_ORGANIZATIONS, identifying the plant/warehouse where the material source resides.
• SS_ID, VARIANT_ID, VARIANT_NO, MATERIAL_SOURCE_ID — identifiers for the sampling event, variant, and material source record.
• BATCH_NO, RECIPE_NO, RECIPE_VERSION, FORMULA_NO, FORMULA_VERS — production and formulation context.
• LOT_NUMBER, QUANTITY, UOM — lot and quantity details for the sourced material.
• STORAGE_ORG, STORAGE_SUBINVENTORY, STORAGE_LOCATOR — physical storage location, with STORAGE_LOCATOR populated from the concatenated segments of MTL_ITEM_LOCATIONS_KFV.
• STORAGE_SPEC_ID, STORGE_SPEC_NAME, STORAGE_SPEC_VERSION — the specification attached to the storage location.
• DEFAULT_SPEC_ID, DEFAULT_SPEC_NAME, DEFAULT_SPEC_VERSION — the default specification for the material.
• VARIANT_SCHED_START_DATE, SAMPLING_EVENT_ID, SAMPLE_QTY, SAMPLE_QTY_UOM, SAMPLES_PER_TP, RETAINED_SAMPLES — sampling plan attributes.
• RESOURCES, RESOURCE_INSTANCE_ID, YIELD_DATE — resource and yield scheduling context.
• PACKAGE_NAME — the storage package defined in GMD_SS_STORAGE_PACKAGE.

Common Use Cases and Queries

Typical scenarios include reporting the storage specifications and sampling quantities configured for each material source on a batch, resolving the plant code for quality sampling events, and reconciling the storage locator with the organization's subinventory structure.

Example query joining back to the organization definition:

• SELECT v.PLANT_CODE, v.BATCH_NO, v.RECIPE_NO, v.LOT_NUMBER, v.STORAGE_ORG, v.STORAGE_SUBINVENTORY, v.STORAGE_LOCATOR, v.STORGE_SPEC_NAME FROM APPS.GMD_QM_E_MATERIAL_SOURCES_V v WHERE v.PLANT_CODE = :org_code;

Because the view already resolves organization codes, users searching on mtl_organizations can avoid a manual join and instead filter or group directly on PLANT_CODE and STORAGE_ORG to obtain organization-scoped quality sampling output.