Results for “gcs_dataset_codes”

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

Overview

GCS_DATASET_CODES is a configuration table belonging to the GCS – Financial Consolidation Hub product family. Its documented purpose is to hold GCS hierarchy dataset code information, meaning it maps consolidation hierarchies to the datasets and balance types that are valid within each hierarchy. In Oracle EBS 12.1.1 and 12.2.2, the object is registered in the E-Business Suite data dictionary under the GCS schema and is associated with eight documented columns.

The ETRM metadata explicitly notes that this table is "Not implemented in this database" at the referenced implementation level, and the product itself is flagged as obsolete. As a result, GCS_DATASET_CODES will not be present in every environment; it appears only where Financial Consolidation Hub hierarchy configuration has been deployed or historically seeded. Consultants encountering the object in a legacy 12.1.1 or 12.2.2 instance should treat it as a configuration/support table rather than a transactional one.

Applying Data Vault modeling heuristics to the documented foreign key structure, GCS_DATASET_CODES is satellite-leaning: it carries descriptive attributes (BALANCE_TYPE_CODE, DATASET_CODE) that qualify a parent hierarchy record rather than acting as an independent hub or a pure many-to-many link. This classification is a modeling suggestion derived from the FK topology and should not be interpreted as a physical Data Vault implementation.

Key Information Stored

The primary key, GCS_DATASET_CODES_PK, is composite and comprises HIERARCHY_ID and BALANCE_TYPE_CODE. HIERARCHY_ID is a foreign key to GCS_HIERARCHIES_B, anchoring each row to a consolidation hierarchy definition. BALANCE_TYPE_CODE identifies the balance type for which a dataset mapping is defined. Together these two columns guarantee a single dataset assignment per hierarchy and balance type combination.

Two unique indexes document the business-key candidates for the table:

• GCS_DATASET_CODES_U1 (HIERARCHY_ID, BALANCE_TYPE_CODE) — mirrors the primary key and reinforces uniqueness of the hierarchy/balance type pairing.
• GCS_DATASET_CODES_U2 (HIERARCHY_ID, DATASET_CODE) — enforces that a given DATASET_CODE is assigned only once within a hierarchy, providing an alternate uniqueness path.

DATASET_CODE is the substantive business attribute, identifying the dataset associated with the hierarchy and balance type. The remaining documented columns are standard EBS audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These record who created and last modified each configuration row and when, and are populated by the standard EBS WHO columns mechanism. Of the eight documented columns, HIERARCHY_ID, BALANCE_TYPE_CODE, and DATASET_CODE form the functional core; the audit columns support change tracking, reconciliation of configuration drift, and troubleshooting of setup history.

Common Use Cases and Queries

The principal use case is validating and reporting Financial Consolidation Hub hierarchy setup. Because the table governs which datasets and balance types are permitted under each hierarchy, administrators and support analysts query it to confirm that consolidation runs will resolve the expected datasets for a given balance type.

A representative query lists all dataset mappings for a hierarchy:

• SELECT hierarchy_id, balance_type_code, dataset_code FROM gcs_dataset_codes WHERE hierarchy_id = :p_hierarchy_id ORDER BY balance_type_code;

To locate the hierarchy associated with a specific dataset, join to the parent table:

• SELECT h.hierarchy_id, h.name, d.balance_type_code, d.dataset_code FROM gcs_dataset_codes d, gcs_hierarchies_b h WHERE d.hierarchy_id = h.hierarchy_id AND d.dataset_code = :p_dataset_code;

Reporting scenarios include extracting the full balance-type-to-dataset matrix per hierarchy for consolidation design reviews, auditing configuration changes by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY, and diagnosing reconciliation discrepancies where a balance type maps to an unexpected dataset.

Related Objects

The most significant relationship is with the parent hierarchy table, driven by the documented foreign key:

• GCS_HIERARCHIES_B — joined on GCS_DATASET_CODES.HIERARCHY_ID = GCS_HIERARCHIES_B.HIERARCHY_ID; this reference supplies the hierarchy definition that each dataset code qualifies.
• GCS_DATASET_CODES_PK — the composite primary key constraint on (HIERARCHY_ID, BALANCE_TYPE_CODE).
• GCS_DATASET_CODES_U1 — unique index on (HIERARCHY_ID, BALANCE_TYPE_CODE).
• GCS_DATASET_CODES_U2 — unique index on (HIERARCHY_ID, DATASET_CODE).

Other GCS hierarchy and consolidation objects in the same product family may reference hierarchy identifiers in a comparable manner, but they are not confirmed by the metadata provided. Given the obsolete status of the Financial Consolidation Hub, later consolidation architectures supersede this table entirely. Practitioners should verify object existence in any given instance before relying on GCS_DATASET_CODES in custom queries or reports.