Search Results no_limit

Overview

APPS.XTR_LIMIT_EXCESS_LOG_DETAILS_V is a supplementary Oracle E-Business Suite (EBS) view owned by the APPS schema and registered under FND Design Data as XTR.XTR_LIMIT_EXCESS_LOG_DETAILS_V. It belongs to the Treasury (ETRM) module and operates with a status of VALID in both EBS 12.1.1 and 12.2.2. The view is classified by Oracle as a supplementary view used to simplify forms coding, presenting a denormalized, business-friendly projection of limit exception data recorded by the Treasury limit-checking engine. Its principal function is to expose the details of limit breaches and warnings logged during deal and transaction processing, joining the limit exception log to company, party, limit-type, and mirror DDA limit-row information so that a single row describes who exceeded which limit, by how much, on what date, and under what authority.

Because it is a forms-support view, Oracle explicitly warns that direct querying or alteration of the underlying data through this view is not recommended, since the definition may change dramatically in subsequent minor or major releases. It should therefore be treated as a read-only reporting surface rather than a supported DML target.

Underlying Base Objects

The view is defined over the following documented base objects:

• XTR_LIMIT_EXCESS_LOG — the core exception log table holding the recorded limit breaches and warnings.
• XTR_COMPANY_LIMITS — company-level limit definitions that drive the limit-checking rules.
• XTR_LIMIT_TYPES — the catalogue of limit categories (for example, company, counterparty, currency, dealer).
• XTR_PARTY_INFO — party master information for counterparties against which limits are evaluated.
• XTR_MIRROR_DDA_LIMIT_ROW — mirror structure supporting DDA (dealer/detail) limit-row lookups.

The view effectively aggregates the transactional exception record with the descriptive context needed to interpret it, resolving codes such as limit group, limit type, and party into meaningful reporting values.

Key Columns

The view exposes a broad set of columns. The most significant include:

• LOG_ID — the limit exception log batch identifier, a key grouping attribute for a set of exception records.
• EXCEPTION_TYPE — the nature of the breach, documented as WARNING, EXCEEDED, or NO_LIMIT. The NO_LIMIT value is of direct relevance to users searching on the term "no_limit", indicating that no limit was defined for the party or category checked.
• EXCEEDED_BY_AMOUNT and HCE_AMOUNT — the amount by which the limit was breached, and the same figure expressed in reporting-currency equivalent (HCE).
• LIMITING_AMOUNT — the maximum amount permitted by the limit at the time of the exception.
• EXCEEDED_ON_DATE — the date the exception occurred.
• LIMIT_CODE, LIMIT_COMPANY, LIMIT_GROUP, LIMIT_PARTY, LIMIT_CHECK_TYPE — the identifiers describing which limit was applied, its category, its owning entity, and the party checked.
• DEAL_NUMBER, TRANSACTION_NUMBER, DEALER_CODE, CURRENCY, COMPANY_CODE, COUNTRY_CODE — deal and transaction context.
• AUTHORISED_BY — the Treasury user who authorised the limit exception; DUAL_AUTHORISED_BY and DUAL_AUTHORISED_ON are documented as not currently used.
• AMOUNT_DATE — the maturity or payoff date of the associated instrument.

Common Use Cases and Queries

Typical scenarios include reviewing limit-breach history for audit and compliance, isolating NO_LIMIT conditions to identify parties or categories lacking limit definitions, and reporting authorised exceptions by Treasury user. A representative query is:

• SELECT log_id, exception_type, limit_code, limit_party, exceeded_by_amount, hce_amount, exceeded_on_date FROM apps.xtr_limit_excess_log_details_v WHERE exception_type = 'NO_LIMIT';
• SELECT deal_number, transaction_number, currency, limiting_amount, exceeded_by_amount, authorised_by FROM apps.xtr_limit_excess_log_details_v WHERE exceeded_on_date BETWEEN :start_date AND :end_date;

Such queries support exception dashboards, period-end limit reporting, and root-cause analysis of unresolvable limit categories.