Search Results gcs_ad_transactions_pk

Overview

The GCS_AD_TRANSACTIONS table is a core data object within Oracle E-Business Suite's Financial Consolidation Hub (GCS) module. It serves as the central repository for acquisition and disposal (A&D) transaction control records. In the context of corporate consolidations, this table is critical for tracking the financial and ownership impacts of events such as mergers, acquisitions, and divestitures across reporting periods. Its primary role is to maintain the most current state of these transactions, enabling the consolidation engine to accurately apply ownership percentage changes, goodwill calculations, and elimination entries when generating consolidated financial statements for legal entities and reporting hierarchies.

Key Information Stored

While the provided metadata does not list specific columns beyond key identifiers, the table's structure is designed to manage the lifecycle of an A&D transaction. The primary key, AD_TRANSACTION_ID, uniquely identifies each transaction record. Crucially, the table stores foreign key references that link the transaction to the relevant consolidation relationships and journal entries. These include PRE_CONS_RELATIONSHIP_ID, which likely points to the ownership relationship before the transaction; POST_CONS_RELATIONSHIP_ID, pointing to the relationship after the transaction; and ASSOC_ENTRY_ID, which associates the transaction with its corresponding accounting entry in the consolidation journal. Other typical columns would store transaction dates, effective periods, transaction types (acquisition or disposal), and status flags to control processing workflow.

Common Use Cases and Queries

This table is primarily accessed for reporting on consolidation adjustments and troubleshooting consolidation runs. A common use case is to verify all A&D transactions processed for a specific consolidation entity and period. A typical query would join to relationship and entry tables to provide a comprehensive audit trail.

• Listing Transactions for a Period: SELECT ad_transaction_id, transaction_date FROM gcs_ad_transactions WHERE period_id = :p_period_num AND legal_entity_id = :p_legal_entity;
• Audit Trail for a Specific Entity: Queries often join GCS_AD_TRANSACTIONS to GCS_CONS_RELATIONSHIPS (via the pre- and post- IDs) and GCS_ENTRIES (via ASSOC_ENTRY_ID) to trace the full impact of a transaction from ownership change to posted journal entry.
• Data Fix Scripts: Support personnel may query and update status columns in this table to reprocess or correct stuck transactions during consolidation close.

Related Objects

The table is integral to the Consolidation Hub's data model, with defined foreign key relationships that ensure referential integrity. Based on the provided metadata:

• Primary Key: The table is accessed via its primary key constraint GCS_AD_TRANSACTIONS_PK on the column AD_TRANSACTION_ID.
• Foreign Key Dependencies: The table contains foreign key columns that reference other consolidation objects, though the specific target tables are denoted generically (%) in the metadata. In practice:
  • PRE_CONS_RELATIONSHIP_ID & POST_CONS_RELATIONSHIP_ID: These almost certainly reference the GCS_CONS_RELATIONSHIPS table, which stores ownership percentages between consolidating entities.
  • ASSOC_ENTRY_ID: This typically references the GCS_ENTRIES table, which stores the detailed consolidation journal entries generated as a result of the A&D transaction.

This table is a control point, feeding processed transaction data into the core consolidation engine to calculate equity eliminations and non-controlling interest.