Search Results run_entity_id

Overview

The GCS_CONS_ENG_RUNS table is a core technical object within the Oracle E-Business Suite General Ledger Consolidation System (GCS) for releases 12.1.1 and 12.2.2. It serves as the master log or audit trail for individual consolidation engine execution runs. Each record represents a specific instance of a consolidation process for a given entity, hierarchy, and period. The table is critical for tracking the status, parameters, and results of consolidation activities, enabling users to monitor process history, identify the most recent runs, and manage data integrity through flags for locking and impact analysis. Its design supports the complex, multi-entity consolidation workflows central to financial reporting in global organizations.

Key Information Stored

The table's columns can be categorized into defining parameters, status tracking, and audit information. The primary key uniquely identifies a run through four columns: RUN_NAME, HIERARCHY_ID, RUN_ENTITY_ID, and PARENT_ENTITY_ID. RUN_ENTITY_ID is a crucial column that specifies the unique identifier of the consolidation entity for which the engine was executed. Other significant columns include CAL_PERIOD_ID and BALANCE_TYPE_CODE, which define the accounting period and balance type (e.g., actual, budget) for the run. Process state is managed via STATUS_CODE, PROCESS_METHOD, and the START_TIME and END_TIME timestamps. Data integrity controls are enforced through LOCKED_FLAG, IMPACTED_FLAG, and MOST_RECENT_FLAG. Standard EBS "Who" columns (CREATED_BY, CREATION_DATE, etc.) and an OBJECT_VERSION_NUMBER provide audit trails and concurrency control. The ITEM_KEY links to the underlying workflow process, while REQUEST_ID ties the run to a concurrent request.

Common Use Cases and Queries

A primary use case is auditing and monitoring consolidation history. A system administrator or financial controller might query for all runs for a specific entity to troubleshoot issues or verify process completion. The column RUN_ENTITY_ID is frequently used in WHERE clauses for such entity-specific analysis. Another common scenario is identifying the most recent successful consolidation data for reporting, using the MOST_RECENT_FLAG. Sample queries include:

• Finding all runs for a specific entity and hierarchy: SELECT run_name, status_code, start_time, end_time FROM gcs.gcs_cons_eng_runs WHERE run_entity_id = &entity_id AND hierarchy_id = &hierarchy_id ORDER BY creation_date DESC;
• Identifying the latest run for reporting: SELECT * FROM gcs.gcs_cons_eng_runs WHERE most_recent_flag = 'Y' AND run_entity_id = &entity_id AND balance_type_code = 'ACTUAL';
• Investigating failed or in-progress processes: SELECT run_name, run_entity_id, status_code, request_id FROM gcs.gcs_cons_eng_runs WHERE status_code NOT IN ('COMPLETE') AND start_time > SYSDATE - 7;

Related Objects

The GCS_CONS_ENG_RUNS table has defined relationships with other EBS objects through its primary and foreign keys. Its primary key constraint, GCS_CONS_ENG_RUNS_PK, ensures uniqueness across the combination of RUN_NAME, HIERARCHY_ID, RUN_ENTITY_ID, and PARENT_ENTITY_ID. Documented foreign key relationships indicate it references:

• FND_CONCURRENT_REQUESTS via the REQUEST_ID column. This links the consolidation engine run to the standard EBS concurrent request manager for job scheduling and logging.
• Other tables (represented by '%' in the metadata) via HIERARCHY_ID and ANALYSIS_CYCLE_ID. These likely point to master data tables such as GCS_CONS_HIERS for hierarchy definitions and GCS_ANALYSIS_CYCLES_B for planning cycles, though the specific referenced tables are not fully detailed in the provided excerpt.

The unique index GCS_CONS_ENG_RUNS_U1 enforces the primary key constraint on the APPS_TS_TX_IDX tablespace.