Search Results xtr_hedge_retro_tests




Overview
Explore in AI Chat

Overview

The XTR_HEDGE_RETRO_TESTS table is a core data object within the Oracle E-Business Suite (EBS) Treasury (XTR) module, specifically for releases 12.1.1 and 12.2.2. Its primary function is to store detailed results from retrospective effectiveness tests conducted for designated hedging relationships. Under accounting standards such as IAS 39 and IFRS 9, entities must periodically assess and document the historical effectiveness of their hedges to qualify for hedge accounting. This table serves as the central repository for the quantitative and qualitative measurements generated by these mandatory tests, enabling compliance, auditability, and financial reporting for treasury operations.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the table's description and foreign key relationships define its critical data elements. Each record is uniquely identified by the HEDGE_RETRO_TEST_ID primary key. The table links to a specific hedging relationship via the HEDGE_ATTRIBUTE_ID foreign key, which references the XTR_HEDGE_ATTRIBUTES table. It associates the test with a legal entity or company through the COMPANY_CODE column, linked to XTR_PARTY_INFO. The BATCH_ID foreign key to XTR_BATCHES indicates that effectiveness testing is often a batch-processed activity. Typical data stored includes the test calculation date, the measurement period (e.g., start and end dates), the calculated effectiveness ratio (e.g., dollar-offset or regression method results), the cumulative change in fair value of the hedging instrument and the hedged item, and any necessary descriptive justifications for the test outcome.

Common Use Cases and Queries

The primary use case is generating reports for internal accounting, external auditors, and regulatory compliance to demonstrate that hedging relationships remain highly effective throughout their life. A common query involves retrieving all effectiveness tests for a specific hedge or portfolio within a given accounting period. For example, to analyze test results for a particular hedging program, one might execute a query joining XTR_HEDGE_RETRO_TESTS to XTR_HEDGE_ATTRIBUTES on HEDGE_ATTRIBUTE_ID and filtering by the hedge identifier and a test date range. Treasury analysts also run queries to identify hedges falling outside acceptable effectiveness thresholds, which may trigger de-designation or adjustment of the hedging strategy. The batch ID linkage allows for tracing the origin of test results for troubleshooting and process control.

Related Objects

The table maintains defined foreign key relationships with several other core XTR tables, establishing its place in the data model. The documented relationships are:

  • XTR_PARTY_INFO: Joined via XTR_HEDGE_RETRO_TESTS.COMPANY_CODE to identify the legal entity for which the test was performed.
  • XTR_HEDGE_ATTRIBUTES: Joined via XTR_HEDGE_RETRO_TESTS.HEDGE_ATTRIBUTE_ID. This is the most critical relationship, linking the test results to the specific hedging relationship's definition and terms.
  • XTR_BATCHES: Joined via XTR_HEDGE_RETRO_TESTS.BATCH_ID, connecting the test record to the batch process that created it, which is essential for process auditing and reconciliation.
The table is also likely referenced by various treasury reports, interfaces, and the Hedge Effectiveness Test (HET) engine within the EBS application.