Search Results ap_web_validate_util




Overview
Explore in AI Chat

Overview

AP_WEB_VALIDATE_UTIL is a utility package in the APPS schema that centralizes validation logic for the Oracle Payables Expense Report module, commonly known as Internet Expenses (OIE). The package supports the online expense report creation flow by validating header information, expense lines, cost centers, approvers, and report-level attributes before data is committed to the Payables interface tables. It functions as the validation layer of the OIE processing architecture, sitting between the web-based entry forms (OA framework and the older Web Expense forms) and the downstream database packages that populate the expense feed distributions consumed by Payables.

Because the package is classified as a utility (UTIL) API, it is not intended to be a user-facing or installable public interface. It supplies reusable validation routines that other OIE packages invoke during save, submit, and approval processing.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions within this package. Their documented responsibilities are as follows:

  • VALIDATEEXPLINE — Validates a single expense line, applying business rules to the line's core and descriptive attributes.
  • VALIDATEEXPLINES — Performs line validation across a collection of expense lines for a report.
  • VALIDATEEXPLINECOREFIELDS — Validates the mandatory or core fields of an expense line (for example, amounts, dates, and category attributes).
  • VALIDATEEXPLINECUSTOMFIELDS and VALIDATEEXPLINESCUSTOMFIELDS — Validate user-defined or descriptive flexfield values attached to individual expense lines or a set of lines.
  • MAPCOLUMNTOCUSTOMFIELDS — Maps incoming columns to the corresponding custom field definitions, supporting the custom field validation logic.
  • VALIDATECOSTCENTER — Validates the cost center entered against the expense report's distribution requirements.
  • VALIDATEAPPROVER — Validates the approver assigned to an expense report against the applicable approval rules.
  • VALIDATEREPORTHEADER — Validates report header attributes before the report can be submitted.
  • VALIDATEHEADERNOVALIDSESSION — Validates the report header when no valid session context is available, supporting batch or asynchronous invocation.
  • ISRECEIPTREQUIRED — Determines whether a receipt is required for a given expense line based on policy and amount thresholds.

No parameter lists are represented in the documented metadata; callers should reference the package specification for exact signatures.

Tables Accessed

The package references the following tables through APPS synonyms:

  • AP_EXPENSE_FEED_DISTS — The expense feed distribution table that carries validated expense line data into Payables.
  • AP_EXPENSE_REPORT_PARAMS_ALL — Stores expense report parameter definitions used during validation.
  • AP_POL_HEADERS — Payables policy headers that drive expense policies and receipt rules.
  • AP_SUPPLIERS — Supplier information, referenced when validating employee or supplier-related expense attributes.
  • AP_SYSTEM_PARAMETERS — System-level Payables options that influence validation behavior.
  • PLITBLM — The standard PL/SQL table of VARCHAR2 used for message handling.

Additionally, the package references data types and views including FND_CURRENCIES_VL and the OIE_PDM_* types, and depends on AP_WEB_DB_AP_INT_PKG, AP_WEB_DFLEX_PKG, AP_WEB_PARENT_PKG, and AP_WEB_UTILITIES_PKG.

Usage Notes

AP_WEB_VALIDATE_UTIL is invoked indirectly by the Internet Expenses application flow. The ETRM metadata shows it is referenced by four packages: AP_WEB_DISC_PKG, AP_WEB_OA_DISC_PKG, AP_WEB_OA_MAINFLOW_PKG, and AP_WEB_OA_PREFERENCES_PKG. These callers handle discovery (expense line lookups), the OA framework main flow, and user preferences, meaning validation occurs as part of normal save, submit, and approval operations.

The presence of VALIDATEHEADERNOVALIDSESSION indicates the package also supports contexts in which a valid user session is unavailable, such as background or concurrent processing. Customizations and extensions to OIE validation should avoid modifying this package directly; instead, Oracle supports extending expense validation through the descriptive flexfield and policy mechanisms the package already references. Because the package is an internal utility rather than a public API, direct calls from custom code are discouraged and should be replaced with supported APIs where possible.