Search Results xtr_fx_period_weightings_pk

Overview

The XTR_FX_PERIOD_WEIGHTINGS table is a core data object within the Oracle E-Business Suite (EBS) Treasury (XTR) module. It functions as a configuration and control table, central to the management of counterparty exposure and limit utilization for foreign exchange (FX) transactions. Its primary role is to store period-based weighting factors that are applied to FX deals when calculating their contribution towards a counterparty's credit limit. This weighting mechanism allows treasury operations to risk-weight deals based on their remaining tenor or time to maturity, enabling more sophisticated and accurate exposure management than a simple notional sum. The table is integral to the system's ability to enforce prudent risk controls and comply with internal treasury policies.

Key Information Stored

The table's structure is defined by a composite primary key and stores configuration data rather than transactional records. The key columns, which uniquely identify a weighting rule, are DEAL_TYPE, DEAL_SUBTYPE, and NOS_MONTHS. The DEAL_TYPE and DEAL_SUBTYPE columns classify the specific FX product (e.g., Spot, Forward, Swap), linking to the XTR_DEAL_SUBTYPES reference table. The NOS_MONTHS column represents the number of months to maturity for which the associated weighting factor is applicable. While the specific weighting factor column name is not explicitly listed in the provided metadata, based on the table's purpose, it would typically be a column such as WEIGHTING_FACTOR or PERCENTAGE that holds the multiplier (often a decimal or percentage) applied to the deal's notional amount for limit calculations.

Common Use Cases and Queries

The primary use case is the dynamic calculation of utilized credit limits for counterparties. When the system assesses a counterparty's exposure from FX deals, it queries this table to find the appropriate risk weighting based on the deal's subtype and its remaining tenor. A common reporting need is to review or audit the weighting schedule. A sample query to retrieve the full weighting matrix would be:

• SELECT deal_type, deal_subtype, nos_months, weighting_factor FROM xtr.xtr_fx_period_weightings ORDER BY 1,2,3;

Another critical scenario is during the entry or revaluation of an FX deal, where a background process joins the deal information with this table to compute its weighted amount for real-time limit checking. Administrators may also run queries to validate configuration by ensuring all active DEAL_SUBTYPES have corresponding weightings for expected tenor buckets.

Related Objects

The XTR_FX_PERIOD_WEIGHTINGS table maintains a defined relationship within the Treasury data model, primarily serving as a referenced lookup table.

• Primary Key: XTR_FX_PERIOD_WEIGHTINGS_PK on (DEAL_SUBTYPE, DEAL_TYPE, NOS_MONTHS).
• Foreign Key (References): The table has a foreign key relationship to XTR_DEAL_SUBTYPES. It references this table using the combined columns XTR_FX_PERIOD_WEIGHTINGS.DEAL_TYPE and XTR_FX_PERIOD_WEIGHTINGS.DEAL_SUBTYPE. This ensures that weightings can only be defined for valid, registered deal subtypes within the application.
• Dependent Objects: While not listed in the metadata, this table is logically referenced by core Treasury limit calculation engines, likely within PL/SQL packages in the XTR schema, and by views that aggregate counterparty exposure. Transactional tables storing FX deal details would use the DEAL_TYPE and DEAL_SUBTYPE to implicitly link to the weighting rules.