Search Results default_language

Overview

XDO_TEMPLATES_VL is a multilingual (MLS) view owned by the APPS schema in Oracle E-Business Suite, belonging to the XDO (XML Publisher / BI Publisher) product family. It presents the translated view of XML Publisher template definitions by joining the base table XDO_TEMPLATES_B, which stores language-independent template attributes, with XDO_TEMPLATES_TL, which stores the language-specific translations of template name and description. The view returns one row per template per language, filtered to the session language through USERENV('LANG'), so callers receive the template text in the language appropriate to their runtime environment.

Because template definitions drive the report and document generation stack in EBS 12.1.1 and 12.2.2, XDO_TEMPLATES_VL is the canonical reporting surface for XML Publisher metadata. It is the standard access point for concurrent programs, extension logic, and custom reporting that must resolve the human-readable name of a template, its data source, its type, and — critically, for the user's search term — its DEPENDENCY_FLAG.

Underlying Base Objects

The view is documented as being defined over two synonyms: XDO_TEMPLATES_B and XDO_TEMPLATES_TL.

• XDO_TEMPLATES_B — the base table holding the language-independent, transactional/definitional attributes of each template: identifier, owning application, template code, data source binding, template type, status, date range, output type, dependency flag, and the standard WHO columns plus descriptive flexfield attributes.
• XDO_TEMPLATES_TL — the translation table supplying TEMPLATE_NAME and DESCRIPTION per language, joined on APPLICATION_SHORT_NAME, TEMPLATE_CODE, and LANGUAGE.

The join condition is a natural-key match on APPLICATION_SHORT_NAME and TEMPLATE_CODE rather than on the surrogate TEMPLATE_ID, and it is restricted to the current session language via TL.LANGUAGE = USERENV('LANG'). This is a standard MLS pattern in EBS; the "_VL" suffix denotes that the view is the "view of the language" appropriate for the session.

Key Columns

• TEMPLATE_ID — surrogate identifier from the base table; the primary reference key for a template.
• APPLICATION_SHORT_NAME / APPLICATION_ID — the owning EBS application of the template.
• TEMPLATE_CODE — the internal, language-independent code identifying the template within its application.
• TEMPLATE_NAME / DESCRIPTION — translated text sourced from XDO_TEMPLATES_TL.
• DATA_SOURCE_CODE / DS_APP_SHORT_NAME — the data source definition the template consumes and the application that owns it.
• TEMPLATE_TYPE_CODE — the template technology type (for example RTF, PDF, XSL-FO, or Excel).
• DEFAULT_OUTPUT_TYPE / DEFAULT_LANGUAGE / DEFAULT_TERRITORY / MLS_LANGUAGE / MLS_TERRITORY — output and locale defaults.
• TEMPLATE_STATUS / START_DATE / END_DATE — lifecycle state and effective dating; END_DATE null typically denotes the currently active version.
• USE_ALIAS_TABLE / DEPENDENCY_FLAG — DEPENDENCY_FLAG indicates whether the template has dependencies (for example, associated sub-templates, subtemplates, or other linked artifacts) that affect how it may be modified, deleted, or regenerated. It is a primary filter when determining whether a template can be safely maintained.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the XML Publisher forms and APIs.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield segments for customer extensions.

Common Use Cases and Queries

Typical uses include listing available templates for an application, resolving translated names for multi-language deployments, filtering by DEPENDENCY_FLAG before maintenance, and auditing active-versus-retired templates.

List active templates for an application, exposing the dependency flag:

• SELECT template_code, template_name, template_type_code, dependency_flag, start_date, end_date FROM xdo_templates_vl WHERE application_short_name = 'XXCUSTOM' AND NVL(end_date, SYSDATE+1) > SYSDATE;

Find templates flagged as carrying dependencies:

• SELECT application_short_name, template_code, template_name, dependency_flag FROM xdo_templates_vl WHERE dependency_flag = 'Y' ORDER BY application_short_name, template_code;

Locate templates bound to a specific data source:

• SELECT template_code, template_name, data_source_code, default_output_type FROM xdo_templates_vl WHERE ds_app_short_name = 'XDO' AND data_source_code = '<DS_CODE>';

Because the view enforces session-language filtering, queries executed from a session whose language lacks a matching XDO_TEMPLATES_TL row return no template text; join strategies against XDO_TEMPLATES_B directly are preferable where all-language coverage is required. Consistent with EBS practice, this view should be treated as read-only and all maintenance performed through the supported XML Publisher APIs or forms.