Search Results add_tests_to_sample

Overview

GMD_RESULTS_PUB is the public API layer for Quality Control (QC) results processing within the Oracle Process Manufacturing (OPM) module of Oracle E-Business Suite. It exposes a supported programmatic interface that allows external callers — forms, concurrent programs, and custom extensions — to record, validate, and manage QC test results against samples and specifications. The package body header identifies it explicitly as "the public layer for the QC RESULTS," confirming its role as the sanctioned entry point into the results group APIs rather than a private implementation package.

The package has been maintained extensively since its original authorship by H. Verdding of OPM Development (EMEA). Its revision history includes fixes for user_context initialization, composite result creation, sample ID validation, disposition checking, expression-type test evaluation, and the handling of results tied to expression calculations where value, result date, and tester ID must be nulled. These changes reflect the package's centrality to accurate QC data capture across regulated manufacturing environments.

Key Procedures and Functions

• ADD_TESTS_TO_SAMPLE — Associates one or more QC tests with a given sample, establishing the test assignments against which results are subsequently recorded. This is the procedure most directly relevant to the user query "add_tests_to_sample."
• RECORD_RESULTS — Records QC results for tests attached to a sample, applying validation rules and propagating values into specification results. The header notes that this procedure calculates results for expression-type tests and that disposition checks were commented out under Bug 3467531, while expression results with null values force result date and tester ID to null.
• VALIDATE_INPUT — Performs input validation for the public APIs, including expected checks such as resource and sample ID validation referenced in the history notes.
• GET_RESULT_INFO — Retrieves result information for a sample or test context, supporting downstream consumers that need to read QC outcome data without direct table access.

Tables Accessed

The package operates across the core OPM quality schema, accessing tables via APPS synonyms. It reads and writes QC test definitions and values via GMD_QC_TESTS and GMD_QC_TEST_VALUES_B. Result and specification-level data is managed through GMD_RESULTS and GMD_SPEC_RESULTS, while sample context relies on GMD_SAMPLES. Specification-to-test relationships are resolved through GMD_SPEC_TESTS and GMD_SPEC_TESTS_B, with disposition logic touching GMD_EVENT_SPEC_DISP and GMD_SAMPLE_SPEC_DISP. Supporting lookups including FND_APPLICATION, GMD_PARAMETERS_HDR, GMD_QUALITY_CONFIG, GMD_SAMPLING_EVENTS, and the PL/SQL table type PLITBLM round out the data footprint.

Usage Notes

GMD_RESULTS_PUB is invoked from OPM Quality forms and from custom PL/SQL code that needs to add tests to samples or record results without manipulating base tables directly. Although the ETRM metadata lists zero referencing packages, the APIs are callable by external customizations that supply the standard API parameters (p_api_version, p_init_msg_list, p_commit, p_validation_level) along with the results or test record structures. Callers are advised to honor the commit and validation-level conventions and to treat the package as the supported interface, since internal logic — validation, expression evaluation, and specification propagation — assumes this public layer is the entry point. Behavior is consistent across EBS 12.1.1 and 12.2.2.