Search Results detail_code_combination_id

Overview

The GL_ACCOUNT_HIERARCHIES table is a core data structure within the Oracle E-Business Suite General Ledger (GL) module, specifically designed to manage summary and detail account relationships. Its primary role is to store the hierarchical mapping between summary (parent) and detail (child) natural accounts, which is fundamental for generating consolidated financial reports and performing account roll-ups. This table enables the system to aggregate detailed transaction-level balances into higher-level summary balances, a critical function for financial statement preparation and management reporting. The table's structure supports the definition of multiple, ledger-specific hierarchies, allowing for flexible reporting structures across different sets of books or ledgers within a single EBS instance.

Key Information Stored

The table's structure centers on defining the parent-child relationships between accounting flexfield combinations. Its primary and foreign key constraints, as documented in the ETRM, reveal the essential columns and their relationships. The composite primary key (GL_ACCOUNT_HIERARCHIES_PK) consists of SUMMARY_CODE_COMBINATION_ID and DETAIL_CODE_COMBINATION_ID, enforcing the uniqueness of each summary-to-detail link. Critical foreign key columns include LEDGER_ID (or SET_OF_BOOKS_ID in earlier versions), which ties the hierarchy to a specific ledger, and TEMPLATE_ID, which references GL_SUMMARY_TEMPLATES to identify the hierarchy structure. The two central columns, SUMMARY_CODE_COMBINATION_ID and DETAIL_CODE_COMBINATION_ID, are foreign keys to the GL_CODE_COMBINATIONS table, storing the identifiers for the parent and child account combinations, respectively.

Common Use Cases and Queries

The primary use case is the automated roll-up of account balances for financial reporting. When running reports like the Trial Balance or Income Statement, the system traverses these hierarchies to aggregate detail balances into summary totals. A common SQL pattern retrieves all detail accounts for a given summary account within a specific ledger:

• SELECT detail_ccid FROM gl_account_hierarchies WHERE summary_ccid = :p_summary_ccid AND ledger_id = :p_ledger_id;

Conversely, to find the parent summary account for a given detail line item:

• SELECT summary_ccid FROM gl_account_hierarchies WHERE detail_ccid = :p_detail_ccid AND ledger_id = :p_ledger_id;

These relationships are also leveraged during period-end closing processes and are essential for configuring custom financial reports in tools like Oracle Financial Statement Generator (FSG).

Related Objects

As indicated by its foreign key constraints, GL_ACCOUNT_HIERARCHIES has integral dependencies on several key GL tables. GL_CODE_COMBINATIONS is referenced twice, for both summary and detail accounts, forming the core of the relationship. GL_LEDGERS (or GL_SETS_OF_BOOKS) provides the organizational context. GL_SUMMARY_TEMPLATES stores the master definition of the hierarchy template. This table is primarily populated and maintained through the application's "Summary Accounts" form or related APIs, not via direct SQL manipulation. Key reporting views and application programming interfaces (APIs) within the GL module will internally query this table to resolve account aggregations.