Search Results hrate_enabled_flag

Overview

GCS.GCS_EPB_DIM_MAPS is a seed data table owned by the GCS schema within Oracle E-Business Suite. Its documented purpose is to store the dimension mapping from FCH (Financial Consolidation Hub) to EPB (Enterprise Planning and Budgeting) for reporting purposes in EPB. In practical terms, the table acts as a cross-reference dictionary that translates column names used in the FCH data model into their equivalent column names in the EPB reporting model, allowing EPB reports to resolve the correct source attributes when consolidating or presenting financial data.

The object resides in the APPS_TS_SEED tablespace, a standard location for reference and setup data that is shipped and maintained by Oracle rather than created ad hoc by customers. Its status is VALID in the documented release (ETRM 12.1.1), and the underlying FND Design Data identifier is GCS.GCS_EPB_DIM_MAPS. From a heuristic Data Vault modeling perspective, this object is classified as a standalone structure; it participates in no foreign key relationships to other tables and is therefore best treated as an independent reference or lookup table rather than as a hub, link, or satellite within a Data Vault model. The absence of foreign key dependencies confirms that it functions as a self-contained mapping dictionary.

Key Information Stored

The table contains ten documented columns. The most functionally significant are the two mapping columns, which together define the purpose of the object:

• GCS_COLUMN (VARCHAR2, 30) — the source GCS/FCH column name. This column is the primary key of the table via GCS_EPB_DIM_MAPS_PK and is also the single column of the unique index GCS_EPB_DIM_MAPS_U1, making it the definitive business-key candidate as well as the physical surrogate key in this case.
• EPB_COLUMN (VARCHAR2, 30) — the corresponding target EPB column name to which the GCS column is mapped.
• ENABLED_FLAG (VARCHAR2) — indicates whether the mapping row is active and should be honored during EPB reporting.
• HRATE_ENABLED_FLAG (VARCHAR2) — a secondary flag controlling whether historical rates are enabled for the mapped dimension.
• OBJECT_VERSION_NUMBER (NUMBER, 15) — the standard EBS optimistic-locking version counter, incremented on each update to detect concurrent modifications.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Who columns that audit record creation and the most recent modification, including the responsible application user and login session.

Because GCS_COLUMN is both the primary key and the unique-index column, no surrogate key distinct from the business key exists; each GCS column name may appear only once in the table.

Common Use Cases and Queries

The primary use case is resolving the mapping between FCH source columns and EPB destination columns when building or troubleshooting EPB financial reports. A typical query retrieves the active mapping for reporting:

• Retrieve all enabled mappings: SELECT gcs_column, epb_column FROM gcs.gcs_epb_dim_maps WHERE enabled_flag = 'Y';
• Look up the EPB target for a specific GCS source column: SELECT epb_column FROM gcs.gcs_epb_dim_maps WHERE gcs_column = :source_column;
• Identify mappings that have historical rates enabled: SELECT gcs_column, epb_column FROM gcs.gcs_epb_dim_maps WHERE hrate_enabled_flag = 'Y';
• Audit recent changes to the mapping setup using the Who columns: SELECT gcs_column, last_updated_by, last_update_date FROM gcs.gcs_epb_dim_maps ORDER BY last_update_date DESC;

Administrators use the table to verify that every FCH dimension required by a report has a corresponding EPB column and that the mapping is enabled before running consolidation or budgeting reports.

Related Objects

The documented dependency information states that GCS_EPB_DIM_MAPS does not reference any database object and is referenced by the APPS synonym GCS_EPB_DIM_MAPS, through which application code and reports access the table. Because the catalog records no foreign key relationships, there are no join columns to other GCS or FCH tables within this object itself; joins to FCH and EPB source tables are performed logically on the GCS_COLUMN and EPB_COLUMN values rather than through declared constraints. Consumers should therefore treat the table as a standalone reference lookup whose integrity is maintained by the application and seed data rather than by referential constraints.