Search Results post_relationship_id

Overview

The GCS_CONS_IMPACT_ANALYSES table is a core data repository within the Oracle E-Business Suite Global Consolidation System (GCS) for releases 12.1.1 and 12.2.2. Its primary function is to store detailed impact analysis records that inform users of specific alterations to data or data structures which subsequently affect consolidation results. This table acts as a critical audit and diagnostic tool, enabling finance and consolidation managers to trace how changes in consolidation relationships, journal entries, or data loads propagate through and modify the final consolidated financial outcomes.

Key Information Stored

The table's columns are designed to capture the context of a consolidation run and the precise elements that were altered. Key defining and informational columns include:

• IMPACT_ANALYSIS_ID: The primary key uniquely identifying each impact analysis record.
• RUN_NAME, CONSOLIDATION_ENTITY_ID, CHILD_ENTITY_ID: Together, these define the specific consolidation process and entity hierarchy context for the analysis.
• PRE_RELATIONSHIP_ID and POST_RELATIONSHIP_ID: These columns are central to tracking changes in consolidation rules. They store the identifiers for the consolidation relationship before (PRE) and after (POST) a change, directly linking to the GCS_CONS_RELATIONSHIPS table.
• ENTRY_ID, ORIGINAL_ENTRY_ID, PRE_PROP_ENTRY_ID, STAT_ENTRY_ID: This suite of columns references various types of journal entries (from GCS_ENTRY_HEADERS) that may be impacted, such as standard, original, pre-proportional, or statistical entries.
• MESSAGE_NAME: Stores the application message code that describes the nature of the impact.
• LOAD_ID: References the GCS_DATA_SUB_DTLS table, linking the impact to a specific data submission or load process.

Common Use Cases and Queries

A primary use case is auditing the effect of a modified consolidation relationship. For a user who searched for "pre_relationship_id", a typical query would identify all impacts resulting from a change to a specific prior relationship. This is essential for understanding the downstream effects of configuration updates.

Sample Query: To find all impact analyses triggered by a change to a specific prior relationship and the associated message:

SELECT ia.run_name,
       ia.consolidation_entity_id,
       ia.child_entity_id,
       ia.message_name,
       ia.post_relationship_id
  FROM gcs.gcs_cons_impact_analyses ia
 WHERE ia.pre_relationship_id = :specific_relationship_id
 ORDER BY ia.creation_date DESC;

Another common reporting scenario involves analyzing impacts for a particular consolidation run to assess data integrity or explain variances between expected and actual results.

Related Objects

The table maintains integral relationships with other GCS foundation tables through foreign key constraints, as documented in the ETRM metadata:

• GCS_CONS_RELATIONSHIPS: Via PRE_RELATIONSHIP_ID and POST_RELATIONSHIP_ID. This is the most direct link to consolidation hierarchy and rule definitions.
• GCS_ENTRY_HEADERS: Via multiple columns including STAT_ENTRY_ID, ENTRY_ID, ORIGINAL_ENTRY_ID, and PRE_PROP_ENTRY_ID. These links trace impacts to specific journal entries.
• GCS_DATA_SUB_DTLS: Via LOAD_ID. This connects the impact record to the source data load process.

The table's primary key is enforced by the GCS_CONS_IMPACT_ANALYSES_PK constraint on IMPACT_ANALYSIS_ID.