Search Results limiting_amount




Overview
Explore in AI Chat

Overview

APPS.XTR_LIMIT_EXCESS_LOG_V is a reporting view in the Oracle E-Business Suite Treasury (ETRM) module. It presents a projection of treasury limit-check excess events — records generated when a deal, transaction, or position breaches a configured counterparty or company limit. The view exposes the audit and authorisation attributes associated with each excess, including who authorised the exception, when dual authorisation occurred, and the currency of the relevant amounts. Because it surfaces the column LIMITING_AMOUNT (the threshold value applied at the time of the check) alongside EXCEEDED_BY_AMOUNT, it is the natural object to query when investigating "limiting_amount" values, reconciling why a given excess was raised, or building reporting and integration extracts around limit breaches. In Oracle EBS 12.1.1 and 12.2.2 the object is owned by APPS and is intended for read-only query and reporting use rather than transactional maintenance.

Underlying Base Objects

The documented metadata identifies a single referenced base object: the synonym XTR_LIMIT_EXCESS_LOG. The view is defined as a straightforward SELECT over that table, selecting every listed column without joins, filters, aggregation, or calculated expressions. It therefore does not alter or enrich the underlying data — it is a 1:1 projection of the base table's documented column set. Practical implications follow directly: any row visible in the view corresponds to exactly one row in XTR_LIMIT_EXCESS_LOG, and any DML or column addition must be performed against the base table (subject to ETRM's supported extension practices). No additional ETRM tables such as deal, counterparty, or limit definition tables are joined within the view, so descriptive attributes must be resolved separately by the consumer.

Key Columns

The view exposes eighteen columns. The most significant include:

Common Use Cases and Queries

Typical uses include excess reporting for treasury operations, exception audit review, and feeds into risk or compliance extracts.

  • List excesses with their thresholds: SELECT LOG_ID, LIMIT_CODE, LIMIT_PARTY, LIMITING_AMOUNT, EXCEEDED_BY_AMOUNT, CURRENCY FROM APPS.XTR_LIMIT_EXCESS_LOG_V WHERE EXCEEDED_ON_DATE >= :p_from_date;
  • Identify large breaches: ... WHERE EXCEEDED_BY_AMOUNT > :p_threshold ORDER BY EXCEEDED_BY_AMOUNT DESC;
  • Review authorisation status: SELECT LOG_ID, EXCEPTION_TYPE, AUTHORISED_BY, DUAL_AUTHORISED_BY, DUAL_AUTHORISED_ON FROM APPS.XTR_LIMIT_EXCESS_LOG_V WHERE DUAL_AUTHORISED_ON IS NULL;
  • Analyse breaches by counterparty and limit: SELECT LIMIT_PARTY, LIMIT_CODE, COUNT(*), SUM(EXCEEDED_BY_AMOUNT) FROM APPS.XTR_LIMIT_EXCESS_LOG_V GROUP BY LIMIT_PARTY, LIMIT_CODE;

Because descriptive deal and limit data reside elsewhere, these queries are often joined to deal and limit definition tables on DEAL_NUMBER, LIMIT_CODE, and LIMIT_PARTY to produce complete management reporting.