Search Results ap_tolerance_templates_u1

Overview

AP.AP_TOLERANCE_TEMPLATES is a foundational Oracle Payables configuration table that stores named tolerance templates used during Invoice Validation. Each template defines a set of acceptable variance thresholds—expressed as percentages or amounts—that Oracle Payables applies when matching invoices to purchase orders, receipts, and other source documents. When an invoice or match exceeds a configured threshold, Invoice Validation places the document on hold so that an approver can review the discrepancy before payment or posting proceeds.

The table resides in the AP schema under the APPS_TS_TX_DATA tablespace and is registered as FND Design Data SQLAP.AP_TOLERANCE_TEMPLATES. It is a low-volume, reference-oriented object whose rows are reused across many transactional entities. Under a heuristic Data Vault classification, the FK profile (references only to FND_USER and FND_LOGINS for the standard Who columns, with no upstream business-key dependencies) suggests this table is best modeled as a satellite-leaning reference table, holding descriptive tolerance attributes keyed by a surrogate identifier.

Key Information Stored

The primary key is TOLERANCE_ID, a NUMBER(15) surrogate that is also the single column of the unique index AP_TOLERANCE_TEMPLATES_U1. Business users typically identify a template by TOLERANCE_NAME (VARCHAR2(255)), which together with DESCRIPTION provides the human-readable label and explanation. The substantive configuration data resides in the tolerance measure columns:

• PRICE_TOLERANCE and QUANTITY_TOLERANCE — percentage limits for price and quantity variance during matching.
• QTY_RECEIVED_TOLERANCE, MAX_QTY_ORD_TOLERANCE, and MAX_QTY_REC_TOLERANCE — thresholds governing receipt-based quantity and maximum ordered/received quantities.
• TAX_TOLERANCE and TAX_TOL_AMT_RANGE — tax variance percentage and the amount range over which tax tolerance applies.
• SHIP_AMT_TOLERANCE, RATE_AMT_TOLERANCE, and TOTAL_AMT_TOLERANCE — shipment amount, exchange rate amount, and total invoice amount variance limits.
• TOLERANCE_TYPE — categorizes the template for selection logic.
• Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) provide auditability and link to FND_USER and FND_LOGINS.

Common Use Cases and Queries

Tolerance templates are assigned at the supplier-site level and as a system default, so the most frequent query pattern is resolving which template governs a given supplier or the entire ledger. A typical lookup:

• Selecting a template for review: SELECT tolerance_id, tolerance_name, price_tolerance, quantity_tolerance, tax_tolerance FROM ap.ap_tolerance_templates WHERE tolerance_id = :p_id;
• Listing all templates used as supplier defaults: SELECT t.tolerance_name, s.vendor_site_code FROM ap.ap_tolerance_templates t, ap.ap_supplier_sites_all s WHERE s.tolerance_id = t.tolerance_id;
• Identifying the system-wide default: SELECT tolerance_id, tolerance_name FROM ap.ap_tolerance_templates WHERE tolerance_id = (SELECT tolerance_id FROM ap.ap_system_parameters_all);
• Auditing configuration changes by joining LAST_UPDATED_BY to FND_USER and filtering on LAST_UPDATE_DATE.

Reporting use cases include tolerance impact analysis (which suppliers would be most affected by tightening price tolerance), migration validation when moving templates between environments, and reconciliation of the supplier interface stage table against production site assignments.

Related Objects

AP_TOLERANCE_TEMPLATES sits at the center of several Payables relationships via TOLERANCE_ID:

• AP_SYSTEM_PARAMETERS_ALL — stores the ledger-level default template through TOLERANCE_ID.
• AP_SUPPLIER_SITES_ALL — assigns a template to each supplier site via TOLERANCE_ID.
• AP_SUPPLIER_SITES_INT — the supplier site interface table carries TOLERANCE_ID for inbound supplier loading.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY for Who-column audit.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN for session tracking.

Because these referential relationships are enforced through TOLERANCE_ID, deleting or renumbering a template record can orphan supplier-site and system-parameter assignments; changes should therefore be managed through standard Payables configuration forms rather than direct DML.