Search Results run_detail_id

Overview

The GCS_CONS_ENG_RUN_DTLS table is a core data repository within the Oracle General Ledger Consolidation System (GCS) for Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as the detailed transaction log for the consolidation engine, capturing the granular status and results of each child entity processed during a consolidation run. Each record represents a specific task or step for a single entity within a larger consolidation process, enabling detailed tracking, auditing, and error resolution. The table's primary role is to persist the execution context and outcome for every entity-level operation performed by the consolidation engine, linking the high-level run definition to the specific journal entries and adjustments generated.

Key Information Stored

The table stores a comprehensive set of identifiers that map the consolidation process flow. The primary key, RUN_DETAIL_ID, uniquely identifies each processing record. Essential process-defining columns include RUN_NAME (the user-specified consolidation process identifier), CONSOLIDATION_ENTITY_ID (the parent entity), and CHILD_ENTITY_ID. The table holds foreign keys to critical transactional objects: ENTRY_ID and STAT_ENTRY_ID link to the functional and statutory journal entry headers created, while PRE_PROP_ENTRY_ID and PRE_PROP_STAT_ENTRY_ID link to pre-proportional entries. Error handling is facilitated by REQUEST_ERROR_CODE and BP_REQUEST_ERROR_CODE. The CATEGORY_CODE defines the accounting category for the consolidation, and RULE_ID and CONS_RELATIONSHIP_ID define the specific consolidation rule and entity relationship applied. Standard WHO columns (CREATION_DATE, CREATED_BY, etc.) provide audit trails.

Common Use Cases and Queries

This table is central to troubleshooting and reporting on consolidation runs. A primary use case is diagnosing failed or errored consolidation processes by examining the error code columns for specific child entities. Analysts query this table to generate detailed run reports, listing all entities processed, their status, and the resulting journal entries. Common SQL patterns include joining to entity and category tables for descriptive reporting.

• Find all details for a specific consolidation run:
  SELECT * FROM GCS.GCS_CONS_ENG_RUN_DTLS WHERE RUN_NAME = '&RUN_NAME' ORDER BY CHILD_ENTITY_ID;
• Identify entities with errors in a run:
  SELECT RUN_NAME, CHILD_ENTITY_ID, REQUEST_ERROR_CODE, BP_REQUEST_ERROR_CODE FROM GCS.GCS_CONS_ENG_RUN_DTLS WHERE RUN_NAME = '&RUN_NAME' AND (REQUEST_ERROR_CODE IS NOT NULL OR BP_REQUEST_ERROR_CODE IS NOT NULL);
• List generated journal entries from a run:
  SELECT d.RUN_NAME, d.CHILD_ENTITY_ID, d.ENTRY_ID, h.JE_CATEGORY, h.JE_STATUS FROM GCS.GCS_CONS_ENG_RUN_DTLS d, GCS_ENTRY_HEADERS h WHERE d.ENTRY_ID = h.ENTRY_ID AND d.RUN_NAME = '&RUN_NAME';

Related Objects

The GCS_CONS_ENG_RUN_DTLS table has defined foreign key relationships with several key consolidation tables, primarily serving as a child table that references master data and transactional headers.

• GCS_ENTRY_HEADERS: This is the most referenced table. Foreign keys link RUN_DETAIL records to the journal entries they produce (ENTRY_ID, STAT_ENTRY_ID, PRE_PROP_ENTRY_ID, PRE_PROP_STAT_ENTRY_ID).
• GCS_CATEGORIES_B: The CATEGORY_CODE foreign key ensures the consolidation detail aligns with a valid accounting category.
• Primary Key Dependency: The unique index GCS_CONS_ENG_RUN_DTLS_U1 on RUN_DETAIL_ID enforces the primary key constraint GCS_CONS_ENG_RUN_DTLS_PK.
• Other References: The metadata indicates foreign keys to tables for RULE_ID and CONS_RELATIONSHIP_ID, which would link to consolidation rule and entity relationship definitions, respectively, though the specific target tables are not fully named in the excerpt.