Results for “psb_summary_templates”

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

Overview

The PSB_SUMMARY_TEMPLATES table is a core configuration object within the PSB – Public Sector Budgeting module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the definitions of summary templates that govern how budget data is aggregated, rolled up, and presented during the public sector budgeting cycle. A summary template defines a reusable, named structure that determines which budgeting dimensions and hierarchies are summarized when users view or report on budget worksheets, position budgets, and salary or non-salary expenditure lines.

The object resides in the PSB schema and is documented as VALID with a physical schema of nine columns. In the ETRM metadata the Data Vault classification is described as standalone, mined heuristically from foreign-key structure. Interpreted as a modeling suggestion, this indicates the table behaves as an independent reference or definition entity rather than a dependent transaction or association link: it carries stable template definitions that are referenced by other budgeting objects, with no upstream parent table required to give it meaning. It is best treated as a configuration-satellite or reference-hub pattern, keyed by the template identity and the ledger context.

Key Information Stored

The table holds template definition attributes. The most significant documented columns are:

• TEMPLATE_ID — Surrogate identifier for the summary template; part of the composite primary key PSB_SUMMARY_TEMPLATES_PK.
• SET_OF_BOOKS_ID — The ledger (set of books) to which the template belongs; the second component of the composite primary key. This scopes template definitions to a specific accounting ledger.
• TEMPLATE_NAME — The user-facing name of the summary template, used for selection and display.
• EFFECTIVE_START_DATE — The date from which the template definition becomes active, enabling dated versions of the same logical template.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing the most recent modification.
• CREATED_BY, CREATION_DATE — Standard EBS creation audit columns identifying the originating user and timestamp.

The surrogate primary key is the composite (TEMPLATE_ID, SET_OF_BOOKS_ID). A separate unique index, PSB_SUMMARY_TEMPLATES_U1, is defined on (SET_OF_BOOKS_ID, TEMPLATE_ID); this reordering of the same columns reinforces the ledger-first access path and effectively serves as the business-key candidate, ensuring a template identifier is unique within a given set of books.

Common Use Cases and Queries

Administrators and implementers use this table to inventory and validate which summary templates exist for each ledger before running budgeting processes. Typical reporting patterns include listing active templates for a set of books or auditing recently changed definitions.

• Template inventory by ledger: SELECT template_id, template_name, effective_start_date FROM psb.psb_summary_templates WHERE set_of_books_id = :ledger_id ORDER BY template_name;
• Effective-dated lookup: filter on effective_start_date <= SYSDATE to retrieve currently valid templates.
• Audit reporting: select last_updated_by, last_update_date to track configuration changes over time.
• Referential validation: confirm that downstream budgeting worksheets reference a template that exists for the same set of books.

Because the table is a definition/reference entity, queries are predominantly read-only joins and lookups rather than transactional inserts or updates, which normally occur only through the Public Sector Budgeting setup forms or the corresponding public APIs.

Related Objects

The metadata classifies this object as standalone, so foreign-key dependencies are minimal; relationships are driven through the composite key (TEMPLATE_ID, SET_OF_BOOKS_ID) rather than enforced constraints. Significant related objects include:

• PSB_SUMMARY_TEMPLATES_PK — primary-key constraint on (TEMPLATE_ID, SET_OF_BOOKS_ID).
• PSB_SUMMARY_TEMPLATES_U1 — unique index on (SET_OF_BOOKS_ID, TEMPLATE_ID), the business-key candidate.
• Downstream PSB budgeting worksheet and summary definition tables that consume templates via TEMPLATE_ID and SET_OF_BOOKS_ID.
• GL_SETS_OF_BOOKS — the ledger definition referenced through SET_OF_BOOKS_ID.
• Standard EBS audit and concurrency objects referencing LAST_UPDATED_BY and LAST_UPDATE_LOGIN (e.g., FND_USER).

Implementers should treat PSB_SUMMARY_TEMPLATES as the authoritative ledger-scoped registry of summary template definitions, validating both the template and ledger keys whenever joining to budgeting transaction or worksheet data.