Search Results gcs_cons_eng_runs

Overview

The GCS_CONS_ENG_RUNS table is a core data object within the Oracle E-Business Suite Financial Consolidation Hub (GCS) module, specifically for versions 12.1.1 and 12.2.2. As explicitly noted in the ETRM documentation, this module is now marked as obsolete. The table serves as the primary header or control table for consolidation engine processes. It stores high-level metadata and status information for each execution of a financial consolidation, acting as a parent record to detailed run data. Its role is to uniquely identify and track a consolidation run, linking it to the specific consolidation hierarchy, entity, and concurrent request that initiated it.

Key Information Stored

The table's structure is defined by its primary key and foreign key relationships. The composite primary key (GCS_CONS_ENG_RUNS_PK) consists of RUN_NAME, HIERARCHY_ID, RUN_ENTITY_ID, and PARENT_ENTITY_ID, ensuring a unique identifier for each run within its specific consolidation context. Key columns include RUN_NAME, which identifies the process instance; HIERARCHY_ID, which references the consolidation hierarchy used; and RUN_ENTITY_ID and PARENT_ENTITY_ID, which define the entity being consolidated and its parent. Crucially, the REQUEST_ID column creates a foreign key relationship to FND_CONCURRENT_REQUESTS, linking the consolidation process to the E-Business Suite concurrent manager framework for job scheduling and logging. The ANALYSIS_CYCLE_ID column indicates a relationship to analysis cycle data.

Common Use Cases and Queries

This table is central to monitoring and auditing consolidation activities. Common operational queries involve joining with FND_CONCURRENT_REQUESTS to retrieve the status and log of a consolidation job, or listing all runs for a specific entity or hierarchy for historical analysis. A typical reporting query would select run details alongside concurrent request phase and status.

• Sample Query: To track the status of consolidation runs: SELECT g.run_name, g.hierarchy_id, f.request_id, f.phase_code, f.status_code FROM gcs_cons_eng_runs g, fnd_concurrent_requests f WHERE g.request_id = f.request_id ORDER BY f.request_date DESC;
• Use Case: Identifying failed consolidation processes by joining on REQUEST_ID and filtering for error statuses in FND_CONCURRENT_REQUESTS.
• Use Case: Analyzing run history for a specific entity (RUN_ENTITY_ID) to understand processing frequency and outcomes.

Related Objects

The GCS_CONS_ENG_RUNS table has defined foreign key relationships with several other EBS objects, as documented in the ETRM. These relationships are critical for data integrity and application logic.

• GCS_CONS_ENG_RUNS (Self-Referential): The table references itself via the HIERARCHY_ID column, suggesting a potential hierarchical relationship between different consolidation runs or configurations.
• FND_CONCURRENT_REQUESTS: Linked via GCS_CONS_ENG_RUNS.REQUEST_ID. This is the most critical operational relationship, connecting the consolidation engine to the standard EBS job execution and monitoring system.
• GCS_CONS_ENG_RUNS (Analysis Cycle): The table also references itself via the ANALYSIS_CYCLE_ID column, indicating a separate relationship for tracking analysis cycles within the consolidation framework.

Given the module's obsolete status, direct development on this table is unlikely, but it remains essential for supporting and reporting on existing implementations of the Financial Consolidation Hub.