Search Results pre_cons_relationship_id

Overview

The GCS.GCS_AD_TRANSACTIONS table is a core data repository within the Oracle E-Business Suite (EBS) Global Consolidation System (GCS). Specifically, it is a foundational table for the Advanced Global Intercompany System (AGIS), which manages complex intercompany and equity transactions for financial consolidation. This table stores the master record of all advanced accounting transactions, such as acquisitions, disposals, and equity adjustments, that alter the ownership or consolidation relationships between entities in a corporate hierarchy. Its primary role is to serve as the system of record for these transactional events, enabling the accurate calculation of ownership percentages, consolidation treatments, and elimination entries during the financial close process in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's columns capture the complete lifecycle and attributes of an advanced transaction. The AD_TRANSACTION_ID serves as the unique primary key. Critical transactional attributes include PRE_CONS_RELATIONSHIP_ID and POST_CONS_RELATIONSHIP_ID, which define the consolidation relationship before and after the transaction event, respectively. The TRANSACTION_TYPE_CODE and ENTRY_TYPE_CODE classify the nature of the transaction. The ASSOC_ENTRY_ID column, which was the focus of the user's search, is a defining column that links this transaction to an associated journal entry or another transactional record, establishing a critical lineage for audit and reconciliation. Other significant columns include TOTAL_CONSIDERATION for the monetary value involved, CAL_PERIOD_ID and TRANSACTION_DATE for period identification, and the standard WHO columns for tracking changes.

Common Use Cases and Queries

This table is central to reporting and troubleshooting within AGIS. A common use case is tracing the impact of a specific transaction on consolidation relationships. For instance, to find all transactions that modified a particular relationship and their associated entries, one might query:

SELECT adt.transaction_type_code,
       adt.entry_type_code,
       adt.transaction_date,
       adt.assoc_entry_id,
       adt.pre_cons_relationship_id,
       adt.post_cons_relationship_id
FROM   gcs.gcs_ad_transactions adt
WHERE  adt.pre_cons_relationship_id = :p_rel_id
   OR  adt.post_cns_relationship_id = :p_rel_id
ORDER BY adt.transaction_date;

Another frequent scenario involves validating transaction batches by joining on the REQUEST_ID to link transactions to a specific concurrent process submission. Analysts also frequently query transactions within a specific calendar period using CAL_PERIOD_ID to support period-end closing activities.

Related Objects

The integrity of data in GCS_AD_TRANSACTIONS is maintained through defined relationships with other consolidation objects. The table's primary key is enforced by the GCS_AD_TRANSACTIONS_PK constraint on AD_TRANSACTION_ID. As per the provided metadata, it contains several foreign key relationships that are essential for joins in reporting and application logic:

• PRE_CONS_RELATIONSHIP_ID references a consolidation relationship ID in a related GCS table (e.g., GCS_CONS_RELATIONSHIPS).
• POST_CONS_RELATIONSHIP_ID similarly references a consolidation relationship ID in a related table.
• ASSOC_ENTRY_ID references an associated entry identifier, likely in a journal entry or transaction detail table such as GCS_ENTRIES or a related subledger table, forming a critical link between the transactional event and its accounting impact.

These relationships are pivotal for constructing accurate consolidation reports and ensuring data consistency across the Global Consolidation System.