Search Results gl_summary_hierarchies




Overview
Explore in AI Chat

Overview

The GL_SUMMARY_HIERARCHIES table is a core data structure within the Oracle E-Business Suite General Ledger (GL) module. It functions as the detailed mapping table that defines the roll-up relationships for summary account templates. Specifically, it stores the child segment value ranges that are consolidated into a single parent value within a summary template. This table is essential for the system's ability to perform high-level reporting and analysis by aggregating detailed transactional data into summarized balances, a fundamental requirement for financial consolidation and management reporting.

Key Information Stored

The table's primary purpose is to define the hierarchical mapping between a parent segment value and its child ranges. Its structure, as defined by its primary key, is designed to enforce uniqueness for these mappings. The critical columns include TEMPLATE_ID, which links to the parent summary template definition; SEGMENT_POS, indicating the specific accounting flexfield segment (e.g., Cost Center, Account) to which the hierarchy applies; FLEX_VALUE_SET_ID, identifying the value set for the segment; PARENT_FLEX_VALUE, the high-level value that receives the summarized totals; and CHILD_FLEX_VALUE_LOW and CHILD_FLEX_VALUE_HIGH, which define the inclusive range of detailed child values that roll up into the specified parent.

Common Use Cases and Queries

The primary use case is the creation and maintenance of summary account templates, which are then assigned to ledger sets to enable the creation of summary balances. Administrators and functional consultants interact with this data indirectly through the "Summary Accounts" form in the GL application. From a technical perspective, common queries involve validating template definitions or troubleshooting summary balance generation. A typical analytical query might join this table to GL_SUMMARY_TEMPLATES and value set tables to report on all defined roll-up hierarchies.

SELECT sht.template_name,
       gsh.segment_pos,
       gsh.parent_flex_value,
       gsh.child_flex_value_low,
       gsh.child_flex_value_high
FROM   gl_summary_hierarchies gsh,
       gl_summary_templates sht
WHERE  gsh.template_id = sht.template_id
AND    sht.template_name = '&TEMPLATE_NAME'
ORDER BY gsh.segment_pos, gsh.parent_flex_value;

Related Objects

GL_SUMMARY_HIERARCHIES has a direct and critical foreign key relationship with the GL_SUMMARY_TEMPLATES table. The TEMPLATE_ID column in GL_SUMMARY_HIERARCHIES references the TEMPLATE_ID primary key in GL_SUMMARY_TEMPLATES. This enforces that every hierarchy mapping must belong to a valid, existing summary template. The table is also intrinsically linked to the FND_FLEX_VALUE_SETS and related value tables through the FLEX_VALUE_SET_ID, though this is not a formally declared foreign key in the provided metadata. Processes that create summary balances, such as the "Create Summary Balances" concurrent program, rely heavily on the data within this table to perform the correct aggregations.