Search Results fire_request

Overview

The APPS.GML_PO_CON_REQ package belongs to the Oracle Process Manufacturing (OPM) suite and serves as a bridge between the process manufacturing purchasing flow and the Oracle Purchasing application in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented owner is APPS, and it is classified as an "OTHER" API in the ETRM repository. The package header is declared with AUTHID CURRENT_USER, meaning that the procedures execute with the privileges of the calling user rather than the defining user.

The package is primarily responsible for submitting and resubmitting purchase order requisitions and interface records originating from the process manufacturing side (GML) into the standard Oracle Purchasing tables. It functions as a submission driver rather than a full business API, providing the mechanism by which records staged in the purchasing interface are pushed into the Purchasing application for processing.

Key Procedures and Functions

The package exposes two documented procedures:

• FIRE_REQUEST — The procedure that initiates or "fires" the request submission. Based on the naming and the package's overall purpose, it triggers the submission of pending process manufacturing requisition or purchasing interface records. This is the procedure most directly associated with the user search term "fire_request," indicating it is the entry point custom code or concurrent programs invoke to begin the request process.
• PO_RESUB — A resubmission procedure. It takes standard concurrent program parameters, including errbuf and retcode (for error and completion status reporting), along with date range inputs (v_from_date, v_to_date) and an optional purchase order number (v_po_no, defaulting to NULL). Its purpose is to reprocess or resubmit purchase orders that previously failed or need to be re-sent through the interface. The presence of errbuf/retcode confirms it is designed to run as a concurrent program.

A third procedure, RECV_RESUB, appears in the source only as a commented-out block. The documentation notes it is no longer used and was disabled to resolve invalid object errors; it is therefore not part of the active interface.

Tables Accessed

The package references the following tables through APPS synonyms:

• CPG_PURCHASING_INTERFACE — The staging table holding process manufacturing purchasing records awaiting transfer into Oracle Purchasing. The procedures read from this interface to determine what must be submitted or resubmitted.
• PO_HEADERS_ALL — The core Purchasing table storing purchase order header information. It is written to or validated when purchase orders are created or resubmitted.
• PO_LINE_LOCATIONS_ALL — The Purchasing table holding purchase order line and shipment/ location details. The package interacts with it to ensure complete PO structures are created or corrected during submission.

Usage Notes

GML_PO_CON_REQ is typically invoked through concurrent programs or custom integrations rather than directly by end users. The PO_RESUB procedure's errbuf and retcode parameters confirm it is registered as a concurrent program executable, allowing it to report completion status through the standard concurrent manager framework. The FIRE_REQUEST procedure serves as the direct call point for initiating request submission, frequently referenced in custom scripts or workflow logic where the search term "fire_request" applies. Because the package is AUTHID CURRENT_USER, the invoking user must possess appropriate privileges on the underlying Purchasing tables and interface objects. The documented metadata also indicates the package is referenced by one other package, suggesting it is a shared utility within the OPM purchasing integration layer. Administrators should be aware of its date-range and optional PO number parameters when scheduling the resubmission concurrent program to control scope and avoid reprocessing already-submitted orders.