Search Results get_req_attributes

Overview

PO_REQAPPROVAL_INIT1 is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that serves as the primary entry point for initiating and managing the Oracle Workflow approval process for purchasing documents. Its responsibilities cover requisitions, purchase orders, blanket agreements, and related document types generated within the PO module. The package orchestrates the creation of workflow item keys, the population of item attributes, and the launch of the approval workflow process itself, thereby connecting purchasing transaction state changes to the Oracle Workflow engine and the AME (Approval Management Engine) hierarchy.

The package header dates back to 1997 and has been maintained through releases supporting EBS 12.1.1 and 12.2.2, with notable changes including the default value of the PrintFlag parameter being set to 'N' rather than NULL. Later enhancements introduced retroactive price change handling and organization assignment change support, reflecting the evolving complexity of procurement approvals.

Key Procedures and Functions

The documented interface exposes 67 procedures and functions. The central routine is START_WF_PROCESS, which generates the workflow item key, establishes the item attributes, and starts the approval workflow process. Its design accommodates the originating action, document identity, preparer, submitter, forwarding attributes, default approval path, notes, and output preferences such as print, fax, and email flags, along with sourcing rule and retroactive price change indicators.

Supporting routines fall into several functional groups:

• Workflow startup and context: SET_STARTUP_VALUES and GET_MULTIORG_CONTEXT prepare the session and organizational context required before the workflow is launched.
• Document status management: SET_DOC_STAT_PREAPPROVED, SET_DOC_STAT_PREAPPROVED1, SET_DOC_STAT_INPROCESS, and SET_DOC_TO_ORIGINALSTAT transition the purchasing document between pre-approved, in-process, and original states.
• Document and user resolution: GET_REQ_ATTRIBUTES, GET_USER_NAME, and GET_EMPLOYEE_ID retrieve requisition attributes and resolve user and employee identities used in approval routing.
• Eligibility and verification: CAN_OWNER_APPROVE, IS_SUBMITTER_SAME_AS_PREPARER, IS_DOC_PREAPPROVED, and REGISTER_DOC_SUBMITTED determine whether approval is required or bypassed.
• Action history and outcomes: INS_ACTIONHIST_SUBMIT, SET_END_VERIFYDOC_FAILED, SET_END_VERIFYDOC_PASSED, SET_END_VALID_ACTION, and SET_END_INVALID_ACTION record submission history and set terminal workflow outcomes. ENCUMB_ON_DOC_UNRESERVED handles encumbrance activity when documents are unreserved.

Tables Accessed

The package interacts with a broad set of purchasing and foundation tables through APPS synonyms. PO_HEADERS, PO_DRAFTS, PO_ACTION_HISTORY, PO_ACCEPTANCES, PO_DOCUMENT_TYPES, PO_DOCUMENT_TYPES_ALL, PO_DOC_STYLE_HEADERS, and PO_AME_APPROVALS_S supply document definition, approval routing, and historical action data. MTL_CATEGORY_SETS_B supports category validation, HR_ALL_ORGANIZATION_UNITS_TL provides organization context, and FND_USER, FND_FORM_FUNCTIONS, FND_LANGUAGES, and FND_NEW_MESSAGES resolve user, function, language, and message information. FINANCIALS_SYSTEM_PARAMETERS supplies system-level defaults that govern document behavior.

Usage Notes

PO_REQAPPROVAL_INIT1 is invoked primarily by the Purchasing forms and by internal PO module code when a user submits a requisition or purchase order for approval, conditionally submits, forwards, or re-submits a document, or applies retroactive price changes to releases. It is also referenced by 40 other packages within the APPS schema, indicating its role as a shared approval-launching service. Because the START_WF_PROCESS signature includes explicit print, fax, and email flags and is defaulted for backward compatibility, callers pass output preferences at submission time. Customizations that extend approval behavior should call the documented procedures rather than attempting to start the workflow directly, ensuring that action history, document status, and AME routing remain consistent.