Search Results gcs_role_entity_relns_pk

Overview

GCS_ROLE_ENTITY_RELNS is a table in the GCS schema (Financial Consolidation Hub) within Oracle E-Business Suite 12.1.1 and 12.2.2. As its name and the ETRM description indicate, it stores role and entity relationship information — the association between security roles and the consolidation entities those roles are authorized to access. This is the object that helps drive access control and data visibility within Financial Consolidation Hub, ensuring users assigned to a role can only view, consolidate, and report on the entities they are entitled to see.

The heuristic Data Vault classification for this object is standalone, meaning it does not behave as a convention-al hub, link, or satellite and must be modeled as an independent relation. This is consistent with the table's nature: it is a security mapping table that links a role to an entity within a given origin system and partition. The classification is offered as a modeling suggestion rather than a documented fact.

Key Information Stored

The table's documented physical schema contains 11 columns. The primary key is defined by the constraint GCS_ROLE_ENTITY_RELNS_PK on (ROLE_NAME, ORIG_SYSTEM, ORIG_SYSTEM_ID, PARTITION_ID, ENTITY_ID) — a natural composite key rather than a single surrogate identifier. A separate unique index, GCS_ROLE_ENTITY_RELNS_U1 on (ROLE_NAME, ORIG_SYSTEM_ID, PARTITION_ID, ENTITY_ID), serves as the business-key candidate. The most important columns are:

• ROLE_NAME — the name of the security role associated with an entity; a leading column in both the primary key and unique index.
• ENTITY_ID — identifies the consolidation entity to which the role is related.
• ORIG_SYSTEM and ORIG_SYSTEM_ID — the source system reference and its identifier, allowing relation-ships originating from external systems to be tracked alongside native EBS data.
• PARTITION_ID — the partition under which the relationship is scoped, supporting data segmentation and multi-tenant style isolation.
• OBJECT_VERSION_NUMBER — supports optimistic locking, incremented on each update to prevent lost updates in concurrent editing.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified each row and when.

Common Use Cases and Queries

The principal use case is validating and reporting on role-to-entity authorization for consolidation activities. A typical query retrieves all entities authorized for a given role:

• SELECT ENTITY_ID FROM GCS_ROLE_ENTITY_RELNS WHERE ROLE_NAME = :role;
• Reporting entities by partition: SELECT ROLE_NAME, ENTITY_ID FROM GCS_ROLE_ENTITY_RELNS WHERE PARTITION_ID = :part;
• Auditing recently changed relationships: SELECT * FROM GCS_ROLE_ENTITY_RELNS WHERE LAST_UPDATE_DATE > :since;
• Identifying external-source mappings: SELECT ORIG_SYSTEM, ORIG_SYSTEM_ID FROM GCS_ROLE_ENTITY_RELNS WHERE ORIG_SYSTEM IS NOT NULL;

Because the primary key includes ROLE_NAME, ORIG_SYSTEM, and PARTITION_ID, joins back to entity and role master tables should filter on all key components to avoid duplicate rows.

Related Objects

The ETRM metadata documents this object as standalone, so no formal foreign keys are recorded. The following objects are the most significant logical counterparts based on the join columns present:

• ENTITY_ID — resolves to the consolidation entity definition table in the GCS schema.
• ROLE_NAME — corresponds to the role definition object used by Financial Consolidation Hub security.
• ORIG_SYSTEM / ORIG_SYSTEM_ID — link to origin-system reference data used for cross-system entity mapping.
• PARTITION_ID — relates to the partition configuration controlling data scoping.
• GCS_ROLE_ENTITY_RELNS_PK and GCS_ROLE_ENTITY_RELNS_U1 — the key constraints that enforce uniqueness on the relationship.

Administrators should treat this table as the authoritative mapping of role-to-entity authorization when troubleshooting visibility or consolidation access issues.