Search Results gcs_cons_relationships
Overview
The GCS_CONS_RELATIONSHIPS table is a core data object within Oracle E-Business Suite's Financial Consolidation Hub (GCS) module. It serves as the central repository for storing the structural definitions of relationships between entities within a consolidation hierarchy. These relationships are fundamental to the consolidation process, as they define the parent-child links between legal entities, business units, or other consolidation nodes. The table's primary role is to store the metadata that dictates how financial data is aggregated, rolled up, and treated during the consolidation close, directly supporting the calculation of ownership percentages, elimination entries, and currency translations.
Key Information Stored
The table's primary key is the CONS_RELATIONSHIP_ID, a unique system-generated identifier for each hierarchical link. Other critical foreign key columns define the context and rules for each relationship. The HIERARCHY_ID links to GCS_HIERARCHIES_B, identifying the specific consolidation hierarchy version. The TREATMENT_ID references GCS_TREATMENTS_B to define the standard consolidation method (e.g., full, proportional, equity) for the relationship. The CURR_TREATMENT_ID references GCS_CURR_TREATMENTS_B, specifying the currency translation treatment to be applied. Additional columns, inferred from standard GCS design, would typically include identifiers for the parent and child nodes, effective dates, and sequencing information.
Common Use Cases and Queries
This table is central to hierarchy maintenance, validation reporting, and consolidation engine processing. Common operational and reporting queries include validating the setup of a specific hierarchy, analyzing treatment assignments, and troubleshooting consolidation results. A typical query pattern retrieves the full structure of a hierarchy for review:
- SELECT cr.cons_relationship_id, cr.parent_id, cr.child_id, h.hierarchy_name, t.treatment_name FROM gcs_cons_relationships cr, gcs_hierarchies_b h, gcs_treatments_b t WHERE cr.hierarchy_id = h.hierarchy_id AND cr.treatment_id = t.treatment_id AND h.hierarchy_id = :p_hierarchy_id ORDER BY cr.parent_id, sequence_num;
Another critical use case is impact analysis, where the system references existing relationships (via PRE_RELATIONSHIP_ID) to model the effects of proposed hierarchy changes before they are implemented.
Related Objects
The GCS_CONS_RELATIONSHIPS table has defined foreign key relationships with several key GCS setup tables, as documented in the ETRM metadata:
- References To (Parent Tables):
- GCS_HIERARCHIES_B: Joined via HIERARCHY_ID. This provides the master hierarchy definition.
- GCS_TREATMENTS_B: Joined via TREATMENT_ID. This defines the consolidation method (e.g., Full, Equity, Proportional).
- GCS_CURR_TREATMENTS_B: Joined via CURR_TREATMENT_ID. This defines the currency translation rule.
- Referenced By (Child Table):
- GCS_CONS_IMPACT_ANALYSES: Joined via PRE_RELATIONSHIP_ID referencing CONS_RELATIONSHIP_ID. This table stores simulation data for proposed hierarchy changes.
-
Table: GCS_CONS_RELATIONSHIPS
12.2.2
product: GCS - Financial Consolidation Hub (Obsolete) , description: GCS consolidation hierarchy relationship information , implementation_dba_data: Not implemented in this database ,
-
Table: GCS_TREATMENTS_B
12.2.2
product: GCS - Financial Consolidation Hub (Obsolete) , description: Consolidation treatments , implementation_dba_data: Not implemented in this database ,
-
Table: GCS_CURR_TREATMENTS_B
12.2.2
product: GCS - Financial Consolidation Hub (Obsolete) , description: Consolidation currency treatments , implementation_dba_data: Not implemented in this database ,
-
Table: GCS_CONS_IMPACT_ANALYSES
12.2.2
product: GCS - Financial Consolidation Hub (Obsolete) , description: Impact Analysis information for consolidation processes , implementation_dba_data: Not implemented in this database ,
-
Table: GCS_HIERARCHIES_B
12.2.2
product: GCS - Financial Consolidation Hub (Obsolete) , description: GCS hierarchy header information , implementation_dba_data: Not implemented in this database ,