Search Results xdo_templates_b




The XDO_TEMPLATES_B table is a critical component within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2, serving as the foundation for XML Publisher (XMLP) template management. XML Publisher is Oracle's enterprise reporting solution, enabling the creation of highly customizable, data-driven templates for generating outputs in formats such as PDF, Excel, HTML, and RTF. The XDO_TEMPLATES_B table stores metadata and binary content for these templates, ensuring seamless integration with Oracle EBS modules.

Structure and Key Columns

The XDO_TEMPLATES_B table is part of the XDO (XML Publisher) schema and contains the following key columns:
  • TEMPLATE_ID: Primary key, uniquely identifying each template.
  • APPLICATION_SHORT_NAME: Associates the template with a specific Oracle EBS application (e.g., GL, AP, AR).
  • TEMPLATE_CODE: A user-defined identifier for the template.
  • TEMPLATE_NAME: Descriptive name of the template.
  • TEMPLATE_TYPE: Specifies the format (e.g., RTF, PDF, XSL-FO).
  • DATA_SOURCE_CODE: Links to the data source definition in XDO_DATA_SOURCES.
  • FILE_NAME: Original filename of the uploaded template.
  • CONTENT_TYPE: MIME type of the template (e.g., application/rtf).
  • TEMPLATE_FILE: BLOB column storing the binary template content.
  • LAST_UPDATE_DATE and LAST_UPDATED_BY: Audit columns tracking modifications.

Functional Role in Oracle EBS

The XDO_TEMPLATES_B table acts as the repository for all XML Publisher templates used across Oracle EBS modules. These templates define the layout and formatting of reports, invoices, checks, and other documents. Key functionalities include:
  • Template Storage: Centralizes template binaries and metadata for efficient retrieval.
  • Version Control: Works with XDO_TEMPLATES_TL (translation table) to support multilingual templates.
  • Integration with Concurrent Processing: Templates are referenced by concurrent programs to generate outputs during batch runs.
  • Dynamic Data Binding: Associates templates with data sources (XDO_DATA_SOURCES) for runtime data merging.

Technical Considerations

  • Performance: BLOB storage of large templates may impact query performance; indexing on TEMPLATE_CODE and APPLICATION_SHORT_NAME is recommended.
  • Security: Access is controlled via Oracle EBS responsibilities and the FND_LOAD_UTIL framework.
  • Upgrades/Migrations: Template data must be preserved during EBS upgrades, often using FNDLOAD or XDO_LDR utilities.

Common Use Cases

  1. Financial Reporting: GL journal reports, FSG outputs.
  2. Payables/Receivables: Check printing, invoice formats.
  3. Multi-Org Support: Templates customized by operating unit.
  4. Regulatory Compliance: Tax forms, statutory reports.

Conclusion

The XDO_TEMPLATES_B table is indispensable for Oracle EBS reporting, providing a structured mechanism to manage template assets. Its integration with XML Publisher ensures flexibility in document design while maintaining alignment with EBS data models. Administrators should prioritize regular maintenance, such as purging obsolete templates and optimizing BLOB storage, to ensure system efficiency.

  • 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 , 

  • View: XDO_TEMPLATES_VL 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:XDO.XDO_TEMPLATES_VL,  object_name:XDO_TEMPLATES_VL,  status:VALID,  product: XDO - XML Publisher ,  description: XDO_TEMPLATES_VL is a view to join XDO_TEMPLATES_B and XDO_TEMPLATES_TL. ,  implementation_dba_data: APPS.XDO_TEMPLATES_VL , 

  • View: XDO_TEMPLATES_VL 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:XDO.XDO_TEMPLATES_VL,  object_name:XDO_TEMPLATES_VL,  status:VALID,  product: XDO - XML Publisher ,  description: XDO_TEMPLATES_VL is a view to join XDO_TEMPLATES_B and XDO_TEMPLATES_TL. ,  implementation_dba_data: APPS.XDO_TEMPLATES_VL , 

  • Table: XDO_TEMPLATES_TL 12.2.2

    owner:XDO,  object_type:TABLE,  fnd_design_data:XDO.XDO_TEMPLATES_TL,  object_name:XDO_TEMPLATES_TL,  status:VALID,  product: XDO - XML Publisher ,  description: XDO_TEMPLATES_TL is a translation table for XDO_TEMPLATES_B. ,  implementation_dba_data: XDO.XDO_TEMPLATES_TL , 

  • Table: XDO_TEMPLATES_TL 12.1.1

    owner:XDO,  object_type:TABLE,  fnd_design_data:XDO.XDO_TEMPLATES_TL,  object_name:XDO_TEMPLATES_TL,  status:VALID,  product: XDO - XML Publisher ,  description: XDO_TEMPLATES_TL is a translation table for XDO_TEMPLATES_B. ,  implementation_dba_data: XDO.XDO_TEMPLATES_TL , 

  • Lookup Type: XDO_USE_ALIAS_TABLE 12.1.1

    product: XDO - XML Publisher ,  meaning: Flags whether the template uses the alias table or not ,  description: This is for XDO_TEMPLATES_B table. If this value is Y, template should be processed with the alias table stored in XDO_TEMPLATE_FIELDS. , 

  • Lookup Type: XDO_USE_ALIAS_TABLE 12.2.2

    product: XDO - XML Publisher ,  meaning: Flags whether the template uses the alias table or not ,  description: This is for XDO_TEMPLATES_B table. If this value is Y, template should be processed with the alias table stored in XDO_TEMPLATE_FIELDS. ,