Search Results rg_dss_var_templates




Overview
Explore in AI Chat

Overview

RG_DSS_VAR_TEMPLATES is a table owned by the RG schema (Application Report Generator product) in Oracle EBS 12.1.1 and 12.2.2. Its documented ETRM description identifies it as storing "Financial Analyzer financial data item summary templates." The table serves as the binding mechanism between a Financial Analyzer variable definition and a General Ledger summary template, effectively recording the segment-level composition that each variable should use when the summary template is applied.

Note that the RG schema is a legacy, tightly-scoped reporting schema associated with Financial Analyzer and Application Report Generator functionality, not a core transactional module. Access to these objects is typically restricted to reporting internals rather than end-user configuration screens.

From a heuristic Data Vault modeling perspective (mined from the FK structure), this table is best classified as a link table. Its composite primary key of (VARIABLE_ID, TEMPLATE_ID) and its two outbound foreign keys to RG_DSS_VARIABLES and GL_SUMMARY_TEMPLATES position it between two independent entities, which is characteristic of a link rather than a hub or satellite.

Key Information Stored

The table contains 53 documented columns. The most significant are:

  • VARIABLE_ID — Part of the composite primary key and a foreign key to RG_DSS_VARIABLES. Identifies the Financial Analyzer variable to which the template association applies.
  • TEMPLATE_ID — Part of the composite primary key and a foreign key to GL_SUMMARY_TEMPLATES. Identifies the GL summary template linked to the variable.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS Who columns capturing audit and row-level ownership metadata for insert and update activity.
  • SEGMENT1_TYPE through SEGMENT30_TYPE — A repeating family of columns specifying the segment type configuration for each of the up to thirty account segments associated with the variable/template combination. These columns drive how account segments are interpreted when the summary template is applied to the Financial Analyzer variable.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) columns, providing extensible storage for installation-specific data without schema changes.

The surrogate primary key is RG_DSS_VAR_TEMPLATES_PK, defined on (VARIABLE_ID, TEMPLATE_ID). The business-key candidate is the same pair, as it represents the natural unique combination of variable and template.

Common Use Cases and Queries

Typical usage centers on reporting diagnostics, migration validation, and reconciliation between Financial Analyzer variables and GL summary templates. A common pattern lists all templates assigned to a given variable:

  • SELECT VARIABLE_ID, TEMPLATE_ID, SEGMENT1_TYPE, SEGMENT2_TYPE, CREATION_DATE FROM RG_DSS_VAR_TEMPLATES WHERE VARIABLE_ID = :variable_id;
  • Joining to resolve template names: SELECT t.VARIABLE_ID, g.TEMPLATE_NAME FROM RG_DSS_VAR_TEMPLATES t, GL_SUMMARY_TEMPLATES g WHERE t.TEMPLATE_ID = g.TEMPLATE_ID;
  • Detecting orphaned associations, i.e., records whose VARIABLE_ID no longer exists in RG_DSS_VARIABLES.
  • Auditing recently created or modified associations using CREATED_BY and LAST_UPDATE_DATE.
  • Extracting DFF values from CONTEXT and ATTRIBUTE1..15 for custom reporting.

Because the table is not exposed through standard concurrent programs in all environments, direct SQL access via a read-only reporting user is the most common query route.

Related Objects

The most significant related objects, based on the documented FK relationships and composite key structure, are:

  • RG_DSS_VARIABLES — Parent of the VARIABLE_ID foreign key; holds the Financial Analyzer variable definitions referenced here.
  • GL_SUMMARY_TEMPLATES — Parent of the TEMPLATE_ID foreign key; holds the General Ledger summary template definitions.

Additional objects in the RG schema and the GL reporting family may reference these entities, but the two tables above represent the authoritative, documented dependencies for RG_DSS_VAR_TEMPLATES. Its link-table role means any change to a parent variable or template can invalidate associations defined here, so referential integrity checks should accompany any data movement or migration.