Search Results epb_table_name




Overview
Explore in AI Chat

Overview

GCS.GCS_SYSTEM_OPTIONS is a seed configuration table owned by the GCS schema that stores system-level setup parameters for Oracle Financial Consolidation Hub (FCH), a component of the Enterprise Performance Management (EPM) and Enterprise Trial Balance Reporting (ETRM) stack delivered with Oracle E-Business Suite 12.1.1 and 12.2.2. The table occupies the APPS_TS_SEED tablespace, which is reserved for setup and seed data rather than transactional volume, and it carries standard Oracle Applications "Who" audit columns alongside an OBJECT_VERSION_NUMBER column that supports optimistic locking during concurrent updates.

Rows in this table define, by name, the XML publisher or spreadsheet templates that Financial Consolidation Hub uses for each stage of the consolidation pipeline — acquisition and disposal trial balances, data submission loads, trial balances, journal entries, intercompany matching, hierarchy listings, valueset map validation, and writeback. As a result, the table functions as a central registry of template assignments, and each setup record is consumed by consolidation, data submission, and reporting processes maintained by various GCS packages and concurrent programs.

The metadata's heuristic Data Vault classification marks this table as standalone, meaning the mining exercise did not detect a surrounding hub/link/satellite structure rooted at this object. In practice, however, SYSTEM_OPTION_ID behaves as a surrogate business key stable across environments, and the table itself resembles a single-row-per-configuration satellite: one current row describes the active template configuration, while the audit columns capture when it was last changed. Solution architects should treat the object as a lightweight configuration dimension rather than a traditional transactional table.

Key Information Stored

Although the physical schema contains 23 columns, only a subset carries meaningful consolidation semantics. The most important columns include:

The remaining audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) conform to the standard Oracle Applications WHO columns and are useful for change tracking rather than business meaning.

Common Use Cases and Queries

The primary diagnostic use case is verifying which templates are associated with the active consolidation configuration before running a consolidation program or publishing reports. Administrators frequently query AD_TEMPLATE_CODE after an upgrade to confirm that acquisition and disposal templates carried forward correctly between releases. Typical SQL patterns include:

  • Selecting the active configuration row to confirm template assignments: SELECT system_option_id, tb_template_code, ad_template_code, ds_tb_template_code, interco_match_template_code FROM gcs.gcs_system_options;
  • Checking intercompany setup: filter on INTERCO_MAP_ENABLED_FLAG to confirm intercompany mapping or matching is enabled and that the associated template codes are populated.
  • Auditing recent changes: order by LAST_UPDATE_DATE and review LAST_UPDATED_BY to determine who last touched the system options.
  • Reporting template inventory across environments by joining the various TEMPLATE_CODE columns to XML Publisher definitions or GCS template definition tables.

Because the table resides in APPS_TS_SEED and is referenced by consolidation engine code, direct DML should be avoided; changes should flow through the standard setup forms or supported APIs to keep the OBJECT_VERSION_NUMBER consistent.

Related Objects

The documented foreign-key data records a self-referencing relationship, GCS_SYSTEM_OPTIONS.SYSTEM_OPTION_ID referencing CS_SYSTEM_OPTIONS, which indicates the object participates in a small configuration cluster. Additional significant objects that depend on or reference GCS_SYSTEM_OPTIONS include the GCS consolidation and template definition tables that resolve the TEMPLATE_CODE columns, GCS data submission tables that consume DS_TB_TEMPLATE_CODE and DS_LOAD_TEMPLATE_CODE, intercompany matching tables that consume INTERCO_MATCH_TEMPLATE_CODE, and the GCS hierarchy definition tables referenced through LN_ITEM_HIERARCHY_OBJ_ID. The GCS system options setup form and the Financial Consolidation Hub concurrent programs that read the template codes at runtime also constitute downstream dependents of this seed table. When reviewing dependencies in EBS 12.1.1 or 12.2.2, administrators should treat this object as a low-volume, high-impact seed configuration element whose contents must be validated whenever consolidation behavior or report output changes unexpectedly.