Search Results dump_data_points

Overview

The APPS.GMD_MASS_RESULTS_GRP package is a Group-layer PL/SQL API belonging to the Oracle Process Manufacturing (OPM) Quality Management module. In Oracle EBS 12.1.1 and 12.2.2, OPM quality entities are exposed through a layered API architecture comprising table-handler (TAPI), group, and public layers. The group layer exists to coordinate multiple business entities within a single logical transaction, enforcing the business rules that span more than one base table.

The package header comment identifies its purpose explicitly: it contains group-layer APIs for the Mass Results Entity. The Mass Results entity represents the bulk propagation of specification test results across many samples, results, and specification instances that originate from a sampling event. The package therefore supports the mass-entry and mass-processing side of quality data collection, where a laboratory or quality technician records results for a batch of samples derived from one or more sampling events, and the system must distribute those outcomes consistently through the results and specification tables.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer. The header carries a 2003 copyright and a header revision marker (GMDGMRSS.pls 115.0), confirming it is a long-standing component of the OPM quality data model. The API classification is GRP, and the package is referenced by zero other packages in the ETRM inventory, indicating it is a top-of-stack entry point rather than a dependency of lower-level code.

Key Procedures and Functions

The package exposes two documented procedures.

• POPULATE_RESULTS — Accepts a sequence identifier and returns a return-status indicator. It drives the population of result records for a mass-results transaction, taking the identifier that links a batch of related rows and materializing the corresponding specification results within the quality data model. It is the primary workhorse of the package and is the procedure most likely to be invoked by mass results processing.
• DUMP_DATA_POINTS — Accepts optional sample, result, and test identifiers, all defaulting to NULL. It is a diagnostic or maintenance routine that emits data-point information for the supplied scope. When called with NULL arguments it operates across the full scope of mass results data points; when specific identifiers are supplied, it narrows the output to those samples, results, or tests. This procedure appears to be intended for debugging and data inspection rather than for transactional business processing.

No functions and no additional procedures are documented for this package. Parameter lists beyond those shown in the specification should not be assumed; in particular, no overloads are documented.

Tables Accessed

The documented table references reflect the breadth of the Mass Results entity:

• GMD_MASS_RESULTS_GT — a global temporary table that serves as the staging or working area for mass results processing, populated and consumed by POPULATE_RESULTS.
• GMD_RESULTS, GMD_SPEC_RESULTS, GMD_SAMPLES, GMD_MASS_SAMPLES — the core quality data tables holding result values, specification results, and the sample records to which results are attached.
• GMD_SAMPLING_EVENTS, GMD_EVENT_SPEC_DISP, GMD_SAMPLE_SPEC_DISP — sampling event and specification disposition tables that determine which specifications and tests apply to a given sample or event.
• GMD_QC_TESTS, GMD_SPEC_TESTS_B, GMD_TEST_METHODS — the test definition, specification test, and test method tables that supply the analytical framework against which results are recorded and evaluated.

Together these tables indicate that the package resolves applicable tests and specifications for sampled material, applies recorded results, and writes or stages the resulting specification outcomes.

Usage Notes

Because the package is a group-layer API, it is typically invoked from OPM Quality forms or from custom PL/SQL that needs to reproduce form behavior at the API level rather than through direct table DML. Mass results entry, laboratory data import, and batch result uploads are the most probable callers. Standard practice for GRP-layer APIs is to wrap the call in the caller's own transaction and inspect the returned status before committing. POPULATE_RESULTS should be treated as transactional; DUMP_DATA_POINTS should be treated as a read-only diagnostic aid and restricted to development or support use, since it produces output rather than performing business processing. Because the package is referenced by no other documented packages and is declared AUTHID CURRENT_USER, callers must ensure the invoking schema has the necessary privileges on the underlying GMD tables. In 12.2.2, as in 12.1.1, the object remains owned by APPS and is exposed through APPS synonyms.