Search Results xtr_date_amount_types




Overview
Explore in AI Chat

Overview

The XTR_DATE_AMOUNT_TYPES table is a core configuration table within the Oracle Treasury (XTR) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a master control table that defines valid combinations of date types and amount types for specific treasury deal types. This table enforces business rules and data integrity by establishing which financial dates (e.g., value date, maturity date) can be associated with which monetary amounts (e.g., principal amount, interest amount) for a given transaction type. Its role is critical in ensuring that treasury deals are structured correctly within the system's data model, serving as a reference point for deal entry, validation, and processing workflows.

Key Information Stored

The table's structure is defined by a composite primary key, which encapsulates its fundamental business rule. The key columns are DEAL_TYPE, DATE_TYPE, and AMOUNT_TYPE. The DEAL_TYPE column identifies the category of treasury transaction, such as a foreign exchange deal or a money market deposit. The DATE_TYPE specifies a significant date in the deal's lifecycle, while the AMOUNT_TYPE denotes a specific financial figure associated with the deal. Each record represents a single, authorized linkage between these three entities. The table does not store transactional data itself but rather the permissible framework under which transactional data in other XTR tables must operate.

Common Use Cases and Queries

A primary use case is the validation of deal components during data entry via the Treasury front-end. Before a user can save a deal, the application validates that the dates and amounts being entered conform to the combinations defined in this table. For reporting and analysis, the table is essential for understanding the data model and constructing accurate queries. A common SQL pattern involves joining this table to its parent reference tables to retrieve descriptive information for configuration reviews or support tickets.

  • Sample Query to List All Valid Combinations for a Deal Type:
    SELECT dat.deal_type, dat.date_type, dt.description as date_desc, dat.amount_type, at.description as amount_desc
    FROM xtr_date_amount_types dat
    JOIN xtr_date_types dt ON dat.deal_type = dt.deal_type AND dat.date_type = dt.date_type
    JOIN xtr_amount_types at ON dat.deal_type = at.deal_type AND dat.amount_type = at.amount_type
    WHERE dat.deal_type = 'FX_SPOT' -- Example deal type
    ORDER BY dat.date_type, dat.amount_type;

Related Objects

XTR_DATE_AMOUNT_TYPES is centrally connected to two key reference tables via foreign key relationships, ensuring referential integrity. These relationships are documented as follows:

  • XTR_DATE_TYPES: This table is referenced via the foreign key on columns (DEAL_TYPE, DATE_TYPE). It provides the master list of valid date types for each deal type, supplying the descriptive context for the DATE_TYPE used in XTR_DATE_AMOUNT_TYPES.
  • XTR_AMOUNT_TYPES: This table is referenced via the foreign key on columns (DEAL_TYPE, AMOUNT_TYPE). It contains the master definition of all amount types, providing the descriptive context for the AMOUNT_TYPE used in XTR_DATE_AMOUNT_TYPES.

This table is a foundational component that is likely referenced by various transactional tables and user interfaces within the Treasury module to validate and process deal components correctly.