Search Results set_rco_stat_approved

Overview

POR_AME_RCO_WF_PVT is a private PL/SQL package owned by the APPS schema within Oracle E-Business Suite. It provides the workflow callback layer that connects Oracle Purchasing's approval cycle to the Oracle Approvals Management (AME) engine, specifically for requisition change orders (RCO). The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema at runtime rather than as its definer, and it is classified as a private API in the ETRM 12.2.2 documentation, indicating that it is an internal implementation object rather than a supported integration point for customer extensions. Its header identifier records an applicationId constant of 201, confirming that AME transactions routed through this package are stamped with the Purchasing application identity. The package orchestrates the sequence of workflow events that occur after AME evaluates a requisition change order: identifying the next approvers, launching parallel approval branches, and processing the approval, rejection, or timeout responses returned by the workflow activity handlers.

Key Procedures and Functions

Eleven documented procedures constitute the package interface. All share a common workflow signature convention of itemtype, itemkey, actid, funcmode, and resultout, consistent with standard Oracle Workflow function activities. GET_NEXT_APPROVERS resolves the set of approvers that AME determines for the current requisition change order. LAUNCH_PARALLEL_APPROVAL produces the parallel approval branches when the approval routing requires simultaneous approvers rather than a sequential chain.

The response-handling procedures translate workflow outcomes into RCO state. PROCESS_RESPONSE_APPROVE, PROCESS_RESPONSE_REJECT, and PROCESS_RESPONSE_TIMEOUT handle the three terminal response types generated by approver actions or by the expiration of the response window. The latter is the object most closely associated with the search term process_response_timeout: it is the callback invoked when an approver does not act before the allotted response period elapses, allowing the workflow to advance without an explicit approval or rejection.

History and status procedures maintain the audit and state records. INSERT_ACTION_HISTORY creates the initial history row; UPDATE_ACTION_HISTORY_APPROVE, UPDATE_ACTION_HISTORY_REJECT, and UPDATE_ACTION_HISTORY_TIMEOUT each update that record with the disposition of the response. SET_RCO_STAT_APPROVED and SET_RCO_STAT_REJECTED write the final approved or rejected status onto the requisition change order itself.

Tables Accessed

Through APPS synonyms the package reads and writes several core tables. PO_REQUISITION_HEADERS_ALL and PO_DOCUMENT_TYPES supply the requisition change order and its document classification. PO_ACTION_HISTORY receives the approval audit trail manipulated by the INSERT_ACTION_HISTORY and UPDATE_ACTION_HISTORY_* procedures. PO_WF_ITEMKEY_S and WF_ITEMS provide the workflow item key mapping and workflow instance context required by the activity handlers. Approver resolution relies on FND_USER, PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_ASSIGNMENT_STATUS_TYPES to identify active employees and validate their assignment status. PLITBLM is referenced as a PL/SQL index-by table type used for internal collections.

Usage Notes

POR_AME_RCO_WF_PVT is not intended for direct invocation from forms, concurrent programs, or custom code. It is called by Oracle Workflow when the requisition change order approval process reaches the corresponding function activities; the itemtype and itemkey parameters are supplied by the workflow engine at runtime. The ETRM metadata confirms that no other packages reference it, reinforcing its role as a private callback layer rather than a shared utility. Because it is a private API, Oracle does not guarantee interface stability across patches or upgrades, and any customization should be implemented through supported AME configuration and workflow attributes rather than by modifying or directly calling these procedures. Diagnosing timeout behavior in RCO approvals typically involves inspecting WF_ITEMS, PO_ACTION_HISTORY, and the AME transaction records rather than altering this package.