Search Results ap_tolerances




Overview
Explore in AI Chat

Overview

AP_TOLERANCES is a read-only database view owned by the APPS schema in Oracle E-Business Suite Payables (AP). It exposes the tolerance template definitions that govern invoice validation matching and hold resolution in Oracle Payables and Oracle Purchasing. In ETRM 12.1.1 and 12.2.2 the object is documented with a status of VALID and carries the description AP_TOLERANCE. Functionally, the view presents the same column set as its underlying base object and is therefore used primarily for reporting, integration extraction, and diagnostic queries rather than for transactional data entry.

Tolerance templates determine the acceptable variances applied during invoice matching across price, quantity, tax, shipment amount, rate amount, and total amount dimensions. Because the view is read-only, all maintenance of tolerance templates is performed against the base table through the Payables setup forms; the view supplies a stable, query-friendly interface for solutions that need to read tolerance configuration without writing to it.

Underlying Base Objects

The documented definition of AP_TOLERANCES is a straight projection over AP_TOLERANCE_TEMPLATES, which is referenced through a synonym. Every column in the view originates from that single base object; no joins, unions, aggregations, or computed expressions are present in the view text. The projection includes the full set of tolerance attributes plus the standard EBS WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY) that support audit and incremental extraction. Because the dependency is one-to-one, each row returned by AP_TOLERANCES corresponds to exactly one tolerance template record, and the TOLERANCE_ID values are identical between the view and the base object.

Key Columns

  • TOLERANCE_ID — Primary key and the identifier most frequently used in joins to other Payables objects; the user search term "tolerance_id" typically resolves to this column.
  • TOLERANCE_NAME — User-defined name of the tolerance template as displayed in the Payables setup windows.
  • TOLERANCE_TYPE — Classification of the template, indicating the matching or hold context in which the tolerance applies.
  • PRICE_TOLERANCE, QUANTITY_TOLERANCE, QTY_RECEIVED_TOLERANCE — Variance allowances for invoice price and ordered versus received quantities during matching.
  • MAX_QTY_ORD_TOLERANCE, MAX_QTY_REC_TOLERANCE — Maximum quantity tolerances expressed against ordered and received quantities.
  • TAX_TOLERANCE, TAX_TOL_AMT_RANGE — Tax variance allowance and the associated amount range for tax tolerance checks.
  • SHIP_AMT_TOLERANCE, RATE_AMT_TOLERANCE, TOTAL_AMT_TOLERANCE — Amount-based tolerances applied to shipment, rate, and invoice total comparisons.
  • DESCRIPTION — Free-text description of the template.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for change tracking and delta loads.

Common Use Cases and Queries

Typical scenarios include auditing which tolerance template governs a hold, reconciling tolerance configuration between environments, and extracting setup data for reporting or integration. A common lookup by identifier is:

  • SELECT tolerance_id, tolerance_name, price_tolerance, quantity_tolerance, total_amt_tolerance FROM ap_tolerances WHERE tolerance_id = :p_tolerance_id;
  • SELECT tolerance_name, tax_tolerance, tax_tol_amt_range FROM ap_tolerances WHERE tolerance_type = :p_type ORDER BY tolerance_name;
  • SELECT tolerance_id, tolerance_name, last_update_date, last_updated_by FROM ap_tolerances WHERE last_update_date >= :p_since; for incremental extraction.

Because the object is a simple projection, queries against it return the same results as equivalent queries against AP_TOLERANCE_TEMPLATES, while benefiting from the abstracted view name and consistent privileges in the APPS schema.