Search Results start_actuals_period_name




Overview
Explore in AI Chat

Overview

APPS.GL_SUMMARY_TEMPLATES_NAMES_V is a reporting view in the Oracle E-Business Suite General Ledger module, exposed under the APPS schema. It presents summary template definitions maintained in Oracle General Ledger, providing a simplified projection of the GL_SUMMARY_TEMPLATES entity. Summary templates allow accountants to define account range and grouping rules used to produce summarized account balances for reporting, inquiry, and downstream consolidation purposes. The view exposes the identifying attributes of each template alongside its ledger assignment, status, concatenated description, account category, and the period from which actual balances begin to be summarized through the template.

Because the view is defined over GL_SUMMARY_TEMPLATES without joins or filters, it acts as a lightweight, read-only presentation layer. Its principal value lies in its narrower column list relative to the base table, which simplifies ad hoc queries, discoverer workbooks, concurrent program extracts, and integration interfaces that require only template-level metadata. The presence of the START_ACTUALS_PERIOD_NAME column is of particular interest to implementers, as this attribute governs the opening period from which actual balances are aggregated under the template definition.

Underlying Base Objects

The view is defined over a single base object, GL_SUMMARY_TEMPLATES, referenced in the ETRM metadata as a synonym. The defining query performs a straight projection of eight columns from the base table, aliased with the prefix ST. No WHERE clause, DISTINCT, aggregation, or outer join is present, so every row in GL_SUMMARY_TEMPLATES appears once in the view, and the view behaves as a one-to-one filtered projection of the underlying table.

GL_SUMMARY_TEMPLATES stores the definition of each summary template, including its rollup structure and the account ranges it applies. Because the view does not recurse into the summary template detail or range tables, consumers needing the child-level account assignments must query those related objects separately. The view therefore complements, rather than replaces, direct access to the base tables.

Key Columns

  • TEMPLATE_NAME — the user-defined name of the summary template, typically unique within a ledger and the principal search key for reporting.
  • TEMPLATE_ID — the internal primary key of the summary template, used to join to detail and range tables.
  • LEDGER_ID — the ledger to which the template belongs, linking template definitions to a specific accounting ledger.
  • STATUS — the current state of the template, controlling whether it is active and available for use.
  • CONCATENATED_DESCRIPTION — a composed description of the template, useful for display and reporting output.
  • ACCOUNT_CATEGORY_CODE — the account category (for example, assets or revenue) associated with the template.
  • MAX_CODE_COMBINATION_ID — the maximum code combination identifier referenced by the template, indicating the extent of its account range.
  • START_ACTUALS_PERIOD_NAME — the accounting period name from which actual balances are summarized; this is the most frequently searched attribute for this view.

Common Use Cases and Queries

Typical usages include identifying active templates for a ledger, determining when actuals summarization begins, and feeding template metadata into custom reports or interfaces. The following query lists all templates and their starting actuals period:

  • SELECT template_name, ledger_id, status, start_actuals_period_name FROM apps.gl_summary_templates_names_v ORDER BY template_name;
  • SELECT template_name, account_category_code, start_actuals_period_name FROM apps.gl_summary_templates_names_v WHERE ledger_id = :ledger_id AND status = 'A';
  • SELECT template_id, template_name FROM apps.gl_summary_templates_names_v WHERE start_actuals_period_name = :period_name;

Because the view is unrestricted, callers should always constrain by ledger or status in production environments to limit result sets and align with access controls applied at the reporting layer.