Search Results xtr_hedge_attributes




Overview
Explore in AI Chat

Overview

The XTR_HEDGE_ATTRIBUTES table is a core data repository within the Oracle E-Business Suite (EBS) Treasury (XTR) module, specifically for versions 12.1.1 and 12.2.2. It functions as the central table for storing master information about a hedge relationship. A hedge is a financial strategy used to mitigate risk associated with an underlying exposure, such as a forecasted transaction or a recognized asset/liability. This table does not store the underlying exposure or the hedging instrument details themselves; instead, it defines the overarching hedge relationship, its temporal boundaries, status, and classification parameters. Its role is critical for hedge accounting compliance, performance tracking, and the operational management of treasury hedging activities.

Key Information Stored

The table's primary purpose, as documented, is to store the start and end dates of the hedge, hedge status, and classification information. While the full column list is not provided in the excerpt, the foreign key relationships and standard practice indicate it holds several key attributes. The primary key, HEDGE_ATTRIBUTE_ID, uniquely identifies each hedge relationship. Critical columns include START_DATE and END_DATE to define the hedge period, and a STATUS field to track its lifecycle (e.g., Proposed, Effective, Ineffective, Terminated). Classification is managed through foreign key columns like STRATEGY_CODE (linking to XTR_HEDGE_STRATEGIES) and COMPANY_CODE (linking to XTR_PARTY_INFO). It also holds dealer codes (RETRO_DEALER_CODE, PROS_DEALER_CODE) for personnel assignment and a REQUEST_ID linking to the concurrent request (FND_CONCURRENT_REQUESTS) that may have processed it.

Common Use Cases and Queries

This table is central to treasury reporting and audit processes. Common use cases include generating a hedge effectiveness testing register, producing hedge relationship summaries for financial reporting, and tracking the status of all active hedges. A typical query would join this table to its related strategy and company tables to produce a management report.

Sample Query: Active Hedge Summary

  • SELECT ha.HEDGE_ATTRIBUTE_ID, ha.START_DATE, ha.END_DATE, ha.STATUS, hs.STRATEGY_NAME, pi.PARTY_NAME AS COMPANY_NAME FROM XTR_HEDGE_ATTRIBUTES ha, XTR_HEDGE_STRATEGIES hs, XTR_PARTY_INFO pi WHERE ha.STRATEGY_CODE = hs.STRATEGY_CODE AND ha.COMPANY_CODE = pi.PARTY_CODE AND ha.STATUS = 'EFFECTIVE' AND SYSDATE BETWEEN ha.START_DATE AND ha.END_DATE;

Another critical use case is supporting the retroactive and prospective effectiveness testing processes, where this table is joined to XTR_HEDGE_RETRO_TESTS and XTR_DEAL_RETRO_TESTS.

Related Objects

The XTR_HEDGE_ATTRIBUTES table has extensive relationships within the Treasury schema, acting as a hub for hedge-related data. Based on the provided foreign key metadata, key relationships include:

  • Parent/Reference Tables: XTR_HEDGE_STRATEGIES (via STRATEGY_CODE), XTR_PARTY_INFO (via COMPANY_CODE), XTR_DEALER_CODES (via RETRO_DEALER_CODE and PROS_DEALER_CODE), and FND_CONCURRENT_REQUESTS (via REQUEST_ID).
  • Child/Dependent Tables: Several transactional and testing tables use HEDGE_ATTRIBUTE_ID as a foreign key, including XTR_DEAL_RETRO_TESTS, XTR_HEDGE_RELATIONSHIPS, XTR_HEDGE_RETRO_TESTS, and XTR_RECLASS_DETAILS. This structure ensures all testing results and specific hedge linkages are tied back to the master hedge definition.