Search Results get_result_info

Overview

APPS.GMD_RESULTS_PUB is a public PL/SQL package in Oracle E-Business Suite that exposes the application programming interface for process manufacturing quality results. Its header comment, dated to file version 120.1, states that the interface "is used for processing QM Results" and that the package "defines and implements the procedures and datatypes required for processing QM results." The package is registered under product GMD with an active lifecycle and a compatibility designation of S (supported), and its repository scope is marked public. In business terms, this package is the supported entry point through which external or internal callers create, validate, and evaluate quality laboratory results against the specifications that govern a sample. It exists so that callers do not write directly to the underlying GMD quality tables and thereby bypass the specification evaluation, audit, and inventory conversion logic embedded in the API.

A central element of the package is the strongly typed RESULTS_REC record, which models a single quality result. Its fields span the result identifier, sample and organization context, laboratory organization, test identity and replicate count, result value and result date, test kit inventory item and lot, tester and test provider information, sequence, and the specification evaluation attributes: in-specification indicator, assay retest indicator, evaluation indicator, action code, and the ad hoc print-on-COA indicator. Planned and actual resource columns are also present. The record's field-level types anchor to GMD_RESULTS, GMD_SAMPLES, GMD_QC_TESTS, and GMD_SPEC_RESULTS, which reflects the package's role as a controlled gateway to those tables.

Key Procedures and Functions

The ETRM metadata documents four public procedures and functions for this package.

• GET_RESULT_INFO — Retrieves quality result information for a given result or sample context, returning it in the package's result record structure. This is the routine most directly associated with the common search term "get_result_info," and it is the principal read interface for callers that need to inspect an existing result without querying the base tables directly.
• VALIDATE_INPUT — Performs input validation before a result is processed, allowing the caller to detect missing, inconsistent, or out-of-range values against the package's rules rather than surfacing a raw constraint error at insert time.
• RECORD_RESULTS — Persists quality results, writing the supplied result record data into the GMD quality result structures and triggering the associated specification evaluation and action code derivation.
• ADD_TESTS_TO_SAMPLE — Associates test definitions with a sample, populating the expected test set so that results can subsequently be recorded against those tests.

Because the package is classified public and supported, these four routines constitute the sanctioned surface; the record type and its supporting declarations are shared by all of them.

Tables Accessed

The package operates across the core GMD quality model. GMD_RESULTS and GMD_SAMPLES hold the result and sample headers, while GMD_QC_TESTS and GMD_QC_TEST_VALUES_B provide test definitions and discrete test values. GMD_SPEC_TESTS and GMD_SPEC_TESTS_B define the specification tests against which results are judged, and GMD_SPEC_RESULTS stores the evaluation outcome, including the in-specification, evaluation, and action code values exposed on the result record. GMD_SPEC_DISP views, GMD_EVENT_SPEC_DISP and GMD_SAMPLE_SPEC_DISP, resolve the applicable specification for an event or sample, and GMD_SAMPLING_EVENTS supplies sampling event context. GMD_PARAMETERS_HDR and GMD_QUALITY_CONFIG supply quality parameter and configuration defaults that drive evaluation behavior, while GMD_EVENT_SPEC_DISP links events to specifications. FND_APPLICATION is referenced for application context lookups, and PLITBLM is used as the standard PL/SQL index-by table of VARCHAR2 for list handling. Through APPS synonyms, these objects are resolved in the APPS schema.

Usage Notes

GMD_RESULTS_PUB is invoked from Oracle Process Manufacturing quality forms and from concurrent or custom PL/SQL programs that need to load or interrogate laboratory results, because it encapsulates specification evaluation that direct DML would not reproduce. The documented reference count shows that no other packaged object in the ETRM metadata calls this package, so its consumers are forms, concurrent programs, and customer extensions rather than peer PL/SQL packages. Typical custom usage is to call GET_RESULT_INFO to read an existing result into RESULTS_REC, or to populate the record and call VALIDATE_INPUT followed by RECORD_RESULTS when loading results from an external LIMS or instrument interface. Callers must build the RESULTS_REC record fully, supply a valid UPDATE_INSTANCE_ID for concurrency handling, and rely on the package's supplied field types rather than positional literals, since the record definition is the contract. Because the package is supported and public, it may be referenced from custom code in both 12.1.1 and 12.2.2, but direct manipulation of the underlying GMD tables should be avoided to preserve specification evaluation and audit integrity.