Search Results po_reqapproval_init1




Overview

APPS.PO_REQAPPROVAL_INIT1 is the core PL/SQL package body (source file POXWPA1B.pls) that implements the Oracle Workflow initialization logic for the Purchasing requisition approval process in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to prepare and launch the requisition approval workflow by assembling line, header, and document context, setting the appropriate authorization status, and handing control to the Workflow engine. The package is classified as OTHER in the ETRM repository, reflecting its role as a supporting utility rather than a public callable API.

Although the package name contains "INIT1," indicating a first-stage initialization routine, it contains substantial decision logic that governs whether a requisition can be submitted, whether it is pre-approved, and how status transitions are recorded in the action history. The package also reads profile options such as PO_SET_DEBUG_WORKFLOW_ON and POS_DEFAULT_PROMISE_DATE_ACK to control debug logging and promise date defaulting behavior.

Key Procedures and Functions

The package exposes 67 documented procedures and functions. The most significant clusters are:

Tables Accessed

Through APPS synonyms the package reads and writes several core tables. It selects requisition and purchasing header data from PO_HEADERS; records submission and approval events in PO_ACTION_HISTORY and PO_AME_APPROVALS_S; reads document configuration from PO_DOCUMENT_TYPES, PO_DOCUMENT_TYPES_ALL, and PO_DOC_STYLE_HEADERS; and writes draft rows to PO_DRAFTS and acceptance records to PO_ACCEPTANCES. It also reads MTL_CATEGORY_SETS_B for category context, FINANCIALS_SYSTEM_PARAMETERS for system-level defaults, FND_USER, FND_LANGUAGES, FND_NEW_MESSAGES, and FND_FORM_FUNCTIONS for user, language, and function metadata, HR_ALL_ORGANIZATION_UNITS_TL for organization names, and the local REF CURSOR GetRecHdr_csr against PO_REQUISITION_HEADERS_ALL.

Usage Notes

PO_REQAPPROVAL_INIT1 is invoked indirectly by the Oracle Purchasing Requisition Approval workflow rather than called directly from forms or concurrent programs. In practice it is triggered when a requisition is submitted for approval, when the workflow engine starts the initialization activity, and during status transitions managed by the approval process. The package is referenced by 40 other packages, indicating that it is consumed internally by related Purchasing and iProcurement components. Customizations should avoid direct invocation; instead, extend behavior through standard workflow attributes or supported APIs, since internal procedure signatures may change across patch levels.