Search Results no_autho

Overview

APPS.XTR_LIMITS_P is the core limit-checking engine of Oracle Treasury (ETRM) within Oracle E-Business Suite 12.1.1 and 12.2.2. The package body encapsulates the business rules that determine whether a proposed treasury deal, settlement, or counterparty exposure remains within the credit and trading limits defined by the treasury organization. It calculates home-currency-equivalent (HCE) exposure amounts, applies period-based weighting factors, evaluates exposures against every category of limit maintained in the system, and records any excess conditions for subsequent review. Because limits are a control point for counterparty credit risk, dealer authority, sovereign exposure, intra-day trading, and currency concentration, XTR_LIMITS_P is central to the compliance posture of the treasury module.

The package exposes nineteen documented procedures and functions, classified as OTHER in the ETRM metadata, and references thirteen limit-related tables through APPS synonyms. It is referenced by five other packages, confirming its role as a shared service consumed elsewhere in the treasury stack.

Key Procedures and Functions

• WEIGHTED_USAGE — Computes the limit amount consumed by a deal type/subtype and date combination, applying a weighting percentage retrieved from XTR_FX_PERIOD_WEIGHTINGS and defaulting to 100% when no weighting row is found.
• CONVERT_TO_HCE_AMOUNT — Converts a supplied amount and currency into the home currency associated with the given company code.
• GET_HCE_AMOUNT — Retrieves the home-currency-equivalent amount used as the basis for limit consumption.
• LOG_FULL_LIMITS_CHECK and UPDATE_LIMIT_EXCESS_LOG — Write full limit-check results and update excess records in the excess log tables.
• MAINTAIN_EXCESS_LOG — Manages the lifecycle of excess log entries, including insertion and refresh.
• CALC_ALL_MIRROR_DDA_LIMIT_ROW and MIRROR_DDA_LIMIT_ROW_PROC — Maintain mirrored DDA limit rows representing demand-deposit-account style limit positions.
• UPDATE_WEIGHTINGS — Refreshes period weighting values used in utilization calculations.
• 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 — Category-specific limit retrieval functions covering global, group, sovereign, dealer, intra-day, counterparty, settlement, and currency limits respectively.
• GET_ACTUAL_SETTLE_EXCESS — Determines the excess arising from actual settlement activity.
• REINITIALIZE_LIMITS — Resets limit state, typically as part of period rollover or data reinitialization.

Internally, the body declares exceptions ex_no_limit_exists and ex_auth_not_y, which signal missing limit definitions and unauthorized conditions during limit evaluation.

Tables Accessed

The package reads and writes limit definitions and exposure data across the following synonyms:

• Limit definitions: XTR_COMPANY_LIMITS, XTR_COUNTERPARTY_LIMITS, XTR_COUNTRY_COMPANY_LIMITS, XTR_DEALER_LIMITS, XTR_GROUP_LIMITS, XTR_INTRA_DAY_LIMITS, and XTR_LIMIT_TYPES.
• Exposure and activity: XTR_DEAL_DATE_AMOUNTS (deal amounts by date), XTR_MIRROR_DDA_LIMIT_ROW (mirrored DDA positions), and XTR_FX_PERIOD_WEIGHTINGS (weighting factors by deal type, subtype, and month count).
• Excess tracking: XTR_LIMIT_EXCESS_LOG and its sequence XTR_LIMITS_EXCESS_LOG_S, which together record breaches for review.
• Reference data: XTR_MASTER_CURRENCIES (currency definitions), XTR_PARTY_INFO (counterparty and company attributes), and XTR_PRO_PARAM (system parameters).

Usage Notes

XTR_LIMITS_P is not intended for direct end-user invocation but is called from Oracle Treasury forms, concurrent programs, and other treasury packages whenever a deal is entered, amended, settled, or validated. Limit-check forms trigger the GET_LIM_* family to evaluate exposures at save time, while batch processes such as limit revaluation and end-of-day excess reporting invoke LOG_FULL_LIMITS_CHECK and MAINTAIN_EXCESS_LOG to populate the excess log. Customizations and extensions should call the public functions rather than replicating the HCE conversion or weighting logic, ensuring consistent treatment of XTR_FX_PERIOD_WEIGHTINGS and XTR_PARTY_INFO. In both 12.1.1 and 12.2.2, the package ships under the APPS schema with the $Header tag indicating maintenance through 2012; because it is covered by the ETRM support policy, direct modification is discouraged and the standard Oracle APIs should be preserved.