Search Results accrual_to




Overview
Explore in AI Chat

Overview

XTR_A_DEALS is the master deals table within the Oracle Treasury (XTR) module of Oracle E-Business Suite, residing in the XTR schema. Created from the entity "XTR DEAL" by Oracle on 06-MAY-93, it is one of the oldest and most structurally significant objects in the Treasury data model. The table stores the header-level record for every treasury deal captured through the Treasury Management application, including foreign exchange contracts, money market instruments, bonds, swaps, forward rate agreements, and options. In the documented 12.2.2 physical schema it contains 218 columns, and it is validated as a standalone object at the physical level.

From a Data Vault modeling perspective, the heuristic classification for XTR_A_DEALS is a hub. Its business identity is anchored by DEAL_NO, while its numerous descriptive and financial attributes (rates, amounts, dates, counterparties) behave as satellite-style payload. The only documented foreign key is XTR_A_DEALS.SECURITY_ID referencing EDR_PSIG_SECURITY, which ties bond and security-linked deals to the securities master, though the table itself remains a central hub rather than a pure link or satellite.

Key Information Stored

The table's most consequential columns fall into several functional groups:

The surrogate row identifier is provided by the standard Oracle EBS primary key, while DEAL_NO is the principal business-key candidate referenced by deal-linked transactions. The 15 ATTRIBUTE columns implement the Treasury deal descriptive flexfield.

Common Use Cases and Queries

Typical usage includes deal blotter reporting, FX exposure analysis, money market maturity ladders, and bond portfolio valuation. Queries commonly filter by deal type, date, or counterparty, for example:

SELECT DEAL_NO, DEAL_TYPE, CPARTY_CODE, CURRENCY, FACE_VALUE_AMOUNT, MATURITY_DATE
FROM   XTR.XTR_A_DEALS
WHERE  DEAL_TYPE = 'FX'
AND    DEAL_DATE >= :from_date
AND    DEAL_DATE <  :to_date;

Maturity and settlement reporting leverages MATURITY_DATE, SETTLE_DATE, and SETTLE_AMOUNT. Exposure and limit monitoring uses PORTFOLIO_CODE, LIMIT_CODE, and the HCE amount columns. Auditors frequently query the dual-authorisation fields and the created/updated audit columns for control validation.

Related Objects

  • EDR_PSIG_SECURITY: referenced by XTR_A_DEALS.SECURITY_ID; joins bond and security-linked deals to the securities master.
  • XTR Deal child tables (cashflow, interest, settlement): link back to XTR_A_DEALS via DEAL_NO to store scheduled cashflows, interest accruals, and settlement legs.
  • FX deal reference tables: FXD_DEAL_NO, FXO_DEAL_NO, FX_PD_DEAL_NO, FX_RO_DEAL_NO, and NI_DEAL_NO are cross-references that tie XTR_A_DEALS to FX, option, and NDF deal records.
  • Counterparty and portfolio masters: CPARTY_CODE and PORTFOLIO_CODE resolve to their respective Treasury master tables.
  • XTR Revaluation tables: FIRST_REVAL_BATCH_ID and LAST_REVAL_BATCH_ID link deals to revaluation batch runs.

Together these objects position XTR_A_DEALS as the operational hub of the Treasury deal model, with its 218 columns capturing the full commercial, financial, and audit context of each trade.