Search Results ap_inv_aprvl_hist_s




Overview

APPS.AP_WORKFLOW_PKG is the Oracle Payables approval workflow engine. It is the PL/SQL package body that orchestrates the routing, notification, acceptance, rejection, and negotiation of accounts payable documents through Oracle Workflow. In Oracle E-Business Suite 12.1.1 and 12.2.2, this package acts as the integration layer between Payables invoice data and the Approval Management Engine (AME), determining which approvers are required for a given invoice, generating approval notifications, and updating approval history records as workflow activity progresses.

The package also supports supplier-facing negotiation and cancellation flows, including the processing of accept and reject responses from external suppliers and internal approvers who respond to purchase order matched and unmatched invoice events. Its status is documented as VALID in the APPS schema.

Key Procedures and Functions

The ETRM metadata documents 66 procedures and functions. The most significant include:

Tables Accessed

The package reads and writes the principal Payables invoice tables, including AP_INVOICES_ALL and AP_INVOICE_LINES_ALL for header and line data, and AP_INVOICE_DISTRIBUTIONS_ALL for distribution detail. Approval routing and history are persisted in AP_INV_APRVL_HIST, AP_INV_APRVL_HIST_ALL, and AP_INV_APRVL_HIST_S, with AP_APINV_APPROVERS and AP_APPROVERS_LIST_GT holding approver assignments and working sets. Holds and hold codes are accessed through AP_HOLDS_ALL and AP_HOLD_CODES. Supplier and party information comes from AP_SUPPLIERS, HZ_PARTIES, and HZ_PARTY_SITES, while FND_USER supports approver identity resolution. Negotiation history is captured in AP_NEGOTIATION_HIST_S.

Usage Notes

AP_WORKFLOW_PKG is invoked primarily by Oracle Workflow business events and notification response handlers during the invoice approval lifecycle, rather than being called directly by end users. It is referenced by six other packages and is central to the Payables approval workflow configuration. The references to AME_API, AME_API2, and AME_UTIL indicate that approval rule evaluation is delegated to the Approval Management Engine. Customizations that bypass this package risk leaving approval history (including AP_INV_APRVL_HIST_S) inconsistent, so extensions should invoke the documented procedures through supported workflow integration points.