Search Results get_template_information




Overview
Explore in AI Chat

Overview

FND_CONC_TEMPLATES is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides concurrent processing utilities for output post-processing (OPP) templates. Its principal business function is to resolve, at request submission and runtime, which XML Publisher (BI Publisher) template should be applied to the output of a concurrent program, and to return the associated template metadata — template application, template code, template file name, language and territory information, and output format — to the concurrent manager infrastructure that performs post-processing.

The package addresses the fact that a concurrent program defined in FND_CONCURRENT_PROGRAMS may or may not have a default template assigned. When a default template exists, the package returns its details directly; when no default is set, the package must derive an appropriate template using language, territory, and formatting rules. The header comment documents the package purpose simply as "Concurrent processing utilities for Templates and OPP," and the source carries a version identifier associated with the 12.1.1 and 12.2.2 code lines. The classification of the package as an OTHER API indicates that it is an internal support package rather than a formally published, customer-callable interface, although its procedures are public within the package specification.

Key Procedures and Functions

  • GET_TEMPLATE_INFORMATION — Retrieves the XML template details required for OPP, accepting program application and name, concurrent program name, and NLS language and territory values, and returning template-obtained status, template name, template language, format, request language, ISO language and territory, template application name, template code, and format type.
  • FILL_NO_DEF_TEMPLATE — Obtains template information for concurrent programs that do not have a default template defined in FND_CONCURRENT_PROGRAMS.
  • FILL_DEFAULT_TEMPLATE — Populates template information when a default template is defined for the concurrent program.
  • FILL_SPECIAL_DEF_TEMPLATE — Handles special-case default template resolution, addressing scenarios not covered by the standard default template path.
  • FIND_THE_FORMAT — Determines the output format associated with the resolved template.
  • GET_ISO_LANG_AND_TERR — Derives the ISO language and ISO territory codes used in template selection and language matching.
  • GET_DEF_ISO_TERR — Returns the default ISO territory when an explicit territory is not supplied.
  • GET_TEMPLATE_INFO_OPTIONS — Retrieves template information options governing how template selection should proceed.
  • DEF_TEMPLATE_CHECK — Validates whether a default template condition is satisfied for the program.
  • NO_DEF_TEMPLATE_CHECK — Validates the no-default-template condition, confirming that fallback resolution logic must be applied.

Tables Accessed

  • FND_CONCURRENT_PROGRAMS — The primary source of concurrent program definitions and their assigned default templates.
  • FND_APPLICATION — Resolves application identifiers and names for the program and template application.
  • FND_LANGUAGES — Supplies installed language and territory information used for NLS-aware template matching.
  • XDO_TEMPLATES_B and XDO_LOBS — The XML Publisher template definition and LOB tables from which template names, codes, and file content are resolved.
  • ALL_TAB_COLUMNS, USER_TAB_COLUMNS, and USER_SYNONYMS — Data dictionary views used for metadata and synonym resolution checks.

Usage Notes

FND_CONC_TEMPLATES is invoked by the concurrent processing and OPP runtime rather than by end users directly. It is called when a concurrent request is submitted with a template-based layout, when the output post-processor must determine the correct template for a completed request, and when a program has no explicitly assigned default template and fallback resolution by language and territory is required. Because the package is classified as OTHER and is referenced by only one other package, it should be treated as an internal dependency of the concurrent manager and XML Publisher integration. Custom code should not call these procedures directly; instead, custom concurrent programs should assign templates through the standard concurrent program definition screens so that the documented resolution paths are exercised normally.