Search Results p_receipt_num

Overview

GMD_QA_RCV_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the quality and receiving integration for process manufacturing. Its primary business function is to expose quality inspection and sampling data associated with receipts, purchase orders, and QA plans. The package bridges the receiving tables (RCV) and purchasing tables (PO) with the quality module tables (QA_PLANS, GMD_SAMPLING_EVENTS), allowing callers to retrieve disposition, quantity, and inspection result information for a given receipt, and to persist sampling collection details during inspection processing. It is classified as a PUB (public) API, meaning it is intended to be callable by external code, including Oracle Forms, concurrent programs, and customer extensions.

Key Procedures and Functions

The package defines four public program units, all documented in the ETRM metadata:

• GET_DISPOSITION — Returns a VARCHAR2 value representing the disposition associated with a receipt line. Callers supply purchase order, line, shipment, and receipt identifiers. Disposition indicates the quality status or usage decision (for example, accept, reject, or scrap) recorded for the receipt.
• GET_QUANTITY — Returns a NUMBER value representing the quantity tied to the given receipt context. This supports callers that need the received or inspected quantity for the identified purchase order, line, shipment, and receipt.
• GET_INSPECTION_RESULT — Returns a VARCHAR2 value describing the inspection result for the receipt. This allows downstream processes to determine whether the receipt passed, failed, or is pending quality evaluation.
• STORE_COLLECTION_DETAILS — A procedure that inserts sampling collection data into the GMD_SAMPLING_EVENTS table. The metadata notes it carries an autonomous transaction pragma, so its inserts commit independently of the caller's transaction. It accepts purchase order, line, shipment, and receipt identifiers along with plan name, collection ID, and occurrence number.

The user search term "p_receipt_num" corresponds to the shared receipt number parameter present in every documented signature, confirming that all four program units are keyed by the receipt number alongside PO, line, and shipment references.

Tables Accessed

According to the ETRM metadata, the package references the following tables through APPS synonyms:

• GMD_SAMPLING_EVENTS — Written by STORE_COLLECTION_DETAILS to record sampling event data.
• PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL — Read to resolve purchase order, line, and shipment context.
• QA_PLANS — Read to associate inspection and sampling plans with the receipt.
• RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS — Read to resolve receipt number, shipment, and receiving transaction details.

These tables support lookup of the quality outcome (disposition, quantity, inspection result) and persistence of sampling details.

Usage Notes

GMD_QA_RCV_PUB is typically invoked from receiving and quality forms, concurrent programs, and custom code that needs to query inspection results or store sampling collection details for a receipt. Because the functions return scalar values keyed by p_receipt_num (together with PO, line, and shipment), they are convenient for validation logic in Oracle Forms or for reporting queries. STORE_COLLECTION_DETAILS is suited to callers that must persist sampling data without disturbing their own transaction boundary, given its autonomous transaction pragma. The package is not referenced by any other package per the metadata, so it functions as a top-level entry point for external consumers rather than an internal dependency. Developers should call it as APPS and rely on the documented public signatures.