Results for “equity_mode_code”

2 results




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

Overview

GCS_CURR_TREATMENTS_B is a consolidation configuration table within the Oracle E-Business Suite Financial Consolidation Hub (GCS) module. It stores the currency treatment definitions that govern how the consolidation engine translates and reports balances across multiple functional and reporting currencies. Each row represents a discrete currency treatment — a named rule set that specifies which daily conversion rate types are applied to ending balances versus average balances, and how equity and income statement activity is handled during the translation and consolidation process.

The object is documented in ETRM 12.1.1 with an owner of GCS and a total of 31 columns. It is marked as obsolete in the GCS module and is noted as not implemented in the reference database, meaning it appears in the data model and dictionary but may not be instantiated in every environment. Applications that predate or bypass the current consolidation architecture may still carry this table in their schema. A heuristic Data Vault classification derived from the foreign key structure suggests a satellite-leaning pattern, since the table carries descriptive attributes keyed to a single surrogate identifier rather than resolving many-to-many relationships on its own. This classification is a modeling suggestion only, not an Oracle designation.

Key Information Stored

The table is anchored by the surrogate primary key CURR_TREATMENT_ID, defined through the constraint GCS_CURR_TREATMENTS_B_PK. A unique index, GCS_CURR_TREATMENTS_B_U1, is documented on the same column, which is worth noting when evaluating business-key candidates: in this table the unique index does not introduce a separate natural key but reinforces the surrogate. The most functionally significant columns are:

Common Use Cases and Queries

The principal scenario is identifying the rate types and translation modes applied to a given consolidation, and auditing which treatment is flagged as default. A typical query joins the treatment row to the conversion type table twice, once for each rate:

  • SELECT t.curr_treatment_id, e.name ending_rate, a.name average_rate, t.default_flag FROM gcs_curr_treatments_b t JOIN gl_daily_conversion_types e ON t.ending_rate_type = e.conversion_type JOIN gl_daily_conversion_types a ON t.average_rate_type = a.conversion_type WHERE t.enabled_flag = 'Y';
  • Locating the default treatment: filter on DEFAULT_FLAG = 'Y' and ENABLED_FLAG = 'Y'.
  • Reporting consolidation relationship assignments, joining to GCS_CONS_RELATIONSHIPS on CURR_TREATMENT_ID.
  • Mapping custom CTA dimensions by pivoting the CTA_USER_DIM1_ID through CTA_USER_DIM10_ID columns against the corresponding user dimension value tables.

Because the table is obsolete, migration or cleanup scripts should first confirm row counts and dependencies before removal.

Related Objects

  • GL_DAILY_CONVERSION_TYPES — referenced twice, via ENDING_RATE_TYPE and AVERAGE_RATE_TYPE.
  • GCS_CONS_RELATIONSHIPS — the dependent child table, linking each consolidation relationship back to its currency treatment through CURR_TREATMENT_ID.
  • FND_DM_PRODUCTS — referenced through PRODUCT_ID for dimensional scoping.
  • GCS_CURR_TREATMENTS_TL — the translated-language companion table typically paired with _B tables for descriptive text.
  • GL_LEDGERS — provides functional and reporting currency context for the treatments applied.
  • Standard EBS audit and user tables (FND_USER, FND_TASKS) support the CREATED_BY, LAST_UPDATED_BY, and TASK_ID columns.