Results for “gl_summary_templates_v”

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

Overview

GL_SUMMARY_TEMPLATES_V is a concurrent-program and reporting view owned by the APPS schema in Oracle E-Business Suite General Ledger. It exposes the contents of the GL_SUMMARY_TEMPLATES base table joined to GL_LEDGERS, and is used to present summary account template definitions in a form that resolves the internal LEDGER_ID into a user-readable ledger name. Summary templates are the mechanism by which General Ledger creates summary (parent) accounts, aggregating balances from detail accounts along a chosen accounting flexfield hierarchy. The view therefore supports inquiry, reporting, and integration logic that must display or process template configuration without performing an explicit lookup against GL_LEDGERS.

The view is valid in both Oracle EBS 12.1.1 and 12.2.2. Its principal value is denormalization: the ledger name, the template definition, and the per-segment type flags are surfaced together, allowing consumers to identify how each of the up to thirty accounting flexfield segments participates in a template.

Underlying Base Objects

The view text defines a two-table join: GL_SUMMARY_TEMPLATES (aliased ST) as the driving table, and GL_LEDGERS (aliased LGR) joined on ST.LEDGER_ID = LGR.LEDGER_ID. The documented referenced base objects in ETRM 12.2.2 are GL_SUMMARY_TEMPLATES (synonym) and GL_LEDGERS (synonym). Because the join is an equi-join on LEDGER_ID, the view returns one row per summary template per owning ledger. ROW_ID is derived from the base table ROWID, supporting updatable-view behavior for tools that identify rows by ROWID. All audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are passed through from GL_SUMMARY_TEMPLATES, as are the descriptive flexfield columns ATTRIBUTE1 through ATTRIBUTE8 and the CONTEXT segment.

Key Columns

• TEMPLATE_ID / TEMPLATE_NAME — The primary identifier and user-assigned name of the summary template.
• LEDGER_ID / LEDGER_NAME — The ledger the template belongs to; LEDGER_NAME is resolved from GL_LEDGERS.
• SEGMENT1_TYPE through SEGMENT30_TYPE — Per-segment flags indicating how each accounting flexfield segment is treated within the template (for example, whether the segment is preserved as a detail selector or summarized). This is the column family most frequently searched, including the query "segment1_type".
• ACCOUNT_CATEGORY_CODE — Associates the template with an account category for reporting or allocation usage.
• START_ACTUALS_PERIOD_NAME — The period from which actual balances are accumulated for the summary template.
• STATUS — Lifecycle state of the template definition.
• CONCATENATED_DESCRIPTION / DESCRIPTION — Human-readable template text.
• MAX_CODE_COMBINATION_ID — Highest code combination identifier referenced by the template, useful for change-detection routines.
• ATTRIBUTE1–ATTRIBUTE8, CONTEXT — Descriptive flexfield content carried from the base table.

Common Use Cases and Queries

Typical consumers query the view to list templates for a ledger, to inspect which segments are summarized, and to drive custom reporting or validation. A representative query retrieving templates that reference SEGMENT1:

• SELECT template_name, ledger_name, segment1_type FROM apps.gl_summary_templates_v WHERE ledger_id = :p_ledger_id;
• SELECT template_id, template_name, ledger_name, status FROM apps.gl_summary_templates_v WHERE segment1_type IS NOT NULL ORDER BY template_name;

Because the view is a simple join over two base objects, it is suitable for read-only browsing and for joining to GL_CODE_COMBINATIONS or GL_BALANCES when reconciling summarized versus detail balances. Writes should generally be directed to GL_SUMMARY_TEMPLATES rather than to the view.