Results for “xtr_layout_values_v”

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

Overview

XTR_LAYOUT_VALUES_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Treasury (XTR) module. It exposes the metadata that drives Treasury's configurable layout and template framework — the definitions that determine, for each template type and subsection, which fields are displayed, their internal column mapping, formatting, and descriptive labels. In EBS 12.1.1 and 12.2.2 this view is registered as a valid database object and is available for querying, reporting, and integration, but it is not itself a data-entry object; it is a read-oriented projection of a single underlying table.

Underlying Base Objects

The view is defined over exactly one documented base object: XTR_LAYOUT_VALUES, referenced via a synonym. There are no joins, unions, or aggregation in the view body, which is a straight column projection:

SELECT TEMPLATE_TYPE, VIEW_SUBSECTION, FIELD_NAME, COL_VALUE, DESCRIPTION, LENGTH, FIELD_TYPE, FIELD_FORMAT FROM XTR_LAYOUT_VALUES

Because the mapping is one-to-one and non-restrictive, the view returns every row of the base table with no filtering or transformation applied. The "V" suffix is therefore a naming convention rather than a signal for re-aggregation, and row counts between the view and the base table remain identical.

Key Columns

• TEMPLATE_TYPE — the template classification that the layout row belongs to, grouping layout definitions by Treasury document or process type.
• VIEW_SUBSECTION — the logical subsection within a template where the field is rendered, allowing multiple fields to be grouped under a single template region.
• FIELD_NAME — the logical field identifier as presented in the layout definition.
• COL_VALUE — the internal column or value mapping associated with the field. This is the column most commonly targeted by direct searches (e.g., searches for "col_value"), because it links the display field back to a physical or logical data column. Users querying on col_value generally want to resolve a field name to its underlying column mapping, or vice versa.
• DESCRIPTION — the human-readable label or explanatory text for the field.
• LENGTH — the defined length of the field.
• FIELD_TYPE — the data type classification governing how the field is rendered and validated.
• FIELD_FORMAT — the display format applied to the value when presented in the layout.

Common Use Cases and Queries

The primary use case is metadata discovery: identifying which fields belong to a given template type or subsection, and resolving field-to-column mappings. This is typical during extensions, custom reports, and reconciliation of Treasury layouts after upgrades from 12.1.1 to 12.2.2.

To list all layout definitions for a template type:

SELECT template_type, view_subsection, field_name, col_value, description FROM apps.xtr_layout_values_v WHERE template_type = :p_template_type ORDER BY view_subsection, field_name;

To resolve a specific search on the internal column mapping:

SELECT template_type, view_subsection, field_name, col_value, field_type, field_format FROM apps.xtr_layout_values_v WHERE col_value = :p_col_value;

To find fields by description or restrict by type:

SELECT field_name, col_value, length, field_type FROM apps.xtr_layout_values_v WHERE description LIKE '%' || :p_label || '%' AND field_type = :p_type;

Because the view is non-restrictive, these predicates are applied at query time and every returned attribute can be traced directly to a base row in XTR_LAYOUT_VALUES. Joins to other Treasury metadata should be performed on template_type, view_subsection, and field_name where applicable.