Search Results maintain_excess_log




Overview
Explore in AI Chat

Overview

XTR_LIMITS_P is the core limits-engine package within the Oracle E-Business Suite Treasury (ETRM) module, owned by the APPS schema. Its business purpose is to evaluate, calculate, and record credit and counterparty limit utilisation for treasury deals. Whenever a deal, foreign-exchange transaction, or settlement is captured, the package determines the home-currency-equivalent (HCE) amount of the exposure, applies the appropriate weighting for the deal type and subtype, compares the result against the configured limit thresholds, and writes any breach to the limit excess log.

The package encapsulates limit-checking logic for multiple limit dimensions, including global, group, sovereign, dealer-deal, intra-day, counterparty, and currency limits. It is classified in the ETRM documentation as an OTHER API (not a public open interface), meaning it is intended primarily for internal consumption by ETRM forms, concurrent programs, and other ETRM packages rather than by external integrations. The header comment indicates the package has been shipping since at least the 11i era and was maintained through the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

  • WEIGHTED_USAGE — Calculates the amount utilised against a limit code for a given counterparty/company combination, factoring deal type, subtype, amount date, and the HCE amount.
  • CONVERT_TO_HCE_AMOUNT — Converts an amount in a specified currency and company code into its home-currency equivalent.
  • GET_HCE_AMOUNT — Returns the home-currency-equivalent for a supplied amount and currency.
  • LOG_FULL_LIMITS_CHECK — Records the outcome of a complete limits check for a deal or transaction, capturing deal, counterparty, product, limit code, limit party, amount, dealer, and currency details. A second-currency parameter supports FX deals.
  • UPDATE_LIMIT_EXCESS_LOG — Updates the limit excess log entry associated with a specific deal and transaction number, recording the acting user and log identifier.
  • CALC_ALL_MIRROR_DDA_LIMIT_ROW — Recalculates all limit HCE amounts and weightings, with an automatic-recalculation control parameter.
  • UPDATE_WEIGHTINGS — A concurrent-program cover routine that drives recalculation of weightings and returns standard concurrent error buffer and return code outputs.
  • MIRROR_DDA_LIMIT_ROW_PROC — Calculates the utilised amount field for all DDA mirror rows, accepting an action and prior limit/deal/transaction identifiers.
  • GET_LIM_GLOBAL, GET_LIM_GROUP, GET_LIM_SOVEREIGN, GET_LIM_DEALER_DEAL, GET_LIM_INTRA_DAY, GET_LIM_CPARTY, GET_LIM_SETTLE, GET_LIM_CCY — Retrieve and enforce the corresponding limit category (global, group, sovereign, dealer, intra-day, counterparty, settlement, and currency limits respectively).
  • GET_ACTUAL_SETTLE_EXCESS — Determines the actual settlement excess amount against settlement limits.
  • MAINTAIN_EXCESS_LOG — Maintains limit excess log records, including housekeeping of log entries.
  • REINITIALIZE_LIMITS — Reinitialises limit data, typically as part of recalculation or setup refresh.

Tables Accessed

The package reads and writes a set of ETRM limit and deal tables accessed through APPS synonyms. Limit definitions are held in XTR_COMPANY_LIMITS, XTR_COUNTERPARTY_LIMITS, XTR_COUNTRY_COMPANY_LIMITS, XTR_DEALER_LIMITS, XTR_GROUP_LIMITS, and XTR_INTRA_DAY_LIMITS. Deal and exposure amounts originate from XTR_DEAL_DATE_AMOUNTS. Weighting factors for FX period limits are drawn from XTR_FX_PERIOD_WEIGHTINGS. Excess breaches are persisted in XTR_LIMIT_EXCESS_LOG and its sequence XTR_LIMITS_EXCESS_LOG_S, while intermediate results are staged in XTR_MIRROR_DDA_LIMIT_ROW. Supporting reference data includes XTR_LIMIT_TYPES, XTR_MASTER_CURRENCIES, XTR_PARTY_INFO, and XTR_PRO_PARAM.

Usage Notes

XTR_LIMITS_P is invoked automatically from ETRM deal capture and settlement forms whenever a limit check is required, and from the UPDATE_WEIGHTINGS concurrent program, which recalculates weightings across all mirror DDA limit rows. It is also referenced by five other ETRM packages, which call its limit-retrieval and logging functions as part of their own processing. Because it is classified as OTHER rather than a public API, custom code should treat it as a dependent internal component: extensions should prefer supported ETRM APIs and be aware that signatures may change between 12.1.1 and 12.2.2. When diagnosing limit breaches, review XTR_LIMIT_EXCESS_LOG records produced by LOG_FULL_LIMITS_CHECK and UPDATE_LIMIT_EXCESS_LOG.