Results for “gcs_entities_attr”

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

Overview

GCS_ENTITIES_ATTR is a Financial Consolidation Hub (GCS) table that stores additional data type information for consolidation entities. In Oracle EBS 12.1.1 and 12.2.2, Financial Consolidation Hub provides a centralized repository for aggregating subsidiary and parent entity results, applying transformation and validation rules, and producing consolidated financial statements. The GCS_ENTITIES_ATTR table extends the core entity definition held in GCS_ENTITIES by capturing, per entity and per data type, the applicable ledger, source system, and rule set assignments.

The object resides in the GCS schema and is classified as VALID within the ETRM data dictionary. The documented physical schema contains 15 columns, with a composite primary key defined by GCS_ENTITIES_ATTR_PK on (ENTITY_ID, DATA_TYPE_CODE). A unique index, GCS_ENTITIES_ATTR_U1 on (ENTITY_ID, DATA_TYPE_CODE, EFFECTIVE_START_DATE), acts as a business-key candidate and confirms that the table is date-effectivity enabled. From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as a standalone structure. Rather than serving as a pure hub, link, or satellite, it behaves as an entity-attribute detail table combining entity and data type references with rule and ledger context, which is a modeling suggestion only.

Key Information Stored

The most significant columns define which processing rules apply to an entity for a given data type and effective period:

• ENTITY_ID — Identifier of the consolidation entity; part of the composite primary key and the principal join back to the entity definition.
• DATA_TYPE_CODE — Distinguishes the type of entity data (for example, balances versus supplementary detail); the second component of the primary key.
• LEDGER_ID — The ledger associated with the entity and data type, linking financial data to the correct accounting representation.
• SOURCE_SYSTEM_CODE — Identifies the originating source system or application that supplied the data.
• BALANCES_RULE_ID — References the balances rule applied when extracts are produced for this entity and data type.
• TRANSFORM_RULE_SET_ID — References the transformation rule set applied during consolidation processing.
• VALIDATION_RULE_SET_ID — References the validation rule set used to verify data before or during consolidation.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — Date-effectivity boundaries that allow historical tracking of entity attribute changes and support the unique index.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — Standard EBS audit and optimistic locking columns present on the majority of transactional tables.

The surrogate or composite primary key is the pairing of ENTITY_ID and DATA_TYPE_CODE. The business-key candidate evidenced by GCS_ENTITIES_ATTR_U1 extends this pairing with EFFECTIVE_START_DATE, giving each entity/data type combination a versioned history.

Common Use Cases and Queries

Typical usage includes verifying which ledger and rule sets are attached to an entity before a consolidation run, auditing changes to rule assignment across periods, and joining entity attributes to balances or transformation metadata for reporting.

• Listing active rule assignments for a consolidation entity.
• Reconciling source systems against entity-to-ledger mappings for an extract.
• Historical analysis of transformation or validation rule changes.

A representative query to return the current row for an entity and data type is:

• SELECT entity_id, data_type_code, ledger_id, source_system_code, balances_rule_id, transform_rule_set_id, validation_rule_set_id FROM gcs.gcs_entities_attr WHERE entity_id = :entity_id AND data_type_code = :data_type_code AND TRUNC(SYSDATE) BETWEEN effective_start_date AND NVL(effective_end_date, TRUNC(SYSDATE));

For trending, aggregate by effective_start_date to observe when rule sets changed. Because the physical schema is standalone in the mined relationship data, joins to other GCS tables are driven by ENTITY_ID rather than by enforced database constraints, so applications and reports are responsible for maintaining referential integrity.

Related Objects

The following objects are the most significant counterparts for joining or interpreting GCS_ENTITIES_ATTR:

• GCS_ENTITIES — the parent entity definition; join on ENTITY_ID to obtain entity names and consolidation hierarchy context.
• GCS_ENTITIES_ATTR_PK — the primary-key constraint on (ENTITY_ID, DATA_TYPE_CODE).
• GCS_ENTITIES_ATTR_U1 — the unique business-key index on (ENTITY_ID, DATA_TYPE_CODE, EFFECTIVE_START_DATE).
• GL_LEDGERS — resolves LEDGER_ID to the ledger name and chart of accounts.
• GCS_BALANCES_RULES — resolves BALANCES_RULE_ID to the balances rule definition.
• GCS_TRANSFORM_RULE_SETS — resolves TRANSFORM_RULE_SET_ID to the transformation rule set.
• GCS_VALIDATION_RULE_SETS — resolves VALIDATION_RULE_SET_ID to the validation rule set.
• GCS_SOURCE_SYSTEMS — resolves SOURCE_SYSTEM_CODE to the source system definition.

Because the metadata documents a standalone classification, these relationships should be treated as logical joins rather than database-enforced foreign keys, and any dependent reporting or integration logic must enforce consistency through application-level validation.