Search Results gcs_cons_eng_run_dtls_pk

Overview

The GCS_CONS_ENG_RUN_DTLS table is a core data repository within Oracle E-Business Suite's Financial Consolidation Hub (GCS) module. It functions as a detailed transaction log for individual consolidation processes. Each time a consolidation engine run is executed—such as for data collection, translation, elimination, or consolidation—this table stores granular, line-level information about the actions performed and the resulting financial data entries. Its primary role is to provide a complete, auditable trail that links high-level consolidation runs to the specific journal entries and adjustments generated in the general ledger, ensuring transparency and supporting reconciliation.

Key Information Stored

The table's structure is designed to track the lineage and outcome of each consolidation step. Its primary key, RUN_DETAIL_ID, uniquely identifies each detail record. The most critical columns are the foreign keys that establish relationships with other central GCS entities. These include RUN_ID (linking to the parent run header), ENTRY_ID (for the main resulting journal entry), and STAT_ENTRY_ID (for statistical journal entries). It also stores identifiers for pre-consolidation entries (PRE_PROP_ENTRY_ID, PRE_PROP_STAT_ENTRY_ID), the specific consolidation rule applied (RULE_ID), the consolidation relationship used (CONS_RELATIONSHIP_ID), and the financial category involved (CATEGORY_CODE). This design allows analysts to trace any consolidated journal entry back to its originating rule, relationship, and process run.

Common Use Cases and Queries

This table is essential for troubleshooting, audit reporting, and process analysis. A common use case is investigating the results of a specific consolidation run to verify all generated entries. A typical query would join to the entry headers table to retrieve journal details.

• Audit Trail for an Entry: SELECT gerh.run_name, gcerd.* FROM gcs_cons_eng_run_dtls gcerd JOIN gcs_cons_eng_run_hdrs gerh ON gcerd.run_id = gerh.run_id WHERE gcerd.entry_id = <ENTRY_ID>;
• Detail Report for a Run: SELECT category_code, rule_id, entry_id FROM gcs_cons_eng_run_dtls WHERE run_id = <RUN_ID> ORDER BY run_detail_id;
• Reconciliation: Analysts use this table to reconcile the count and sum of entries generated by a run against expectations, ensuring no data was lost during the consolidation process.

Related Objects

The GCS_CONS_ENG_RUN_DTLS table has defined foreign key relationships with several fundamental GCS tables, as documented in the ETRM. These relationships are central to its function:

• GCS_ENTRY_HEADERS: Linked via multiple columns (ENTRY_ID, STAT_ENTRY_ID, PRE_PROP_ENTRY_ID, PRE_PROP_STAT_ENTRY_ID). This is the most critical relationship, connecting the process detail to the actual journal entries created in the general ledger.
• GCS_CATEGORIES_B: Linked via CATEGORY_CODE. This ties the detail record to the financial category (e.g., revenue, expense) being consolidated.
• GCS_CONS_ENG_RUNS (implied): While not listed in the provided foreign keys, the RUN_ID column would typically join to a run header table (like GCS_CONS_ENG_RUN_HDRS) to connect details to the parent consolidation process.
• The table also references rules and relationships (RULE_ID, CONS_RELATIONSHIP_ID), likely linking to rule definition tables such as GCS_CONS_RULES_B.