Search Results get_result_match_for_spec
Overview
GMD_COA_DATA_OM_NEW is a group-layer PL/SQL API in the Oracle EBS Process Manufacturing (OPM) product family. Its purpose is to populate Certificate of Analysis (COA) data by gathering quality results, specifications, and associated order and inventory context into the GMD_COA_DATA structure. The package header comments describe it as "group layer API for Population Of COA DATA," confirming that it functions as the assembly engine that feeds the COA report and related header/detail tables. It has been maintained continuously since its creation by Manish Gupta in June 2003, with subsequent fixes recorded against defects concerning sample selection, test evaluation filtering, specification matching, and secondary unit of measure population.
Key Procedures and Functions
- POPULATE_COA_DATA — The principal driver procedure. It orchestrates the retrieval and insertion of COA content, drawing on quality results, specifications, lots, and order data. It is the entry point most callers invoke.
- GET_TEXT_FOR_RANGE — Retrieves textual content associated with a specification or result range, typically for narrative or attribute text printed on the COA.
- GETPRECISION — Derives the numeric precision applied to reported test values so that results display consistently on the certificate.
- LOG_INITIALIZE — Establishes the logging context used by the package's debug and diagnostic routines.
- PRINTLN — Writes a line to the package's log, supporting troubleshooting during concurrent processing.
- POPULATE_HDR_TEXT — Inserts header-level narrative text into GMD_COA_SPEC_HDR_TEXT from the QC text table, a procedure added under Bug#4260445 to carry specification text onto the COA header.
Historical revisions documented in the header reference related internal routines such as get_order_params, populate_spec, getLatestSample, and call_spec_match. The procedure getLatestSample was modified to validate a specified lot number, and the c_get_test cursor in populate_spec was changed so tests lacking an evaluation would not appear on the COA report. In get_order_params the lot number was initialized and call_spec_match was relocated inside the loop; later work replaced DECODE constructs with OR predicates. This last routine relates directly to the search term get_result_match_for_spec, which concerns matching a result to its governing specification.
Tables Accessed
The package reads and writes across quality, inventory, and order schemas via APPS synonyms. Quality tables include GMD_SPECIFICATIONS_B, GMD_QC_TESTS and GMD_QC_TESTS_B, GMD_RESULTS, and GMD_COMPOSITE_RESULTS, which together supply test definitions, specification limits, and measured values. Sampling context comes from GMD_SAMPLING_EVENTS. Inventory tables MTL_LOT_NUMBERS, MTL_ITEM_REVISIONS, MTL_SECONDARY_INVENTORIES, and MTL_PARAMETERS provide lot, revision, subinventory, and organization attributes appearing on the certificate. Order information is retrieved from OE_ORDER_HEADERS and OE_ORDER_HEADERS_ALL for customer-linked COA output. Customer identity and ship-to details are resolved through HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES.
Usage Notes
GMD_COA_DATA_OM_NEW is invoked during COA report generation, typically through the OPM quality concurrent programs and supporting forms that produce certificates for lots, orders, or shipments. Because it is a group-layer API rather than a form-level or low-level utility, it is intended for orchestrated batch execution; the presence of LOG_INITIALIZE and PRINTLN indicates that callers may enable logging for diagnostic purposes. It is referenced by one other package in the ETRM metadata, so customizations should avoid altering the public signatures of POPULATE_COA_DATA or POPULATE_HDR_TEXT. The package is compatible with EBS 12.1.1 and 12.2.2, and the last documented header revision predates those releases, so its behavior is stable across both versions.
-
PACKAGE BODY: APPS.GMD_COA_DATA_OM_NEW
12.1.1
-
PACKAGE BODY: APPS.GMD_COA_DATA_OM_NEW
12.2.2
-
PACKAGE BODY: APPS.GMD_SPEC_MATCH_MIG_GRP
12.2.2
-
PACKAGE BODY: APPS.GMD_SPEC_MATCH_GRP
12.2.2
-
PACKAGE BODY: APPS.GMD_SPEC_MATCH_MIG_GRP
12.1.1
-
PACKAGE BODY: APPS.GMD_SPEC_MATCH_GRP
12.1.1
-
PACKAGE: APPS.GMD_SPEC_MATCH_MIG_GRP
12.1.1
-
PACKAGE: APPS.GMD_SPEC_MATCH_MIG_GRP
12.2.2
-
PACKAGE: APPS.GMD_SPEC_MATCH_GRP
12.2.2
-
PACKAGE: APPS.GMD_SPEC_MATCH_GRP
12.1.1
-
APPS.GMD_SPEC_MATCH_MIG_GRP dependencies on GMD_SPEC_MATCH_MIG_GRP
12.2.2
-
APPS.GMD_SPEC_MATCH_MIG_GRP dependencies on GMD_SPEC_MATCH_MIG_GRP
12.1.1
-
APPS.GMD_COA_DATA_OM_NEW dependencies on GMD_API_PUB
12.1.1
-
APPS.GMD_COA_DATA_OM_NEW dependencies on GMD_API_PUB
12.2.2
-
APPS.GMD_COA_DATA_OM_NEW dependencies on GMD_SPEC_MATCH_GRP
12.2.2
-
APPS.GMD_COA_DATA_OM_NEW dependencies on GMD_SPEC_MATCH_GRP
12.1.1
-
APPS.GMD_COA_DATA_OM_NEW dependencies on FND_API
12.1.1
-
APPS.GMD_COA_DATA_OM_NEW dependencies on FND_API
12.2.2
-
APPS.GMD_COA_DATA_OM_NEW dependencies on FND_MSG_PUB
12.1.1
-
APPS.GMD_COA_DATA_OM_NEW dependencies on FND_MSG_PUB
12.2.2
-
APPS.GMD_SPEC_MATCH_GRP dependencies on GMD_SPEC_MATCH_GRP
12.2.2
-
APPS.GMD_SPEC_MATCH_GRP dependencies on GMD_SPEC_MATCH_GRP
12.1.1
-
APPS.GMD_SPEC_MATCH_GRP dependencies on GMD_API_PUB
12.1.1
-
APPS.GMD_SPEC_MATCH_GRP dependencies on GMD_API_PUB
12.2.2
-
APPS.GMD_SPEC_MATCH_GRP dependencies on FND_API
12.1.1
-
APPS.GMD_SPEC_MATCH_MIG_GRP dependencies on GMD_API_PUB
12.2.2
-
APPS.GMD_SPEC_MATCH_MIG_GRP dependencies on FND_API
12.1.1
-
APPS.GMD_SPEC_MATCH_MIG_GRP dependencies on GMD_API_PUB
12.1.1
-
APPS.GMD_SPEC_MATCH_MIG_GRP dependencies on FND_API
12.2.2
-
APPS.GMD_SPEC_MATCH_GRP dependencies on FND_API
12.2.2
-
APPS.GMD_SPEC_MATCH_MIG_GRP dependencies on FND_MSG_PUB
12.1.1
-
APPS.GMD_SPEC_MATCH_MIG_GRP dependencies on FND_MSG_PUB
12.2.2
-
APPS.GMD_SPEC_MATCH_GRP dependencies on FND_MSG_PUB
12.1.1
-
APPS.GMD_SPEC_MATCH_GRP dependencies on FND_MSG_PUB
12.2.2