Search Results gcs_dataset_codes




Overview
Explore in AI Chat

Overview

The GCS_DATASET_CODES table is a core data definition table within Oracle E-Business Suite's Financial Consolidation Hub (GCS) module. It serves as a critical configuration object that defines and manages the permissible dataset codes associated with specific consolidation hierarchies. In essence, it establishes a controlled mapping between a consolidation hierarchy and the types of financial data (datasets) that can be loaded and processed within that hierarchy. This table enforces data integrity by ensuring that only authorized balance types are processed for a given consolidation structure, forming a foundational element of the consolidation data model.

Key Information Stored

The table's structure is defined by a composite primary key, which dictates the core business rule it enforces. The two key columns are HIERARCHY_ID and BALANCE_TYPE_CODE. The HIERARCHY_ID column stores a unique identifier that links directly to a specific consolidation hierarchy defined in the GCS_HIERARCHIES_B table. The BALANCE_TYPE_CODE column stores the code representing a specific type of financial dataset, such as Actual, Budget, or Forecast balances. The combination of these two columns creates a unique record authorizing that dataset type for use within the linked hierarchy. While the provided metadata focuses on these key columns, typical implementations may include descriptive and control columns like CREATION_DATE or LAST_UPDATE_DATE, governed by standard Oracle EBS audit triggers.

Common Use Cases and Queries

This table is primarily referenced during the setup and validation phases of the consolidation process. A common operational use case is to validate whether a specific balance type is allowed for a hierarchy before initiating a data load or consolidation run. Administrators may query this table to review or audit the dataset configuration for all hierarchies. For reporting, it is frequently joined to the hierarchy definition table to produce user-friendly lists.

Sample SQL to list all authorized datasets for a hierarchy:

  • SELECT h.hierarchy_name, d.balance_type_code FROM gcs_dataset_codes d, gcs_hierarchies_b h WHERE d.hierarchy_id = h.hierarchy_id ORDER BY 1, 2;

Sample SQL to validate a specific dataset for a process:

  • SELECT 'VALID' FROM gcs_dataset_codes WHERE hierarchy_id = :p_hierarchy_id AND balance_type_code = :p_balance_type;

Related Objects

The GCS_DATASET_CODES table maintains a strict foreign key relationship with the core hierarchy definition table, ensuring referential integrity. The documented relationship is:

  • GCS_HIERARCHIES_B: The table is referenced via the foreign key constraint where GCS_DATASET_CODES.HIERARCHY_ID column references GCS_HIERARCHIES_B.HIERARCHY_ID. This join is essential for retrieving the hierarchy name or other attributes. As a master configuration table, GCS_DATASET_CODES is likely referenced by various consolidation processing engine tables and views within the GCS module, though these specific dependencies are not detailed in the provided excerpt.