Search Results get_transaction_type
Overview
GML_PO_CON_REQ is a PL/SQL package body owned by APPS in the Oracle E-Business Suite, classified as OTHER in the ETRM repository. It belongs to the Process Manufacturing (OPM/GML) integration layer that bridges Oracle Purchasing and the GEMMS (Global Enterprise Manufacturing Management System) environment. Its central responsibility is to synchronize purchasing documents between the two systems: standard and planned purchase orders and releases flow from Oracle to GEMMS, while receipts flow from GEMMS back into Oracle. The package header comment identifies GMLPORCO.pls as the concurrent program used for "Synchronizing POs RCPT," and the executable is fired through FND_SUBMIT_REQUEST as a SQL file that opens the Common Purchasing Log File in the directory named in the init.ora, displaying that log in the standard Concurrent Manager request log.
Key Procedures and Functions
- FIRE_REQUEST — The primary documented procedure. It submits the synchronization concurrent request programmatically using FND_REQUEST.SET_MODE and FND_CONCURRENT.GET_REQUEST_STATUS, checking the status of the previously submitted run (identified by the concurrent program short name GMLPORCV in application GML) before launching a new one. The logic deliberately suppresses a fresh submission when the prior request is still in PENDING or RUNNING phase with NORMAL development status, because a still-active request will itself pick up the current set of interface rows. A separate branch handles the INACTIVE / NO_MANAGER condition. The procedure declares local variables for request id, call status, request phase, request status, development phase, development status, log line, and error message, and is associated with the header revision $Header: GMLPORCB.pls 115.13 2002/12/04, originally authored 29-JAN-99 by Tony Ricci.
- PO_RESUB — The second documented procedure, provided for resubmission handling of purchase order data through the same integration flow. It supports re-driving the interface when a prior cycle must be repeated.
Tables Accessed
- CPG_PURCHASING_INTERFACE — The staging interface table that carries purchase order and receipt records between Oracle and GEMMS. This is the core synchronization surface the package operates against.
- PO_HEADERS_ALL — The Purchasing header table, consulted for purchase order header details that must be synchronized or referenced during submission.
- PO_LINE_LOCATIONS_ALL — The Purchasing shipment/line location table, providing the scheduling and receipt-relevant detail required for the outbound document set.
Usage Notes
GML_PO_CON_REQ is not intended for direct interactive use. It is invoked indirectly when the concurrent program that calls FIRE_REQUEST is submitted, and the request-status guard ensures only one synchronization cycle runs at a time. The package is referenced by one other package, confirming its role as a shared integration utility rather than an end-user API. The search term "get_transaction_type" does not correspond to a documented procedure in this package; the two exposed program units in the ETRM metadata are FIRE_REQUEST and PO_RESUB. Customizations should respect the existing single-flight behavior in FIRE_REQUEST rather than issuing parallel submissions, since concurrent execution would duplicate processing of CPG_PURCHASING_INTERFACE rows. Behavior is consistent across EBS 12.1.1 and 12.2.2, as the package is a legacy OPM component carried forward without structural change.
-
PACKAGE BODY: APPS.GML_PO_CON_REQ
12.2.2
-
PACKAGE BODY: APPS.GML_PO_CON_REQ
12.1.1
-
PACKAGE BODY: APPS.INVTTMTX
12.2.2
-
PACKAGE BODY: APPS.INVTTMTX
12.1.1
-
PACKAGE BODY: APPS.AMS_BOM_PVT
12.1.1
-
PACKAGE BODY: APPS.AMS_BOM_PVT
12.2.2
-
PACKAGE BODY: APPS.EC_XML_UTILS
12.1.1
-
PACKAGE BODY: APPS.EC_XML_UTILS
12.2.2
-
PACKAGE: APPS.PQH_GEN_FORM
12.1.1
-
PACKAGE: APPS.PQH_GEN_FORM
12.2.2
-
PACKAGE BODY: APPS.WIP_DEFAULT_SHOPFLOORMOVE
12.1.1
-
PACKAGE BODY: APPS.WIP_DEFAULT_RES
12.1.1
-
PACKAGE BODY: APPS.WIP_DEFAULT_SHOPFLOORMOVE
12.2.2
-
PACKAGE BODY: APPS.WIP_DEFAULT_RES
12.2.2
-
APPS.PON_AUCTION_PKG dependencies on PON_AUC_DOCTYPES
12.1.1
-
APPS.PON_AUCTION_PKG dependencies on PON_AUC_DOCTYPES
12.2.2
-
APPS.INVTTMTX dependencies on MFG_LOOKUPS
12.2.2
-
APPS.INVTTMTX dependencies on MTL_SUBINVENTORIES_ALL_V
12.2.2
-
APPS.INVTTMTX dependencies on MFG_LOOKUPS
12.1.1
-
APPS.JAI_OM_WSH_PKG dependencies on OE_TRANSACTION_TYPES_TL
12.2.2
-
APPS.AMS_BOM_PVT dependencies on FND_MSG_PUB
12.2.2
-
APPS.AMS_BOM_PVT dependencies on FND_MSG_PUB
12.1.1
-
APPS.INVTTMTX dependencies on MTL_SUBINVENTORIES_ALL_V
12.1.1
-
APPS.JAI_OM_WSH_PKG dependencies on JAI_CMN_FIN_YEARS
12.1.1
-
APPS.JAI_OM_WSH_PKG dependencies on OE_TRANSACTION_TYPES_TL
12.1.1
-
APPS.JAI_OM_WSH_PKG dependencies on JAI_CMN_FIN_YEARS
12.2.2
-
APPS.GML_PO_CON_REQ dependencies on PO_HEADERS_ALL
12.1.1
-
APPS.GML_PO_CON_REQ dependencies on PO_HEADERS_ALL
12.2.2
-
APPS.PON_AUCTION_PKG dependencies on PON_AUC_DOCTYPES
12.2.2
-
APPS.PON_AUCTION_PKG dependencies on PON_AUC_DOCTYPES
12.1.1
-
APPS.GML_PO_CON_REQ dependencies on PO_LINE_LOCATIONS_ALL
12.1.1
-
APPS.GML_PO_CON_REQ dependencies on PO_LINE_LOCATIONS_ALL
12.2.2
-
APPS.EC_XML_UTILS dependencies on EC_XML_UTILS
12.1.1
-
APPS.EC_XML_UTILS dependencies on EC_XML_UTILS
12.2.2
-
APPS.EC_XML_UTILS dependencies on EC_DEBUG
12.1.1
-
APPS.EC_XML_UTILS dependencies on EC_DEBUG
12.2.2
-
PACKAGE: APPS.PON_AUCTION_PKG
12.1.1
-
PACKAGE: APPS.PON_AUCTION_PKG
12.2.2
-
PACKAGE BODY: APPS.PQH_GEN_FORM
12.2.2
-
PACKAGE BODY: APPS.PQH_GEN_FORM
12.1.1
-
APPS.AMS_BOM_PVT dependencies on FND_API
12.1.1
-
APPS.AMS_BOM_PVT dependencies on FND_API
12.2.2
-
APPS.WIP_DEFAULT_SHOPFLOORMOVE dependencies on FND_API
12.1.1
-
APPS.WIP_DEFAULT_SHOPFLOORMOVE dependencies on FND_API
12.2.2
-
APPS.WIP_DEFAULT_RES dependencies on FND_API
12.2.2
-
APPS.WIP_DEFAULT_RES dependencies on FND_API
12.1.1
-
PACKAGE BODY: APPS.JAI_OM_WSH_PKG
12.1.1
-
PACKAGE BODY: APPS.JAI_OM_WSH_PKG
12.2.2
-
PACKAGE BODY: APPS.PON_AUCTION_PKG
12.1.1
-
PACKAGE BODY: APPS.PON_AUCTION_PKG
12.2.2