Search Results populate_coa_data

Overview

GMD_COA_DATA_NEW is a PL/SQL package in the Oracle E-Business Suite Process Manufacturing (Process Execution) module. Its declared purpose, per the source header, is to "gather COA data via business rules." COA refers to a Certificate of Analysis, the quality document generated for a manufactured or shipped item that records specification compliance and result values. The package assembles the header, detail, and text payloads needed to produce such a certificate, sourcing that data across the order, customer, inventory, lot, and quality schemas.

The package is declared with AUTHID CURRENT_USER and is classified as an OTHER API in the ETRM 12.2.2 metadata. The header comment identifies the API name as GMD_COA_DATA_NEW, type "Group," at version 2.1. Its role is strictly as a data-gathering API: the comment states the package "assumes validation is done in calling program/form," so callers are responsible for verifying that input parameters are valid before invocation. The business rules that drive the selection of quality data operate across a customer, global, and item-lot hierarchy, which allows COA content to be resolved from the most specific applicable specification.

Key Procedures and Functions

• POPULATE_COA_DATA — The main entry point, referenced in the source header as the package's principal procedure. It accepts a standard EBS API parameter block (p_api_version, p_init_msg_list, p_commit, p_validation_level) together with an rec_param record of the COA parameters. It returns the standard return status and message outputs (x_return_status, x_msg_count, x_msg_data) plus three OUT collections: tbl_hdr (COA header rows), tbl_dtl (COA detail rows), and the text tables tbl_spec_text and tbl_rslt_text for specification and result narrative. This is the procedure called by the user search term "populate_coa_data."
• DUMP_TO_DB_TABLES — The second documented procedure, which persists the gathered collections into the COA database tables. It complements POPULATE_COA_DATA by moving the in-memory header, detail, and text structures into their permanent storage.

Tables Accessed

• Order and customer data: OP_ORDR_HDR, OP_ORDR_DTL, OP_CUST_MST, and OP_BILL_LAD supply order number, ship date, customer identity, and bill-of-lading references that identify the transaction a certificate applies to.
• Inventory and lot data: IC_ITEM_MST, IC_LOTS_MST, and IC_WHSE_MST provide item, lot, sublot, and warehouse descriptors so each COA line is tied to the correct material and location.
• Quality data: GMD_SPECIFICATIONS_B, GMD_SPEC_TESTS_B, GMD_QC_TESTS, GMD_QC_TESTS_B, and GMD_RESULTS hold the specification, test, and analytical result values selected by the COA business rules.
• COA output tables: GMD_COA_HEADERS and GMD_COA_DETAILS are the destination tables written by DUMP_TO_DB_TABLES. The QC_TEXT_TBL structure supports the specification and result text payloads.

Usage Notes

Because the package is referenced by no other documented package, it is not part of a published dependency chain; it is invoked directly. Typical callers are the COA generation forms in Process Manufacturing and any concurrent program or custom code that builds certificates of analysis. Callers must supply the parameter record, honor the commit and validation-level flags, and interrogate x_return_status together with the message outputs before consuming the returned collections. The AUTHID CURRENT_USER declaration means privileges are evaluated against the invoking schema, so the calling user must hold appropriate grants on the referenced synonyms.