Search Results coded_text




Overview
Explore in AI Chat

Overview

The XTR_LAYOUT_TEMPLATE_LINE_V view is an Oracle E-Business Suite (EBS) database object owned by the APPS schema and registered under the XTR – Treasury product module. It is a simple projection view defined over the layout template line entity, exposing the individual line-level definitions that make up a treasury layout template. In EBS 12.1.1 and 12.2.2, treasury layouts drive the structured placement of fields on printed and exported documents such as deal confirmations, payment instructions, and bank communication files. The view therefore serves as the reporting and integration access point for the template line metadata that determines how each field is rendered, positioned, and calculated.

The object's status is VALID, and its documented description places it firmly within the XTR Treasury module's configuration and reporting layer. The view is read-oriented: it presents the line definitions that applications, concurrent programs, and custom reports consume when generating output, rather than a transactional store of treasury activity.

Underlying Base Objects

The view is defined over a single referenced base object, the synonym XTR_LAYOUT_TEMPLATE_LINE, which resolves to the underlying table of the same name in the APPS schema. The view text is a direct column projection:

Because no joins, filters, or aggregation are present, the view is a one-to-one row and column mapping of the base line table. This design preserves the base table's grain — one row per layout line per template — while providing a stable, documented interface that insulates consuming reports and integrations from direct dependency on the physical table. Each line is associated with its parent template through the TEMPLATE_NAME key, allowing the full set of lines for a given layout to be retrieved and sequenced.

Key Columns

  • TEMPLATE_NAME — Identifies the parent layout template to which the line belongs; the primary grouping key for all queries.
  • ORDER_NO — Determines the sequencing or positional order of the line within the template.
  • USER_TEXT — Literal, user-entered text printed on the output; used for static labels and headings.
  • CODED_TEXT — The coded or tokenized representation of line content, typically the value referenced programmatically during layout processing. This column is the object of interest for the "coded_text" search.
  • PREVIEW_TEXT — The display form of the line as shown during template preview, resolving coded content into readable form.
  • FIELD_NAME — The source data field bound to the line; links the layout definition to the underlying data element.
  • FIELD_TYPE — Classifies how the field is handled (for example, data versus text).
  • FIELD_SIZE and FIELD_FORMAT — Define the width and formatting applied when the field value is rendered.
  • FIELD_TITLE — The column heading or label associated with the field.
  • PRT_MARK, GRP_MARK, and SUM_MARK — Control flags indicating print inclusion, grouping behaviour, and summation behaviour respectively.

Common Use Cases and Queries

Typical usage focuses on inspecting and validating how a specific template is composed. A configuration analyst retrieving all lines for a template, in order, would issue:

  • SELECT template_name, order_no, field_name, field_title, coded_text, preview_text FROM xtr_layout_template_line_v WHERE template_name = :p_template_name ORDER BY order_no;

To audit which fields participate in grouping or summation, the flag columns are filtered directly:

  • SELECT template_name, order_no, field_name, grp_mark, sum_mark FROM xtr_layout_template_line_v WHERE grp_mark = 'Y' OR sum_mark = 'Y';

Because CODED_TEXT carries the programmatic token for each line, integration developers searching for a particular coded reference use it to locate templates that depend on a given field binding:

  • SELECT template_name, order_no, field_name, coded_text FROM xtr_layout_template_line_v WHERE coded_text LIKE '%' || :p_token || '%';

These queries support template documentation, impact analysis before modifying a layout, and reconciliation of preview output against coded definitions. The view's direct projection of the base table ensures predictable performance and consistent results across EBS 12.1.1 and 12.2.2.