Search Results xtr_layout_template_line_pk

Overview

XTR_LAYOUT_TEMPLATE_LINE is a Treasury (XTR) module table that stores the individual line-level definitions belonging to a confirmation layout template. In Oracle E-Business Suite 12.1.1 and 12.2.2, the XTR product supports treasury deal confirmations, and the layout template framework governs how confirmation documents are formatted, which fields are printed, and in what order. This table is the child of XTR_LAYOUT_TEMPLATE and holds the ordered set of field instructions that make up a template layout.

Each record in XTR_LAYOUT_TEMPLATE_LINE represents one printable element within a named template: its source field, display title, formatting rules, and positional order. From a Data Vault modeling perspective, the mined heuristic classifies this object as satellite-leaning. This suggests that the table behaves as a descriptive attribute store whose grain is bound to a parent business key (TEMPLATE_NAME) plus a sequence (ORDER_NO), rather than acting as an independent hub or as a pure associative link resolving two separate hubs.

Key Information Stored

The table is owned by the XTR schema and contains 13 documented columns. The primary key, XTR_LAYOUT_TEMPLATE_LINE_PK, is a composite key defined on TEMPLATE_NAME and ORDER_NO. TEMPLATE_NAME is also the foreign key pointing back to XTR_LAYOUT_TEMPLATE, so it serves simultaneously as the parent reference and part of the child's business key. ORDER_NO supplies the ordinal position of the line within the template and completes the uniqueness constraint.

• TEMPLATE_NAME — Identifies the parent layout template; foreign key to XTR_LAYOUT_TEMPLATE and part of the primary key.
• ORDER_NO — Sequence number defining the line's position within the template; second component of the primary key.
• FIELD_NAME — The underlying data field or token that the line renders when the confirmation is produced.
• FIELD_TITLE — The display label or column heading shown to the recipient for that field.
• FIELD_TYPE — Classifies the field (for example, data, text, or grouping element) to drive rendering behavior.
• FIELD_FORMAT — Formatting mask or pattern applied to the field value during output.
• FIELD_SIZE — Width or length allocated to the field in the rendered layout.
• CODED_TEXT — Stored coded value used when the line represents a coded or enumerated element.
• USER_TEXT — Free-form user-entered text associated with the line.
• PREVIEW_TEXT — Sample or preview content shown when the template is being designed or reviewed.
• GRP_MARK — Flag indicating a grouping marker or break associated with the line.
• PRT_MARK — Print marker controlling whether or how the line is emitted on output.
• SUM_MARK — Marker denoting that the line participates in summation or totaling logic.

The composite key on TEMPLATE_NAME and ORDER_NO is the defining business-key candidate; no separate surrogate single-column identifier is documented.

Common Use Cases and Queries

Typical usage centers on retrieving, validating, and reporting the layout definition of a confirmation template. Common scenarios include auditing which fields appear on a given template, verifying print and summation flags before generating confirmations, and comparing line configurations across templates or environments.

• List all lines for a template in display order: SELECT ORDER_NO, FIELD_NAME, FIELD_TITLE, FIELD_TYPE FROM XTR_LAYOUT_TEMPLATE_LINE WHERE TEMPLATE_NAME = :p_template ORDER BY ORDER_NO;
• Identify printable versus suppressed lines using PRT_MARK for output verification.
• Detect summation columns via SUM_MARK for reconciliation reporting.
• Join to XTR_LAYOUT_TEMPLATE to obtain template-level headers alongside their lines.
• Compare templates by counting lines per TEMPLATE_NAME for change-impact analysis.

Related Objects

The most significant related object is the parent template table, joined on the shared key column.

• XTR_LAYOUT_TEMPLATE — Parent table; join on XTR_LAYOUT_TEMPLATE_LINE.TEMPLATE_NAME = XTR_LAYOUT_TEMPLATE.TEMPLATE_NAME. Supplies template header attributes.
• Confirmation and layout template setup forms and concurrent programs in the Treasury module consume these line definitions at generation time.
• Reporting views and BI Publisher layouts that render deal confirmations depend on the field, format, and order data held here.
• XTR_LAYOUT_TEMPLATE_LINE_PK enforces uniqueness and is referenced where downstream processes validate template integrity.