Search Results gcs_system_options




Overview
Explore in AI Chat

Overview

GCS_SYSTEM_OPTIONS is a setup table in the GCS (Financial Consolidation Hub) product of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores system-level configuration for Financial Consolidation Hub, the module responsible for aggregating, translating, and consolidating subsidiary ledger data into a corporate reporting entity. The table is owned by the GCS schema and is marked VALID in the ETRM repository. Its documented physical schema under 12.1.1 contains 23 columns, governed by a single unique index, GCS_SYSTEM_OPTIONS_U1, defined on SYSTEM_OPTION_ID.

From a data-modeling standpoint, the ETRM metadata classifies this object heuristically as a standalone satellite. This classification should be treated as a modeling suggestion rather than a normative statement: the table carries descriptive configuration attributes keyed by a surrogate identifier, with no strong multi-parent dependency graph identified in the mined foreign-key structure. The FK metadata shows a single outgoing reference from GCS_SYSTEM_OPTIONS.SYSTEM_OPTION_ID to CS_SYSTEM_OPTIONS, indicating that the GCS row inherits or mirrors an option identifier from the CS (Consolidation) schema. In practice, this table behaves as a configuration singleton or near-singleton per consolidation deployment, defining which Enterprise Planning and Budgeting (EPB) and consolidation templates, hierarchies, and matching behaviors are active.

Key Information Stored

The surrogate primary key and unique business-key candidate is SYSTEM_OPTION_ID, which identifies each system option record and serves as the join key to CS_SYSTEM_OPTIONS. The remaining columns fall into several functional clusters.

Common Use Cases and Queries

Administrators and technical consultants query this table to verify which templates and intercompany settings are active for a given consolidation configuration, especially after cloning a production instance or troubleshooting template resolution errors. A typical lookup retrieves the current option set:

  • SELECT system_option_id, tb_template_code, entry_template_code, interco_map_enabled_flag FROM gcs.gcs_system_options;
  • Joining to the parent to correlate CS-level and GCS-level option identifiers: SELECT g.system_option_id, g.tb_template_code, c.* FROM gcs.gcs_system_options g JOIN cs.cs_system_options c ON g.system_option_id = c.system_option_id;
  • Auditing configuration drift across environments by comparing INTERCO_MAP_ENABLED_FLAG and template codes between instances.
  • Reporting on recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The most significant related objects are those tied to the documented foreign-key path and the consolidation configuration surface:

  • CS_SYSTEM_OPTIONS — parent option table joined on SYSTEM_OPTION_ID; the documented FK target.
  • GCS_SYSTEM_OPTIONS_U1 — unique index on SYSTEM_OPTION_ID enforcing the business key.
  • Template definition tables referenced by the various *_TEMPLATE_CODE columns (trial balance, entry, data load, intercompany match, hierarchy list, value map, writeback).
  • Hierarchy metadata objects referenced by LN_ITEM_HIERARCHY_OBJ_ID.
  • FCH global value-set combination records associated with FCH_GLOBAL_VS_COMBO_ID.

Because the table is a standalone satellite, its dependencies are primarily logical references to configuration entities rather than enforced child FKs, so integrity is maintained by the consolidation setup UI and concurrent program logic rather than by database constraints alone.