Search Results report_sub




Overview
Explore in AI Chat

Overview

XTR_LAYOUT_TEMPLATE_V is a Treasury (XTR) module view owned by the APPS schema. It presents layout template definitions used by Oracle Treasury for structuring reports, letters, and related output documents. The view exposes configuration metadata that governs how Treasury documents are generated, including which report or report submission each template is associated with and whether the underlying report view currently exists. Because the view is a thin projection over the base table XTR_LAYOUT_TEMPLATE, it provides a stable, read-friendly interface for reporting, integration, and diagnostic queries without exposing the table directly to consumers. The object holds VALID status in the EBS 12.1.1 and 12.2.2 data dictionary, and its column list reflects the classic Treasury template model rather than any later multi-org or OAF-specific restructuring.

Underlying Base Objects

The view is defined over XTR_LAYOUT_TEMPLATE, accessed through a synonym in the APPS schema as documented in the ETRM metadata. The definition is a straightforward SELECT of the base table's columns with no joins, filters, or aggregations:

Because there is a one-to-one column mapping and no WHERE clause, row counts in the view match those of the base table, and all DML against templates must be performed on the base table. The view is therefore best understood as a naming and access convenience layer, historically used where a view-based responsibility or synonym was required by Treasury setup screens and concurrent program definitions.

Key Columns

  • TEMPLATE_NAME — the identifier of the layout template.
  • TEMPLATE_TYPE — classifies the template, distinguishing layout styles or document categories.
  • REPORT_TYPE — the category of report the template applies to.
  • ACTION_TYPE — the action (for example, printing or generation) the template supports.
  • CURRENT_TEMPLATE_YN — flags the template currently in effect for its combination of report and action.
  • DESCRIPTION — free-text description of the template.
  • WHO_CREATED / WHEN_CREATED — audit columns identifying the creating user and creation date.
  • REPORT_NAME — the report associated with the template.
  • REPORT_SUB — the report submission identifier, matching the "report_sub" search term; this links the template to the specific concurrent/registered report submission used to produce output.
  • VIEW_EXISTS_YN — indicates whether the referenced report view exists, useful for diagnosing broken template configurations.
  • CLIENT_LETTER / CLIENT_OR_CPARTY_LETTER — flags identifying templates used for client letters and client or counterparty letters respectively.

Common Use Cases and Queries

Typical uses include auditing which template is active for a given report, troubleshooting missing output caused by a template referring to a non-existent report view, and joining template metadata to concurrent program or report definitions for integration work. The following queries illustrate these scenarios.

  • List active templates and their report submissions:
    SELECT template_name, report_name, report_sub, action_type FROM xtr_layout_template_v WHERE current_template_yn = 'Y';
  • Find templates whose report view is missing:
    SELECT template_name, report_name, report_sub FROM xtr_layout_template_v WHERE view_exists_yn = 'N';
  • Identify letter templates:
    SELECT template_name, client_letter, client_or_cparty_letter FROM xtr_layout_template_v WHERE client_letter = 'Y' OR client_or_cparty_letter = 'Y';
  • Audit template creation:
    SELECT template_name, who_created, when_created FROM xtr_layout_template_v ORDER BY when_created DESC;

These queries support Treasury administrators in validating layout configuration and in tracing the report_sub value that ties each template to its generating report.