Search Results gcs_cons_impact_analyses_pk

Overview

The GCS_CONS_IMPACT_ANALYSES table is a core data repository within Oracle E-Business Suite's Financial Consolidation Hub (GCS) module, specifically for releases 12.1.1 and 12.2.2. It is designed to store detailed impact analysis information generated during consolidation processes. The table's primary role is to track and audit the downstream effects of various consolidation activities, such as changes to ownership percentages, intercompany relationships, or data submissions. By maintaining a historical and analytical record of these impacts, the table enables financial controllers and system administrators to understand the consequences of consolidation adjustments before finalizing them, ensuring data integrity and auditability throughout the financial close cycle.

Key Information Stored

The table's structure is centered around linking consolidation impacts to specific transactional and master data entities. Its primary key is the IMPACT_ANALYSIS_ID, which uniquely identifies each impact analysis record. The table's significance is further defined by its numerous foreign key relationships, which point to critical transactional headers and master data. Key columns include PRE_RELATIONSHIP_ID, which links to the GCS_CONS_RELATIONSHIPS table to identify the ownership or intercompany relationship that was changed. Multiple entry-related columns—STAT_ENTRY_ID, ENTRY_ID, ORIGINAL_ENTRY_ID, and PRE_PROP_ENTRY_ID—all reference the GCS_ENTRY_HEADERS table, allowing the system to track the specific journal entries created, modified, or proposed as a result of the impact analysis. The LOAD_ID column references the GCS_DATA_SUB_DTLS table, connecting the impact analysis to a specific data submission or load process.

Common Use Cases and Queries

This table is primarily accessed for audit, troubleshooting, and reporting purposes within the consolidation workflow. A common use case is tracing the lineage of consolidation adjustments to understand which relationship change triggered specific journal entries. System administrators may query this table to diagnose issues in the impact analysis engine or to purge historical analysis data as part of a maintenance cycle. A typical reporting query would join this table to its referenced entities to provide a comprehensive audit trail.

Sample Query Pattern:

• SELECT ia.IMPACT_ANALYSIS_ID, eh.ENTRY_NAME, cr.RELATIONSHIP_NAME FROM GCS_CONS_IMPACT_ANALYSES ia LEFT JOIN GCS_ENTRY_HEADERS eh ON ia.ENTRY_ID = eh.ENTRY_ID LEFT JOIN GCS_CONS_RELATIONSHIPS cr ON ia.PRE_RELATIONSHIP_ID = cr.RELATIONSHIP_ID WHERE ia.LOAD_ID = :p_load_id;

Related Objects

The GCS_CONS_IMPACT_ANALYSES table has defined dependencies on several key GCS tables, as documented by its foreign key constraints. These relationships are fundamental to its role in the consolidation data model.

• GCS_CONS_RELATIONSHIPS: Joined via GCS_CONS_IMPACT_ANALYSES.PRE_RELATIONSHIP_ID. This links an impact analysis record to the specific consolidation relationship (e.g., ownership percentage) that was evaluated or changed.
• GCS_ENTRY_HEADERS: Joined via multiple columns (STAT_ENTRY_ID, ENTRY_ID, ORIGINAL_ENTRY_ID, PRE_PROP_ENTRY_ID). These links associate the analysis with the various consolidation journal entries it generated or affected, including statistical, standard, original, and proposed/provisional entries.
• GCS_DATA_SUB_DTLS: Joined via GCS_CONS_IMPACT_ANALYSES.LOAD_ID. This connects the impact analysis to the source data submission detail, providing context on the data load that initiated the consolidation process.