Search Results xtr_interest_tolerances_pk

Overview

The XTR_INTEREST_TOLERANCES table is a core data object within the Oracle E-Business Suite Treasury (XTR) module. It is designed to store the configuration and rules for tolerance levels associated with the override feature, specifically for interest-related transactions. In the context of treasury operations, this table enables controlled flexibility by defining permissible variances or thresholds. When users attempt to override standard system-calculated interest values, the tolerances stored in this table are referenced to determine if the manual override is within an acceptable, pre-defined range. This functionality is critical for maintaining financial controls and audit integrity while allowing for necessary operational adjustments in complex treasury deals across versions 12.1.1 and 12.2.2.

Key Information Stored

The table's primary purpose is to define tolerance parameters keyed by specific transactional contexts. Its structure, inferred from the provided metadata, includes several critical columns. The INTEREST_TOLERANCE_ID serves as the unique primary key identifier for each tolerance rule. The COMPANY_CODE and CPARTY_CODE columns link to the XTR_PARTY_INFO table, establishing the tolerance rule for a specific legal entity (company) and counterparty relationship. The DEAL_TYPE column, a foreign key to XTR_DEAL_TYPES, specifies the type of financial instrument (e.g., loan, deposit, swap) to which the tolerance applies. While the exact tolerance value columns are not listed in the excerpt, they typically store numeric thresholds—such as absolute amount or percentage limits—that define the allowable override range for interest calculations.

Common Use Cases and Queries

The primary use case is the validation of manual overrides during deal entry or amendment. For example, when a user modifies an interest rate or amount, the application queries this table to check if the deviation falls within the configured tolerance for that company, counterparty, and deal type. A common reporting need is to audit all configured tolerances. A sample SQL query to retrieve this setup information would be:

SELECT it.interest_tolerance_id, it.company_code, it.cparty_code, it.deal_type, pi1.party_name company_name, pi2.party_name cparty_name, dt.description deal_type_desc FROM xtr_interest_tolerances it, xtr_party_info pi1, xtr_party_info pi2, xtr_deal_types dt WHERE it.company_code = pi1.party_code AND it.cparty_code = pi2.party_code AND it.deal_type = dt.deal_type ORDER BY it.company_code, it.cparty_code;

Another critical scenario is troubleshooting failed override attempts, where support personnel would query the relevant tolerance rule to verify the threshold against the user's input.

Related Objects

The XTR_INTEREST_TOLERANCES table is centrally connected to other key Treasury tables. It has a mandatory foreign key relationship with XTR_DEAL_TYPES via the DEAL_TYPE column, classifying the financial instrument. It has two distinct foreign key relationships with the XTR_PARTY_INFO table: one for the COMPANY_CODE (the owning entity) and another for the CPARTY_CODE (the counterparty). This ensures tolerances are defined within valid entity relationships. The table is also referenced by the application's validation logic, likely within PL/SQL packages in the XTR schema that handle deal processing and override authorization. Its primary key is enforced by the index XTR_INTEREST_TOLERANCES_PK.