Results for “gl_summary_templates”

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

Overview

GL_SUMMARY_TEMPLATES, owned by the GL schema in Oracle E-Business Suite 12.1.1 and 12.2.2, is the General Ledger table that defines summary account templates. Summary accounts allow an installation to maintain derived balances at a level above individual detail code combinations, aggregating activity across specified ranges of chart-of-accounts segment values. Each row in GL_SUMMARY_TEMPLATES represents one such template and describes the structural rules that govern how the corresponding summary code combination is built and maintained.

The table is registered as VALID and forms a central configuration object within the Oracle General Ledger product. Because summary account templates are referenced repeatedly throughout the GL data model, this table sits at the nexus of account hierarchy definitions, balance storage, budget processing, and posting logic. Under the heuristic Data Vault classification supplied in the ETRM metadata, the table is described as hub-leaning: it behaves as a durable, identity-bearing reference entity (identified by TEMPLATE_ID) around which many dependent transactions and balances cluster, rather than as a purely descriptive satellite.

Key Information Stored

GL_SUMMARY_TEMPLATES contains 58 documented columns and is uniquely identified by the primary key constraint GL_SUMMARY_TEMPLATES_PK, with TEMPLATE_ID also serving as the business-key candidate enumerated through the unique index GL_SUMMARY_TEMPLATES_U1. The most significant columns include:

• TEMPLATE_ID — surrogate primary key and unique identifier for each summary template.
• TEMPLATE_NAME and CONCATENATED_DESCRIPTION — the user-facing name and the assembled description of the template.
• LEDGER_ID — foreign key to GL_SETS_OF_BOOKS_11I, identifying the ledger (set of books) to which the template belongs.
• STATUS — lifecycle state of the template, controlling whether it is active for maintenance.
• ACCOUNT_CATEGORY_CODE — the account category associated with the summarized balances.
• MAX_CODE_COMBINATION_ID — foreign key to GL_CODE_COMBINATIONS, referencing the furthest (highest) detail combination included in the summarization range.
• START_ACTUALS_PERIOD_NAME — the period from which actual balances begin to be summarized.
• AMOUNT_TYPE and DR_CR_CODE — control the amount semantics and debit/credit orientation of summarized balances.
• BOUNDARY_CODE and FUNDS_CHECK_LEVEL_CODE — boundaries and funds-check behavior applied to the template.
• FUNDING_BUDGET_VERSION_ID — foreign key to GL_BUDGET_VERSIONS, tying the template to a funding budget version.
• SEGMENT1_TYPE through SEGMENT30_TYPE — per-segment type indicators that describe how each chart-of-accounts segment participates in the summary rule.
• ATTRIBUTE1–ATTRIBUTE8 and CONTEXT — the standard descriptive flexfield and descriptive columns, along with audit columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical work with this table involves reviewing which summary templates exist for a ledger, auditing their segment definitions, or tracing how summary balances were produced. A common pattern joins the template to its ledger and to the code combination range it spans:

• Template inventory by ledger: select TEMPLATE_ID, TEMPLATE_NAME, ACCOUNT_CATEGORY_CODE, and STATUS from GL_SUMMARY_TEMPLATES where LEDGER_ID = :ledger_id, joined to GL_SETS_OF_BOOKS_11I for the ledger name.
• Segment analysis: inspecting SEGMENT1_TYPE through SEGMENT30_TYPE to confirm which segments are constrained versus aggregated for a given template.
• Balance tracing: joining GL_BALANCES.TEMPLATE_ID to GL_SUMMARY_TEMPLATES.TEMPLATE_ID to identify which summarized balances derive from a particular template.
• Hierarchy validation: joining GL_ACCOUNT_HIERARCHIES and GL_SUMMARY_HIERARCHIES on TEMPLATE_ID to reconcile the template against its account hierarchy.
• Budget and funds analysis: linking via FUNDING_BUDGET_VERSION_ID to GL_BUDGET_VERSIONS to assess funding budget coverage.

Reporting generally filters on STATUS to isolate active templates and on START_ACTUALS_PERIOD_NAME to align summarized actuals with the reporting period.

Related Objects

GL_SUMMARY_TEMPLATES is extensively referenced across the GL schema. The most significant dependents and related objects include:

• GL_BALANCES and GL_DAILY_BALANCES — store the summarized balances keyed by TEMPLATE_ID.
• GL_ARCHIVE_BALANCES and GL_ARCHIVE_DAILY_BALANCES — archival counterparts that retain historical summarized balances by template.
• GL_CODE_COMBINATIONS — both a referenced object (through MAX_CODE_COMBINATION_ID) and a dependent (through its own TEMPLATE_ID column), linking detail combinations to templates.
• GL_ACCOUNT_HIERARCHIES and GL_SUMMARY_HIERARCHIES — describe the hierarchical structure associated with each template.
• GL_SETS_OF_BOOKS_11I and GL_BUDGET_VERSIONS — referenced parents supplying ledger and funding budget version context.
• GL_DYNAMIC_SUMM_COMBINATIONS and GL_TEMPORARY_COMBINATIONS — combinations generated in support of summary processing.
• GL_POSTING_INTERIM, GL_BALANCES_DELTA, and GL_TRANSLATION_INTERIM — interim and delta structures that carry TEMPLATE_ID during posting, translation, and reconciliation.

Together these relationships establish GL_SUMMARY_TEMPLATES as the anchor for summarized accounting balances and their derived hierarchies within Oracle General Ledger.