Results for “field_name”

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

Overview

The XTR_LAYOUT_VALUES table resides in the XTR schema, the database account that supports the Oracle Treasury (ETRM) module within Oracle E-Business Suite 12.1.1 and 12.2.2. Oracle documents the object as holding the common variables for confirmation templates. Confirmation templates in Treasury generate the printed and electronic deal confirmations exchanged with counterparties; the layout values defined in this table supply the reusable field definitions, formatting rules, and static values consumed when those templates render a confirmation document.

In Data Vault modeling terms, the FK structure suggests a satellite-leaning classification: the table hangs directly off a parent keyed by TEMPLATE_TYPE and therefore behaves like a descriptive, attribute-bearing child of a template master rather than an independent hub or an associative link. Treat this as a modeling suggestion for lineage and integration design, not as an Oracle-imposed constraint.

Key Information Stored

The table carries nine documented columns. The most significant are:

• TEMPLATE_TYPE — identifies the confirmation template to which a layout value belongs; part of the composite primary key and the FK to XTR_LAYOUT_WHERE_CLAUSE.
• FIELD_NAME — the name of the template variable or field; the second component of the primary key.
• COL_VALUE — the value assigned to the field when the template is rendered.
• DESCRIPTION — the descriptive label for the field, and a component of the second unique index.
• FIELD_TYPE — the data type category governing how the field is interpreted.
• FIELD_FORMAT — the display format mask applied to the field value.
• LENGTH — the length or width specification of the field.
• VIEW_SUBSECTION — groups layout values into a subsection of the rendered confirmation view.
• ZD_EDITION_NAME — the editioning column, present on this and all Oracle 12.2 edition-based redefinition objects; it appears in both unique indexes.

The surrogate primary key is XTR_LAYOUT_VALUES_PK, defined over TEMPLATE_TYPE and FIELD_NAME. The documented business-key candidates are XTR_LAYOUT_VALUES_U1 (TEMPLATE_TYPE, FIELD_NAME, ZD_EDITION_NAME) and XTR_LAYOUT_VALUES_U2 (TEMPLATE_TYPE, DESCRIPTION, ZD_EDITION_NAME); the inclusion of ZD_EDITION_NAME enables multiple coexisting editions of the same template layout during an upgrade or redefinition cycle.

Common Use Cases and Queries

Typical scenarios include auditing which variables a given confirmation template exposes, verifying formatting consistency across templates, and extracting the layout definition to reconcile it with the corresponding Oracle BI Publisher or Oracle Reports template file. A basic retrieval for one template is:

• SELECT field_name, col_value, field_type, field_format, length, description FROM xtr_layout_values WHERE template_type = :p_template_type ORDER BY view_subsection, field_name;
• SELECT DISTINCT template_type, view_subsection FROM xtr_layout_values ORDER BY template_type, view_subsection; — to enumerate template/section structure.
• SELECT lv.field_name, lv.col_value FROM xtr_layout_values lv JOIN xtr_layout_where_clause lw ON lw.template_type = lv.template_type WHERE lv.template_type = :p_type; — to correlate layout values with the template's selection criteria.

Because XTR is a Treasury-specific schema, these queries are most often run for troubleshooting confirmation output mismatches, validating a template after patching, or feeding a control report that compares configured field formats against corporate standards.

Related Objects

The FK relationship documented above anchors this table to the template definition hierarchy. Significant related objects include:

• XTR_LAYOUT_WHERE_CLAUSE — referenced via XTR_LAYOUT_VALUES.TEMPLATE_TYPE; supplies the WHERE-clause filter that selects the Treasury deals or transactions a confirmation template will process.
• XTR_CONFIRMATION_TEMPLATES (confirmation template master) — the conceptual parent providing TEMPLATE_TYPE values consumed by this table.
• XTR_CONFIRMATION_* audit/queue structures — the confirmation generation and delivery objects that read layout values at runtime.
• XTR_LAYOUT_VALUES indexes — XTR_LAYOUT_VALUES_PK, XTR_LAYOUT_VALUES_U1, and XTR_LAYOUT_VALUES_U2, which govern access paths and enforce the business keys.

Any customization that inserts or alters rows should preserve the TEMPLATE_TYPE/FIELD_NAME uniqueness and populate ZD_EDITION_NAME consistently with the active edition in 12.2 environments.