Search Results update_approval_list_response

Overview

PO_APPROVAL_LIST_WF1S is the Oracle Workflow-enabled PL/SQL package body (APPS schema) that implements the approval list engine for the Oracle Purchasing document approval workflow in Oracle E-Business Suite 12.1.1 and 12.2.2. Its source file, POXWAL1B.pls, dates from the original Purchasing workflow design (header revision 120.2, dated 2007) and remains a core component of the PO Approval hierarchy in both releases. The package is responsible for constructing, interrogating, and maintaining the ordered list of approvers that a purchasing document (requisition, purchase order, release, or change order) must traverse before it is authorized. It supports both forward and backward routing through the list, handles approver substitutions and invalid approvers, manages document changes that force list reconstruction, and records approver actions into the action history table.

The package is tightly coupled to Oracle Workflow: it reads workflow item attributes and activity definitions to determine approval routing, and it writes notifications and activity history as processing proceeds. A debug mechanism controlled by the profile option PO_SET_DEBUG_WORKFLOW_ON (read at package initialization into g_po_wf_debug) allows diagnostic tracing through PO_WF_DEBUG_PKG.

Key Procedures and Functions

ETRM documents twenty callable units in this package. The list-management routines include DOES_APPROVAL_LIST_EXIST, which determines whether a list has already been generated for a document, and FIND_APPROVAL_LIST, which locates the applicable list definition. BUILD_DEFAULT_APPROVAL_LIST generates the initial default approver sequence, while IS_APPROVAL_LIST_EMPTY tests whether any approvers remain to be processed. The rebuild family handles exceptions to the normal flow: REBUILD_LIST_FORWARD reconstructs the remaining approvers when routing moves ahead, REBUILD_LIST_DOC_CHANGED responds to modifications in the underlying document, and REBUILD_LIST_INVALID_APPROVER recovers when an assigned approver is no longer valid. GET_NEXT_APPROVER advances the engine to the following approver in sequence.

Action-history maintenance is handled by INSERT_ACTION_HISTORY and the UPDATE_ACTION_HISTORY_* procedures: UPDATE_ACTION_HISTORY_APPROVE, UPDATE_ACTION_HISTORY_TIMEOUT, UPDATE_ACTION_HISTORY_APP_FWD, UPDATE_ACTION_HISTORY_FORWARD, and UPDATE_ACTION_HISTORY_REJECT, each recording the corresponding approver outcome. UPDATE_APPROVAL_LIST_RESPONSE and UPDATE_APP_LIST_RESP_SUCCESS persist the approver's response back to the approval list; these are the routines most directly associated with the search term "update_approval_list_response". GET_APPROVAL_RESPONSE retrieves the recorded response. INSERT_RES_ACTION_HISTORY and CREATE_ATTACH_INFO_TEMP support result history and temporary attachment data, and IS_DOCUMENT_MANAGER_ERROR_1_2 inspects the workflow item attribute DOC_MGR_ERROR_NUM (returning 'Y' for error numbers 1 or 2) to detect document manager failures.

Tables Accessed

The package references several tables through APPS synonyms. PO_DOCUMENT_TYPES supplies the document type definitions that govern approval behavior and routing. WF_ITEMS, WF_ACTIVITIES, and WF_PROCESS_ACTIVITIES provide the workflow item, activity, and process definitions used to determine approver sequence and activity outcomes. WF_NOTIFICATIONS is used to create, update, and close the approval notifications delivered to approvers. PLITBLM (the PL/SQL index-by table of long values) is referenced for bulk data handling within the package.

Usage Notes

PO_APPROVAL_LIST_WF1S is not intended for direct invocation by end users. It is called by Oracle Purchasing's document approval workflow, driven from the Purchasing forms when a document is submitted for approval, and by the workflow background processes that route notifications and process approver responses. It is also referenced by one other package documented in ETRM, indicating shared use within the approval workflow layer. Customizations should avoid calling these procedures directly; instead, extensions should integrate through the supported workflow activity functions and the standard notification response mechanism. Debugging is enabled only by setting the PO_SET_DEBUG_WORKFLOW_ON profile option to 'Y', which causes progress markers to be written through PO_WF_DEBUG_PKG.