Search Results ap_web_expense_cust_wf




Overview
Explore in AI Chat

Overview

AP_WEB_EXPENSE_CUST_WF is an Oracle Application Object Library package owned by the APPS schema that provides the customization and workflow integration layer for Oracle Payables' Internet Expenses (OIE) module in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Within the EBS architecture, Internet Expenses permits employees to enter work-related expense reports through a self-service web interface and route them through Oracle Workflow for validation and approval. The AP_WEB_EXPENSE_CUST_WF package exposes the extension hooks by which implementers can override or augment the standard behavior of that workflow. Its procedures function as callable activities embedded in the seeded expense report workflow, allowing customers to inject site-specific validation rules, custom approver determination logic, authority verification, and downstream data transfer routines without modifying Oracle's base code. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer, consistent with EBS custom code conventions. The header comment indicates the shipped version is 115.4, with a last modification date of November 14, 2002, reflecting the longevity of this interface across multiple EBS releases.

Key Procedures and Functions

The package documents seven callable units, each corresponding to a defined extension point in the expense report approval workflow.

  • CustomValidateExpenseReport — A workflow-callable procedure that serves as the entry point for adding customer-defined validation to an expense report as it moves through the approval process.
  • DoCustomValidation — The procedure that performs the actual validation logic against a specific report, accepting the report header identifier and returning an error message where validation fails.
  • FindApprover — A workflow-callable procedure that determines the appropriate approver for an expense report, enabling substitution of custom approval routing in place of the standard hierarchy.
  • VerifyAuthority — A workflow-callable procedure that confirms whether a designated approver holds sufficient authority to approve the report at its current approval amount.
  • HasAuthority — A boolean function that encapsulates the authority test itself, accepting the approver identity, the document's cost center, and the approval amount to determine whether approval rights exist.
  • CustomDataTransfer — A workflow-callable procedure invoked to move or post expense report data as part of a customer-specific integration, such as transfer to an external system.
  • DetermineMgrInvolvement — A workflow-callable procedure that establishes whether and how a manager participates in the approval chain for a given expense report.

Tables Accessed

The package accesses a limited set of documented objects through APPS synonyms. FND_NEW_MESSAGES is the Oracle Application Object Library repository used for message retrieval and error reporting; the validation procedures rely on it to surface user-facing messages when custom rules fail. PER_ASSIGNMENT_STATUS_TYPES belongs to Oracle HRMS and defines the valid assignment statuses for employees; it is referenced in the context of approver determination and manager involvement logic, where the assignment status of a prospective approver or manager must be evaluated. No other tables are documented in the ETRM metadata for this package.

Usage Notes

AP_WEB_EXPENSE_CUST_WF is invoked indirectly rather than directly. Its procedures are registered as workflow activity functions within the Internet Expenses expense report workflow, so they execute automatically as a report advances through validation and approval states. Implementers who need to add site-specific validation, alter approver selection, or transfer expense data to another application customize the body of these procedures, and Oracle Workflow calls them at the corresponding nodes. The package is also referenced by one other APPS package, indicating it participates in a larger internal call graph. Because the procedures follow the standard Workflow function signature conventions and are declared in the APPS schema, they may additionally be called from custom PL/SQL or concurrent programs, but such direct invocation is atypical. Changes should be made only through the supported customization mechanism, since the package is a seeded Oracle object and may be overwritten during patching.