Search Results gcs_interco_elm_trx
Overview
The GCS_INTERCO_ELM_TRX table is a core data structure within the Oracle E-Business Suite (EBS) module GCS - Financial Consolidation Hub, which is now designated as obsolete. As its name indicates, this table serves as the primary repository for recording intercompany transaction details during the financial consolidation process. Its fundamental role is to store the granular data necessary for identifying, matching, and eliminating transactions between entities within a corporate group, a critical step in producing accurate consolidated financial statements that comply with accounting standards by preventing double-counting of internal profits and balances.
Key Information Stored
While the specific column list is not detailed in the provided metadata, the table's purpose and its documented foreign key relationship define its essential data elements. Based on its role as an intercompany transactions table, it would typically store attributes such as a unique transaction identifier, the source and target legal entities involved in the transaction, the transaction amount and currency, the accounting date, and a reference to the original source system transaction. Crucially, the metadata confirms the presence of a HIERARCHY_ID column. This key field links each transaction record to a specific consolidation hierarchy defined in the GCS_HIERARCHIES_B table, ensuring transactions are processed within the correct organizational and reporting structure.
Common Use Cases and Queries
The primary use case for this table is the intercompany reconciliation and elimination process within Financial Consolidation Hub. Data would be loaded or generated into this table from feeder systems, and consolidation engines would query it to identify reciprocal balances for netting. A typical analytical query would involve joining to the hierarchy table to report on unmatched intercompany transactions by consolidation group. For example:
SELECT COUNT(*), SUM(t.amount) FROM gcs_interco_elm_trx t WHERE t.hierarchy_id = :p_hier_id AND t.matched_flag = 'N';
Given the module's obsolete status, direct operational use in new implementations is discouraged. However, understanding its structure remains relevant for supporting legacy instances, data migration projects, or historical reporting from older consolidation cycles.
Related Objects
The documented metadata specifies a single, critical foreign key relationship for this table, establishing its dependency within the GCS data model.
- GCS_HIERARCHIES_B: This is the parent table for consolidation hierarchy definitions. The
GCS_INTERCO_ELM_TRX.HIERARCHY_IDcolumn references the primary key ofGCS_HIERARCHIES_B. This relationship ensures every intercompany transaction is associated with a valid, defined consolidation hierarchy, which dictates the rules and entity relationships for processing those transactions.
-
Table: GCS_INTERCO_ELM_TRX
12.1.1
owner:GCS, object_type:TABLE, fnd_design_data:GCS.GCS_INTERCO_ELM_TRX, object_name:GCS_INTERCO_ELM_TRX, status:VALID, product: GCS - Financial Consolidation Hub , description: Intercompany transactions table. , implementation_dba_data: GCS.GCS_INTERCO_ELM_TRX ,
-
Table: GCS_HIERARCHIES_B
12.1.1
owner:GCS, object_type:TABLE, fnd_design_data:GCS.GCS_HIERARCHIES_B, object_name:GCS_HIERARCHIES_B, status:VALID, product: GCS - Financial Consolidation Hub , description: GCS hierarchy header information , implementation_dba_data: GCS.GCS_HIERARCHIES_B ,