Results for “ap_web_oa_active_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_WEB_OA_ACTIVE_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It supports the Oracle Payables and Internet Expenses (OIE) workflow infrastructure, specifically the determination and resolution of approval information, workflow status, and payment status for expense reports processed through the Oracle Approval Management (OAM) and Oracle Workflow engine. Within EBS 12.1.1 and 12.2.2, this package is a supporting utility object rather than a public API; the ETRM classification of the package body is "OTHER," reflecting its role as internal infrastructure invoked by other components rather than a published integration interface.

The package is primarily concerned with querying the state of an expense report as it traverses its approval and payment lifecycles, and with identifying the current approver, the approver's name, the expenses administrator, and the last notification activity generated by the workflow engine. Because expense approval in Oracle Internet Expenses is driven by Oracle Workflow, the package cross-references both Payables transactions and Workflow runtime tables.

Key Procedures and Functions

The documented package exposes nine procedures and functions:

• GETAPPROVERNAME — Returns the display name of the approver associated with an expense report's approval chain.
• GETAPAPPROVER — Retrieves the Payables-level approver identity for a given report or transaction.
• GETEXPENSESADMIN — Resolves the expenses administrator, typically the individual or role designated to administer expense policies and approvals.
• GETWFLASTNOTIFICATIONACTIVITY — Identifies the most recent notification activity dispatched by the workflow engine for the expense report, useful for determining where an item currently resides in its approval flow.
• GETREPORTSTATUSCODE — Returns the status code describing the expense report's current state.
• GETBOTHPAYSTATUSCODE — Returns the payment status code relevant to the report's disbursement state.
• GETREPORTSTATUS — Returns the human-readable report status derived from the underlying code.
• GETCURRENTAPPROVER — Determines the approver presently responsible for acting on the report.
• GETINCLUDENOTIFICATION — Evaluates whether a notification should be included for the current workflow context.

These routines collectively provide the lookup and resolution layer used by approval-related forms and workflow function activities. Parameter lists are not documented in the ETRM metadata and are intentionally not reproduced here.

Tables Accessed

The package references the following tables through APPS synonyms:

• AP_EXPENSE_REPORT_HEADERS and AP_EXPENSE_REPORT_HEADERS_ALL — the header records of expense reports, providing report identity and status context.
• AP_INVOICES_ALL — the invoice records created from approved expense reports.
• AP_PAYMENT_SCHEDULES_ALL — payment schedule lines used to derive payment status codes.
• AP_CREDIT_CARD_TRXNS — credit card transactions associated with expense lines where relevant.
• AP_LOOKUP_CODES — lookup values used to translate status codes into meaningful descriptions.
• WF_ITEM_ACTIVITY_STATUSES and its view WF_ITEM_ACTIVITY_STATUSES_V — Workflow runtime activity status used to locate the current and last activity.
• WF_ITEM_ATTRIBUTE_VALUES — Workflow item attributes carrying approval context.
• WF_PROCESS_ACTIVITIES and WF_ROLES — process activity definitions and role resolution for approver identification.

Usage Notes

AP_WEB_OA_ACTIVE_PKG is invoked indirectly through Oracle Internet Expenses approval workflows, the Expense Report and Approval forms, and Workflow function activities rather than being called directly by end users. The ETRM metadata records that it is referenced by twelve other packages, confirming its role as shared infrastructure within the AP Web/OIE stack. It is not referenced by any database object outside that dependency set.

Because the package body is VALID and owned by APPS, customizations should avoid modifying it directly; extensions should instead wrap or extend behavior at higher layers. When diagnosing approval routing or status display issues in EBS 12.1.1 or 12.2.2, tracing the Workflow activity and role queries within this package is a common investigation step.