Search Results gcs_curr_treatments_b




Overview
Explore in AI Chat

Overview

The GCS_CURR_TREATMENTS_B table is a core data structure within the Oracle E-Business Suite (EBS) Financial Consolidation Hub (FCH) module, specifically designated as version 12.1.1 / 12.2.2. Its primary function is to store master data defining the currency conversion methodologies, or "treatments," to be applied during the financial consolidation process. These treatments govern how transactional data from various subsidiary entities, which may operate in different functional currencies, is translated into the consolidation currency. The table is integral to ensuring accurate and compliant consolidated financial reporting in multi-currency corporate environments. It is important to note that the provided ETRM metadata explicitly labels the GCS module as "Obsolete," indicating this object pertains to a legacy implementation.

Key Information Stored

The table's central identifier is the CURR_TREATMENT_ID, which serves as the primary key (GCS_CURR_TREATMENTS_B_PK) and uniquely defines each currency treatment rule. The most critical data points stored are the references to specific exchange rate types used for different aspects of conversion. According to the documented foreign key relationships, the table contains at least two key columns: ENDING_RATE_TYPE and AVERAGE_RATE_TYPE. These columns hold foreign keys that reference the GL_DAILY_CONVERSION_TYPES table, thereby linking each consolidation treatment to the predefined daily conversion rate types in the General Ledger. This structure allows administrators to configure whether balance sheet items (typically using an ending period rate) and income statement items (often using an average period rate) are translated using specific corporate, spot, or historical rate types.

Common Use Cases and Queries

The primary use case is the setup and maintenance of currency translation rules within the Consolidation Hub. A system administrator would create or modify records in this table to define treatments like "Group Translation - EUR" or "Hyperinflation Adjustment - USD." Common operational queries involve retrieving treatment definitions for validation or integration with consolidation rules. A typical SQL pattern would join to the GL_DAILY_CONVERSION_TYPES table to resolve the rate type codes for reporting purposes:

  • SELECT gct.curr_treatment_id, gct.ending_rate_type, end_rates.conversion_type ending_type_name, gct.average_rate_type, avg_rates.conversion_type average_type_name FROM gcs_curr_treatments_b gct, gl_daily_conversion_types end_rates, gl_daily_conversion_types avg_rates WHERE gct.ending_rate_type = end_rates.conversion_type (+) AND gct.average_rate_type = avg_rates.conversion_type (+);

This table is also queried by the consolidation engine during a consolidation run to determine the correct translation logic for each entity relationship.

Related Objects

The GCS_CURR_TREATMENTS_B table exists within a defined relational schema, as evidenced by its foreign key constraints. It has two outgoing foreign key dependencies and one incoming reference.

  • Referenced Tables (Outgoing FK): The table references the GL_DAILY_CONVERSION_TYPES table twice: once via the ENDING_RATE_TYPE column and once via the AVERAGE_RATE_TYPE column. This ensures referential integrity for the rate types used.
  • Referencing Table (Incoming FK): The GCS_CONS_RELATIONSHIPS table references this table via its CURR_TREATMENT_ID column. This is the most critical relationship, as it links a specific consolidation relationship (defining how a child entity consolidates into a parent) to the currency treatment that should be applied to that entity's data.