Search Results get_conf_match_value

Overview

APPS.GMD_SAMPLES_PUB is the public PL/SQL layer for quality control sample handling within Oracle Process Manufacturing (OPM). It encapsulates the business logic that creates, validates, and deletes quality samples associated with inventory, work-in-process (WIP), customer, supplier, stability, location, and resource sampling events. Because it is classified as a PUB package, its procedures constitute a supported API surface intended to be called from other Oracle E-Business Suite components rather than directly by end users.

The package body carries a documented header dating to 2008 (120.15.12010000.1). Its history reflects steady evolution across releases: early additions supplied item, inventory, WIP, customer, supplier, and generic sample validations; subsequent changes added stability, resource, and location validations (Mini Pack K, API version 2.0), receipt-information checks, material detail identifiers, and a shift away from the QC$EXACTSPECMATCH profile toward GMD_QUALITY_CONFIG lookups via the GET_CONF_MATCH_VALUE function. In Oracle EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and is referenced by zero downstream packages, confirming its role as a top-level public entry point consumed primarily by forms and concurrent programs.

Key Procedures and Functions

• CREATE_SAMPLES — Creates quality sample records, and is the principal write entry point for the package.
• FIND_MATCHING_SPEC — Locates the specification that applies to a given sample context; used to drive spec matching independently of the deprecated profile mechanism.
• DELETE_SAMPLES — Removes existing sample records, complementing CREATE_SAMPLES as the deletion counterpart.
• VALIDATE_ITEM_CONTROLS — Confirms that item-level quality control settings permit the requested sampling operation.
• VALIDATE_INV_SAMPLE — Validates samples originating from inventory.
• VALIDATE_CUST_SAMPLE — Validates samples originating from customer sources.
• VALIDATE_SUPP_SAMPLE — Validates supplier-originated samples, including receipt information checks added by Bug 3576573.
• VALIDATE_WIP_SAMPLE — Validates work-in-process samples; the batch cursor was modified (Bug 3256248) to include completed batches.
• VALIDATE_SAMPLE — Performs common or generic sample validation shared across source types.
• VALIDATE_LOCATION_SAMPLE — Validates samples tied to a location context.
• VALIDATE_RESOURCE_SAMPLE — Validates samples tied to a resource context.
• VALIDATE_STABILITY_SAMPLE — Validates stability-study samples.

Note: parameter lists are intentionally not reproduced here; refer to the package specification for exact signatures.

Tables Accessed

The package reads and writes through APPS synonyms. Core sample data is held in GMD_SAMPLES, with specification and event links in GMD_SAMPLE_SPEC_DISP, GMD_EVENT_SPEC_DISP, and GMD_SAMPLING_EVENTS. Specification matching draws on GMD_CUSTOMER_SPEC_VRS, GMD_INVENTORY_SPEC_VRS, and GMD_MONITORING_SPEC_VRS. Configuration behaviour is retrieved from GMD_QUALITY_CONFIG, replacing the former profile lookup. Manufacturing context is supplied by GMD_RECIPES_B, GMD_RECIPE_VALIDITY_RULES, GMD_OPERATIONS, FM_FORM_MST_B, FM_MATL_DTL, and CR_RSRC_MST. User identity is resolved through FND_USER. Readers searching on "mtl_subinventories" should note that no direct reference to MTL_SUBINVENTORIES is documented for this package; inventory subinventory context is relevant only insofar as it feeds the inventory sample validations.

Usage Notes

GMD_SAMPLES_PUB is typically invoked from OPM Quality forms and from concurrent programs that create or maintain samples, and it may be called from custom code where automated sample generation is required. Callers should treat it strictly as a public API, supply values matching the documented source types, and avoid bypassing the VALIDATE_* routines before invoking CREATE_SAMPLES, since those validations enforce item control and source-specific integrity rules. The change to GMD_QUALITY_CONFIG means exact-spec-match behaviour is now organisation-aware, resolved per org through GET_CONF_MATCH_VALUE; callers in multi-organisation environments should not assume a single global setting.