Results for “reference_txt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The XTR_RECLASS_DETAILS table resides in the XTR (Treasury) schema of Oracle E-Business Suite and stores reclassified effective unrealized gain/loss amounts associated with hedge accounting relationships. In the context of Oracle EBS 12.1.1 and 12.2.2, this table supports the Treasury module's hedge effectiveness and reclassification processing, capturing the amounts that move from Other Comprehensive Income (OCI) into earnings when a forecasted transaction or hedging relationship affects profit and loss. It is a transactional detail table tied directly to hedge attributes and to the concurrent request/batch infrastructure that drives revaluation and retroactive reclassification.

Under a heuristic Data Vault classification mined from its foreign key structure, XTR_RECLASS_DETAILS is best modeled as a link object — it connects a hedge attribute (the parent hedge relationship) to one or more processing batches (LAST_REVAL_BATCH_ID, RETRO_BATCH_ID), while also carrying descriptive and measured attributes. Practitioners should treat this as a modeling suggestion rather than a canonical Data Vault design.

Key Information Stored

The table contains 35 documented columns. The most significant are:

• RECLASS_DETAILS_ID — Surrogate primary key (XTR_RECLASS_DETAILS_PK) and the column users most commonly search for. Also defined as unique index XTR_RECLASS_DETAILS_U1.
• HEDGE_ATTRIBUTE_ID — Foreign key to XTR_HEDGE_ATTRIBUTES, identifying the hedge relationship being reclassified.
• RECLASS_DATE — The accounting date of the reclassification event; combined with HEDGE_ATTRIBUTE_ID it forms the business-key candidate under unique index XTR_RECLASS_DETAILS_U2.
• RECLASS_HEDGE_AMT — The hedged (effective) portion of the reclassified amount.
• RECLASS_GAIN_LOSS_AMT — The total reclassified gain or loss amount recognized into earnings.
• RECLASS_BALANCE_AMT — The remaining reclassification balance carried forward.
• REFERENCE_TXT — Free-form reference identifier for the reclassification entry.
• LAST_REVAL_BATCH_ID and RETRO_BATCH_ID — Foreign keys into XTR_BATCHES recording the batch that last revalued the record and any retroactive reclassification batch.
• COMMENTS and the ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 descriptive flexfield columns — user-defined and descriptive data.
• Audit and request columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID, enabling traceability to the concurrent program and request that created or modified the row.

Common Use Cases and Queries

Typical scenarios include hedge effectiveness reporting, OCI-to-earnings reclassification audits, and reconciliation of reclassification batches to their source hedge relationships.

Retrieve all reclassifications for a hedge relationship:

• SELECT RECLASS_DETAILS_ID, RECLASS_DATE, RECLASS_HEDGE_AMT, RECLASS_GAIN_LOSS_AMT, RECLASS_BALANCE_AMT FROM XTR.XTR_RECLASS_DETAILS WHERE HEDGE_ATTRIBUTE_ID = :hedge_attribute_id ORDER BY RECLASS_DATE;

Reconcile reclassification amounts to processing batches:

• SELECT d.RECLASS_DETAILS_ID, b.BATCH_ID, d.RECLASS_GAIN_LOSS_AMT FROM XTR.XTR_RECLASS_DETAILS d JOIN XTR.XTR_BATCHES b ON b.BATCH_ID = d.LAST_REVAL_BATCH_ID WHERE d.RECLASS_DATE BETWEEN :from_date AND :to_date;

Audit trail by concurrent request:

• SELECT RECLASS_DETAILS_ID, REQUEST_ID, PROGRAM_ID, CREATION_DATE FROM XTR.XTR_RECLASS_DETAILS WHERE REQUEST_ID = :request_id;

Related Objects

• XTR_HEDGE_ATTRIBUTES — Parent hedge relationship table joined via XTR_RECLASS_DETAILS.HEDGE_ATTRIBUTE_ID.
• XTR_BATCHES — Processing batch table joined twice: via LAST_REVAL_BATCH_ID and RETRO_BATCH_ID.
• XTR_RECLASS_DETAILS_PK / _U1 / _U2 — Primary key and unique indexes defining row identity and the (HEDGE_ATTRIBUTE_ID, RECLASS_DATE) business key.
• XTR_HEDGE_ATTRIBUTES (via PK) and any hedge effectiveness or reclassification concurrent programs that populate this table through PROGRAM_ID and REQUEST_ID references.