Search Results gcs_role_hier_relns

Overview

The GCS_ROLE_HIER_RELNS table is a core data object within Oracle E-Business Suite's Financial Consolidation Hub (GCS) module. It functions as a junction table that establishes and maintains the critical relationships between user security roles and specific data hierarchies. This mapping is fundamental to the application's security and data access control model, ensuring that users, based on their assigned roles, can only view and process financial consolidation data for the hierarchies they are authorized to access. Its existence is essential for enforcing segregation of duties and providing a secure, multi-entity consolidation environment in both EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores the composite key that uniquely defines each role-to-hierarchy assignment. The primary key columns are ROLE_NAME, ORIG_SYSTEM, ORIG_SYSTEM_ID, PARTITION_ID, and HIERARCHY_ID. ROLE_NAME identifies the security role, while HIERARCHY_ID is a foreign key pointing to a specific hierarchy definition in the GCS_HIERARCHIES_B table. The ORIG_SYSTEM and ORIG_SYSTEM_ID columns provide context for the source system of the role or related data, which is important in multi-source consolidation landscapes. The PARTITION_ID is crucial for supporting data partitioning strategies, likely aligning with legal entity or consolidation ledger identifiers to optimize performance and data management.

Common Use Cases and Queries

A primary use case is auditing and reporting on security access. System administrators frequently query this table to verify which hierarchies a particular role can access or to list all roles authorized for a specific consolidation hierarchy. Common SQL patterns include joining to GCS_HIERARCHIES_B to get hierarchy details or to role tables (like FND_ROLES) for role descriptions. For example, to audit access for a specific role, one might execute: SELECT r.role_name, h.hierarchy_name FROM gcs_role_hier_relns r, gcs_hierarchies_b h WHERE r.hierarchy_id = h.hierarchy_id AND r.role_name = '&ROLE_NAME';. This table is also central during the user session initialization, where the application determines the permissible data set for the logged-in user based on their role memberships and the corresponding hierarchy mappings stored here.

Related Objects

The table has a direct and documented foreign key relationship, which is its primary structural dependency. The HIERARCHY_ID column references the GCS_HIERARCHIES_B table. This relationship ensures referential integrity, meaning a record in GCS_ROLE_HIER_RELNS cannot point to a non-existent hierarchy. The table is referenced by its primary key constraint (GCS_ROLE_HIER_RELNS_PK). While not listed in the provided metadata, it is logically a child table to the role definitions (potentially in FND_ROLES) and is a parent table to any application logic or views that consume the role-hierarchy relationship data to enforce security, making it a pivotal link in the GCS security architecture.