Search Results xtr_layout_template_pk

Overview

XTR_LAYOUT_TEMPLATE is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores confirmation letter template information. Confirmation letters are generated by Treasury to communicate deal terms — such as foreign exchange, money market, or debt instrument confirmations — to counterparties and internal clients. Each row in XTR_LAYOUT_TEMPLATE defines a reusable layout definition that governs how a confirmation document is rendered, which Oracle Reports executable or report sub-component is invoked, and the conditions under which the template applies.

Because the table carries descriptive attributes about templates and is referenced by child line definitions, a Data Vault modeling heuristic classifies XTR_LAYOUT_TEMPLATE as satellite-leaning. In that interpretation, TEMPLATE_NAME would act as the natural business key of the parent construct, with descriptive and classification columns attached as satellite attributes, while the linkage to line-level detail is captured in the dependent table. This classification is a modeling suggestion rather than a physical constraint in the EBS schema.

Key Information Stored

The table is owned by the XTR schema and the documented physical schema for ETRM 12.2.2 lists 13 columns. The primary key constraint XTR_LAYOUT_TEMPLATE_PK is defined on TEMPLATE_NAME, and a unique index XTR_LAYOUT_TEMPLATE_U1 also exists on TEMPLATE_NAME, confirming it as the single business-key candidate. Because the primary key is the natural template name rather than a system-generated surrogate, joins are performed directly on the name.

• TEMPLATE_NAME — Primary key and business-key candidate; the unique identifier for a confirmation letter template.
• TEMPLATE_TYPE — Classifies the template and participates in a foreign key relationship to XTR_LAYOUT_WHERE_CLAUSE, which supplies selection or filtering criteria.
• REPORT_NAME — Identifies the Oracle Reports executable or report definition used to render the letter.
• REPORT_SUB — Specifies the report sub-component or section used within the parent report.
• REPORT_TYPE — Indicates the rendering or output category of the report.
• DESCRIPTION — Free-text description of the template's purpose.
• ACTION_TYPE — Indicates the document action or processing context associated with the template.
• CLIENT_LETTER — Flag denoting whether the template produces a client-facing letter.
• CLIENT_OR_CPARTY_LETTER — Flag distinguishing whether the template targets a client or a counterparty.
• CURRENT_TEMPLATE_YN — Indicates whether the template is the currently active or effective version.
• VIEW_EXISTS_YN — Indicates whether an associated database view exists for the template.
• WHO_CREATED and WHEN_CREATED — Standard audit columns capturing the creating user and creation timestamp.

Common Use Cases and Queries

The most frequent requirement is to retrieve the active template for a given confirmation scenario. A representative query identifies current templates by type:

SELECT template_name, report_name, report_sub, description FROM xtr_layout_template WHERE current_template_yn = 'Y' AND template_type = :p_type;

Letter-generation logic typically resolves the report executable and sub-section before invoking the concurrent report, so reporting queries commonly select REPORT_NAME, REPORT_SUB, and REPORT_TYPE together with TEMPLATE_NAME. Audit reporting uses WHO_CREATED and WHEN_CREATED to track template authorship over time. Because a single template may have many line definitions, analysts routinely aggregate child rows to count lines per template, joining XTR_LAYOUT_TEMPLATE_LINE on TEMPLATE_NAME. Selection-criteria analysis joins to XTR_LAYOUT_WHERE_CLAUSE via TEMPLATE_TYPE to review the filtering rules that determine when a template is applied.

Related Objects

• XTR_LAYOUT_TEMPLATE_LINE — Child table; its TEMPLATE_NAME foreign key references XTR_LAYOUT_TEMPLATE, holding the ordered line-level definitions for each template.
• XTR_LAYOUT_WHERE_CLAUSE — Referenced by the TEMPLATE_TYPE foreign key; stores the where-clause or selection criteria used to qualify template usage.
• Confirmation letter generation programs — Concurrent programs and Oracle Reports executables identified by REPORT_NAME and REPORT_SUB consume these template rows at run time.
• XTR_LAYOUT_TEMPLATE_PK / XTR_LAYOUT_TEMPLATE_U1 — Primary key constraint and unique index on TEMPLATE_NAME that enforce template-name uniqueness and support efficient lookups.
• XTR confirmation and deal tables — Treasury deal, counterparty, and confirmation records supply the transaction data merged into the letter defined by the template.