Results for “gl_summary_hierarchies”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_SUMMARY_HIERARCHIES is a General Ledger table in the Oracle EBS 12.1.1 and 12.2.2 schemas (owner: GL) that stores the child segment value ranges belonging to a summary template. Summary templates support the definition of hierarchical summarization rules in General Ledger, letting users roll detail account balances up to a parent account for reporting and inquiry purposes. Each row in GL_SUMMARY_HIERARCHIES defines one parent segment value together with the contiguous low and high child value range that maps into that parent, for a specified segment position within a template.

From a data-modeling perspective, the metadata classifies this object as satellite-leaning. This is a heuristic suggestion rather than a normative designation: the table behaves as a dependent child of its parent template, carrying descriptive and range-defining attributes that describe how detail values roll up. Analysts modeling GL summarization data may therefore treat GL_SUMMARY_TEMPLATES as the hub-like anchor and GL_SUMMARY_HIERARCHIES as the satellite holding the value-range detail. The table is marked VALID with 12 documented columns.

Key Information Stored

The documented columns capture the summarization rule and standard audit metadata:

• TEMPLATE_ID — Foreign key to GL_SUMMARY_TEMPLATES; identifies the summary template to which the range belongs.
• SEGMENT_POS — Position of the accounting flexfield segment for which the hierarchy range is defined.
• FLEX_VALUE_SET_ID — The value set from which parent and child segment values are drawn.
• PARENT_FLEX_VALUE — The parent (summary) segment value that receives the summarized detail.
• CHILD_FLEX_VALUE_LOW / CHILD_FLEX_VALUE_HIGH — The low and high bounds of the child value range mapped to the parent.
• STATUS_CODE — Status flag for the hierarchy record.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns.

The primary key is GL_SUMMARY_HIERARCHIES_PK, composed of TEMPLATE_ID, SEGMENT_POS, FLEX_VALUE_SET_ID, PARENT_FLEX_VALUE, CHILD_FLEX_VALUE_LOW, and CHILD_FLEX_VALUE_HIGH. A unique index, GL_SUMMARY_HIERARCHIES_U1, is defined over the same six-column business key, so the fact that no separate surrogate key column is documented means the business key and the physical primary key coincide. Uniqueness is enforced across the template, segment, value set, and range boundaries.

Common Use Cases and Queries

Typical scenarios include auditing which detail values roll up to a given parent, validating range coverage for a summary template, and generating reports of summarization rules. Common patterns include filtering all rows for a template with WHERE TEMPLATE_ID = :template_id, joining to GL_SUMMARY_TEMPLATES on TEMPLATE_ID to resolve template names, and resolving flex value descriptions via FLEX_VALUE_SET_ID, PARENT_FLEX_VALUE, and the child range columns against FND_FLEX_VALUES. Range overlap checks compare CHILD_FLEX_VALUE_LOW and CHILD_FLEX_VALUE_HIGH across rows sharing the same TEMPLATE_ID and SEGMENT_POS to detect conflicting definitions.

SELECT h.template_id, h.segment_pos, h.parent_flex_value,
       h.child_flex_value_low, h.child_flex_value_high
FROM   gl.gl_summary_hierarchies h
WHERE  h.template_id = :template_id
ORDER  BY h.segment_pos, h.parent_flex_value;

Related Objects

The principal related objects, based on the documented foreign key and business-key relationships, are:

• GL_SUMMARY_TEMPLATES — Parent table; joined on GL_SUMMARY_HIERARCHIES.TEMPLATE_ID = GL_SUMMARY_TEMPLATES.TEMPLATE_ID.
• FND_FLEX_VALUES — Supplies parent and child segment value descriptions, keyed by FLEX_VALUE_SET_ID and the value columns.
• FND_FLEX_VALUE_SETS — Defines the value set referenced by FLEX_VALUE_SET_ID.
• GL_SUMMARY_HIERARCHIES_PK / GL_SUMMARY_HIERARCHIES_U1 — Primary key constraint and unique index enforcing the six-column business key.

Because the table participates primarily as a dependent of GL_SUMMARY_TEMPLATES, reporting and integration efforts typically join outward to that parent and to the flexfield value-set tables to present human-readable summarization hierarchies.