Search Results xtr_limit_excess_log_details_v




Overview
Explore in AI Chat

Overview

XTR_LIMIT_EXCESS_LOG_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the Treasury (XTR) product. The view denormalizes and enriches the base limit-excess log maintained by ETRM's credit and limit monitoring engine, presenting one row per recorded limit breach together with the descriptive attributes of the parties, currencies, companies, and limit definitions involved. Its purpose is to give treasury analysts, credit controllers, and downstream reporting or integration components a single flattened source for answering who exceeded a limit, by how much, when, and under which authorisation status.

Because the view joins the transactional excess log to mirror deal, party, company-limit, and limit-type information, it eliminates the multi-table navigation that would otherwise be required to interpret a limit breach. It is therefore a logical source for limit exception dashboards, audit extracts, alerting feed generation, and period-end compliance reporting, and it can be queried directly by SQL*Plus, Oracle Reports, BI Publisher, or custom PL/SQL.

Underlying Base Objects

The view is defined over five objects, all referenced through APPS-owned synonyms:

All joins other than the driving log table are outer joins (the (+) operator), so every logged excess event is preserved even where currency, party, company-limit, or limit-type reference data is missing or has since been redefined.

Key Columns

  • LOG_ID — unique identifier of the excess-log entry; the natural primary key for the view.
  • AMOUNT_DATE / EXCEEDED_ON_DATE — the amount date and the timestamp on which the limit was exceeded; primary date filters for reporting.
  • COMPANY_CODE, LIMIT_CODE, LIMIT_TYPE, LIMIT_PARTY, LIMIT_COMPANY, LIMIT_GROUP — identify the company, limit, limit type (with FX_INVEST_FUND_TYPE from XTR_LIMIT_TYPES), and party or group against which the breach occurred.
  • DEAL_NUMBER, TRANSACTION_NUMBER, DEALER_CODE, CURRENCY — identify the instrument and dealer responsible for the excess.
  • LIMITING_AMOUNT, HCE_AMOUNT, EXCEEDED_BY_AMOUNT — the applicable limit threshold, the measured exposure, and the resulting excess amount.
  • LIMIT_CHECK_TYPE, EXCEPTION_TYPE — classify the check performed and the nature of the exception raised.
  • AUTHORISED_BY, DUAL_AUTHORISED_BY, DUAL_AUTHORISED_ON — capture single and dual authorisation of the exception for audit and control purposes.
  • COUNTRY_CODE — party country, sourced from XTR_PARTY_INFO for geographic analysis.

Common Use Cases and Queries

Typical scenarios include daily limit-breach monitoring, reconciliation of excesses to deals and dealers, ageing of unauthorised exceptions, and feeding external credit-risk systems. Because the joins are outer, always filter on the driving table columns to keep the access path efficient.

List excesses for a company within a date range:

  • SELECT log_id, amount_date, company_code, limit_code, limit_party, deal_number, dealer_code, limiting_amount, hce_amount, exceeded_by_amount, exception_type FROM xtr_limit_excess_log_details_v WHERE company_code = :p_company AND amount_date BETWEEN :p_from AND :p_to ORDER BY amount_date, log_id;

Identify unauthorised or single-authorised exceptions requiring follow-up:

  • SELECT log_id, company_code, limit_code, deal_number, exceeded_by_amount, authorised_by, dual_authorised_by, dual_authorised_on FROM xtr_limit_excess_log_details_v WHERE dual_authorised_on IS NULL AND amount_date >= TRUNC(SYSDATE) - 30;

Summarise excess exposure by limit type and party country:

  • SELECT limit_type, country_code, COUNT(*) excess_count, SUM(exceeded_by_amount) total_exceeded FROM xtr_limit_excess_log_details_v GROUP BY limit_type, country_code ORDER BY total_exceeded DESC;

These queries illustrate how the view supports both detailed exception investigation and aggregated exposure analysis without requiring direct joins to the underlying ETRM limit-excess and reference tables.