Search Results xdo_templates_b_uk2
Overview
The XDO_TEMPLATES_B table is a core repository for XML Publisher (XDO) template metadata within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It stores the fundamental definition and administrative information for every report template registered in the system, including RTF, PDF, eText, and XSL-based layouts. This table does not store the physical template files themselves; instead, it maintains the logical template entity that links to a data source definition and to the physical template files for each language translation. Its primary role is to serve as the central reference point for template management, runtime processing, and integration with other EBS modules like iRecruitment (IRC).
Key Information Stored
The table's structure is designed to uniquely identify a template within and across applications. Key columns include APPLICATION_SHORT_NAME and TEMPLATE_CODE, which together form the primary key (XDO_TEMPLATES_B_PK) and represent the human-readable identifier. The APPLICATION_ID and TEMPLATE_CODE form a unique key (XDO_TEMPLATES_B_UK1) for application-level reference. The system-generated TEMPLATE_ID column (XDO_TEMPLATES_B_UK2) serves as the primary numeric identifier used for foreign key relationships. Other critical columns typically store the template name, description, output type (e.g., PDF, HTML), the associated data source code, and the default language code.
Common Use Cases and Queries
This table is central to diagnosing reporting issues, auditing template usage, and performing administrative overrides. Common scenarios include identifying all templates for a specific application, troubleshooting a missing template error, or finding templates linked to a particular data source. A typical diagnostic query would join with XDO_DS_DEFINITIONS_B to list templates and their data sources:
- SELECT xtb.template_code, xtb.template_name, xdd.data_source_code FROM xdo.xdo_templates_b xtb, xdo.xdo_ds_definitions_b xdd WHERE xtb.data_source_code = xdd.data_source_code AND xtb.application_short_name = 'PER';
Another common pattern is to retrieve the TEMPLATE_ID for use in related tables or APIs, based on the known application and template code.
Related Objects
XDO_TEMPLATES_B has integral relationships with several key XML Publisher objects. Each template must have a corresponding data source definition stored in XDO_DS_DEFINITIONS_B. Each language translation of a template links to a physical file stored in XDO_LOBS. As indicated by the foreign key metadata, this table is directly referenced by EBS modules; for example, the IRC_OFFERS and IRC_TEMPLATE_ASSOCIATIONS tables in iRecruitment use TEMPLATE_ID to link offer letters and associations to specific XML Publisher templates. The XDO_TEMPLATES_TL table stores the translated names and descriptions for the templates defined in this base table.
-
Table: XDO_TEMPLATES_B
12.1.1
owner:XDO, object_type:TABLE, fnd_design_data:XDO.XDO_TEMPLATES_B, object_name:XDO_TEMPLATES_B, status:VALID, product: XDO - XML Publisher , description: XDO_TEMPLATES_B is a table for template information. Each template has a corresponding data source definition stored in the XDO_DS_DEFINITIONS_B. Each translation of a certain template, not each template, has a correspoinding physical templ , implementation_dba_data: XDO.XDO_TEMPLATES_B ,
-
Table: XDO_TEMPLATES_B
12.2.2
owner:XDO, object_type:TABLE, fnd_design_data:XDO.XDO_TEMPLATES_B, object_name:XDO_TEMPLATES_B, status:VALID, product: XDO - XML Publisher , description: XDO_TEMPLATES_B is a table for template information. Each template has a corresponding data source definition stored in the XDO_DS_DEFINITIONS_B. Each translation of a certain template, not each template, has a correspoinding physical templ , implementation_dba_data: XDO.XDO_TEMPLATES_B ,