Search Results gmd_spec_match_grp




Overview
Explore in AI Chat

Overview

GMD_SPEC_MATCH_GRP is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified as a Group (GRP) API within the Process Manufacturing (OPM) Quality module. Its principal business function is specification matching: given a manufacturing or inventory context, the package determines which quality specification (or specification version) applies to an item, lot, batch, resource, or location. This capability underpins quality data collection, results entry, and disposition decisions, ensuring that the correct tests, limits, and versioned specifications are selected whenever samples are taken or results are evaluated.

The package is central to the OPM Quality Management architecture. It resolves the appropriate specification from multiple sources—inventory, customer, supplier, WIP, monitoring, location, and resource specifications—and applies the business rules that govern precedence when more than one specification type could apply. The metadata lists a status of VALID, and the package is referenced by nine other database objects and itself (recursive reference), indicating it acts as a shared utility layer consumed by other quality APIs and forms.

Key Procedures and Functions

Eleven documented procedures and functions comprise the public interface:

  • FIND_INVENTORY_SPEC — Locates the inventory specification applicable to the current item/lot context.
  • FIND_CUSTOMER_SPEC — Retrieves the customer specification relevant to a given customer or order line context.
  • FIND_CUST_OR_INV_SPEC — Applies precedence logic to return either the customer or inventory specification.
  • FIND_WIP_SPEC — Identifies the work-in-process specification for a batch step or routing operation.
  • FIND_WIP_OR_INV_SPEC — Resolves between WIP and inventory specifications based on context.
  • FIND_SUPPLIER_SPEC — Returns the supplier specification applicable to received material.
  • FIND_SUPPLIER_OR_INV_SPEC — Determines whether the supplier or inventory specification governs.
  • GET_RESULT_MATCH_FOR_SPEC — Evaluates results against the matched specification, supporting result-to-spec comparison.
  • FIND_LOCATION_SPEC — Resolves specifications tied to a storage or sampling location.
  • FIND_RESOURCE_SPEC — Returns specifications associated with a resource.
  • GET_INV_SPEC_OR_VR_ID — Returns the inventory specification or specification version identifier for the context.

Tables Accessed

The package reads and references specification masters and version tables including GMD_SPECIFICATIONS_B, GMD_SPEC_TESTS_B, GMD_INVENTORY_SPEC_VRS, GMD_CUSTOMER_SPEC_VRS, GMD_SUPPLIER_SPEC_VRS, GMD_MONITORING_SPEC_VRS, and GMD_WIP_SPEC_VRS. Operational context is drawn from GMD_SAMPLES, GMD_RESULTS, GMD_RESULTS_GRP, GMD_SAMPLE_SPEC_DISP, and GMD_QC_STATUS for quality execution data. Manufacturing context comes from GMD_RECIPES_B, GMD_ROUTINGS_B, GMD_OPERATIONS_B, GME_BATCH_STEPS, and FM_FORM_MST_B/FM_ROUT_DTL. Item and lot identity is resolved via MTL_SYSTEM_ITEMS_B and MTL_LOT_NUMBERS, with OE_ORDER_LINES_ALL supporting customer/order-driven matching.

Usage Notes

GMD_SPEC_MATCH_GRP is typically invoked indirectly rather than called directly by end users. It is consumed by other quality APIs such as GMD_API_PUB, GMD_RESULTS_GRP, and by forms in the OPM Quality module when a user attaches a specification to a sample, enters results, or queries applicable specifications. Because it depends on FND_API and FND_MSG_PUB, callers can expect standard EBS error handling and message stack behavior. The presence of PUBLIC and PLITBLM dependencies indicates use of PL/SQL tables for collection handling. Custom extensions that need specification-matching behavior should call these documented procedures rather than re-implement matching logic, preserving consistency with delivered quality rules across OPM.