Search Results po_reqapproval_launch




Overview
Explore in AI Chat

Overview

PO_REQAPPROVAL_LAUNCH is an APPS-owned PL/SQL package within the Oracle E-Business Suite Purchasing module. Its role is to initiate and drive the Oracle Workflow approval process for requisitions, and to support downstream document generation associated with the requisition-to-purchase-order lifecycle. The package is classified as an "OTHER" API in the ETRM catalog, meaning it is not part of the formally published public API surface (such as the PL/SQL APIs used by external integrations), but rather serves as internal Oracle Workflow integration logic invoked by the application's own processing. The package presents a VALID status in both Oracle EBS 12.1.1 and 12.2.2, confirming it remains an active component of the requisition approval architecture across releases.

Key Procedures and Functions

The ETRM metadata documents two program units within the package:

  • POREQ_SELECTOR — This routine functions as the selection mechanism used when launch of the requisition approval workflow is required. In the standard requisition approval design, a selector is invoked to determine whether a given requisition should be submitted to the workflow and to route the item to the appropriate workflow process. Its presence here indicates that PO_REQAPPROVAL_LAUNCH acts as the entry point that the Purchasing application calls when a requisition is submitted for approval, electing the workflow that then performs the approval routing.
  • LAUNCH_CREATEPO_WF — This routine names the launch of the Create Purchase Order workflow. It is the mechanism by which the package initiates the Workflow process that converts an approved requisition into a purchase order document. This ties the requisition approval stream to the automatic document creation path used for the requisition-to-PO conversion.

The ETRM excerpt does not enumerate parameter lists for either program unit. Accordingly, the signatures are not documented in the available metadata and should be determined from the package specification in the target environment if custom invocation is contemplated.

Tables Accessed

Two tables are referenced through APPS synonyms:

  • PO_DOCUMENT_TYPES — Holds the definition of Purchasing document types, including requisitions and purchase orders. The package reads this table to establish the document type context required when launching the appropriate workflow, ensuring the correct process is started for the document in question.
  • PO_WF_ITEMKEY_S — The Workflow item key sequence for Purchasing. This sequence supplies the unique item key values that identify individual workflow items. The package accesses it to obtain the key used to start the requisition approval or Create Purchase Order workflow instance, so that the resulting workflow item can be tracked and correlated with its originating document.

Usage Notes

PO_REQAPPROVAL_LAUNCH is internal workflow plumbing rather than a general-purpose API. It is most commonly invoked indirectly: when a user submits a requisition for approval in the Purchasing forms, the application calls this package to select and start the appropriate Oracle Workflow process. Similarly, the Create Purchase Order workflow path is launched through this package following requisition approval, supporting autocreate processing.

The ETRM metadata records that the package is referenced by no other packages and that it has no dependent packages other than the STANDARD SYS package, indicating a relatively isolated dependency footprint. Because it is classified as OTHER, it is not intended as a supported extension point, and custom code should not call it directly. Oracle's supported integration approach for requisition approval and autocreate is to use the standard Purchasing APIs and the seeded workflow configuration rather than invoking this internal package. Modifications to workflow launches should be made through the standard Workflow Builder and Purchasing setup, preserving the package's role as an Oracle-managed internal component.