Search Results use_alias_table




Overview
Explore in AI Chat

Overview

XDO_TEMPLATES_B is the principal XML Publisher (BI Publisher) metadata table in Oracle E-Business Suite, owned by the XDO schema. It stores the definition of every report template registered with the XML Publisher engine, including seeded templates shipped with Oracle applications and templates created by implementers through the Template Manager or the XML Publisher Administrator responsibility. In EBS 12.1.1 and 12.2.2 the table is validated and actively maintained by the XDO product, forming part of the core publishing infrastructure used by Concurrent Manager report submissions, Oracle Forms-based report invocation, and the OA Framework publisher integration.

Each row in XDO_TEMPLATES_B describes a template's business identity and its link to a data source definition held in XDO_DS_DEFINITIONS_B. Importantly, the base table holds the template header record, while the physical template file (RTF, XSL-FO, PDF, Excel, or eText output) is associated with each translation of the template rather than with the template itself. This distinction is central to understanding why multiple rows and companion translation tables exist for a single logical template.

From a Data Vault modeling perspective, the FK relationships (IRC_OFFERS and IRC_TEMPLATE_ASSOCIATIONS referencing TEMPLATE_ID) suggest a hub-leaning classification. This is a heuristic observation: XDO_TEMPLATES_B can reasonably be modelled as a hub, with descriptive attributes such as status, default language, and output type placed in a satellite.

Key Information Stored

The table contains 40 documented columns. The most significant include:

Three unique indexes supply business-key candidates. XDO_TEMPLATES_B_U1 covers APPLICATION_SHORT_NAME, TEMPLATE_CODE, and ZD_EDITION_NAME; U2 covers APPLICATION_ID, TEMPLATE_CODE, and ZD_EDITION_NAME; U3 covers TEMPLATE_ID and ZD_EDITION_NAME. These confirm that the application plus template code is the natural business key.

Common Use Cases and Queries

Typical reporting and administration scenarios include locating a template by code, identifying which templates belong to an application, and confirming that a template's data source is correctly linked. A common query pattern joins XDO_TEMPLATES_B to XDO_DS_DEFINITIONS_B on the data source code and application short name:

  • SELECT t.template_code, t.template_type_code, t.template_status FROM xdo_templates_b t WHERE t.application_short_name = :app AND t.template_status = 'ACTIVE';
  • Joining to XDO_DS_DEFINITIONS_B on DS_APP_SHORT_NAME = DATA_SOURCE_APPLICATION_SHORT_NAME and DATA_SOURCE_CODE to validate template-to-datasource coverage.
  • Querying IRC_OFFERS and IRC_TEMPLATE_ASSOCIATIONS by TEMPLATE_ID to find recruiting offers that consume a given template.
  • Auditing templates by LAST_UPDATE_DATE and LAST_UPDATED_BY for change-control reporting.
  • Excluding rows where ZD_EDITION_NAME is not the current edition when querying under Online Patching in 12.2.2.

Related Objects

XDO_TEMPLATES_B sits at the centre of a small but tightly coupled set of XML Publisher objects and dependent application tables:

  • XDO_DS_DEFINITIONS_B — holds the data source definitions referenced by each template.
  • IRC_OFFERS — references XDO_TEMPLATES_B.TEMPLATE_ID via IRC_OFFERS.TEMPLATE_ID.
  • IRC_TEMPLATE_ASSOCIATIONS — references XDO_TEMPLATES_B.TEMPLATE_ID via IRC_TEMPLATE_ASSOCIATIONS.TEMPLATE_ID.
  • XDO_TEMPLATES_TL — the translation table holding locale-specific template attributes and the physical template associations per translation.
  • XDO_LOBS — stores the physical template file content referenced through the translation records.
  • XDO_CONFIG_VALUES — configuration entries that govern publisher behaviour at runtime.

Together these objects form the metadata foundation for all XML Publisher output generated within Oracle EBS.