Search Results no_def_template_check




Overview
Explore in AI Chat

Overview

FND_CONC_TEMPLATES is an Oracle E-Business Suite internal PL/SQL package owned by APPS that provides concurrent processing utilities specifically for report templates and Oracle Publishing (OPP) processing. Its central responsibility is resolving which template definition, template file, language, and output format should be applied when a concurrent request produces formatted output through the Oracle Publishing engine. The package bridges the concurrent manager's request context — including program application, concurrent program name, and session NLS settings — to the physical template stored in the XML Publisher (XDO) repository tables. The package body header (AFCPTPLB.pls, version 120.5.12010000.4, dated 2009/01/30) indicates it is a long-lived, patched component of the FND concurrent processing layer. Within the context of a user search for nls_lang, the package is directly relevant because NLS_LANG and NLS_TERRITORY values are passed into its main entry point and are converted into ISO language and territory codes used to match localized templates — the default template code, short name, and language variables maintained as private state all participate in this resolution, and a dedicated get_iso_lang_and_terr call is invoked from within the main routine.

Key Procedures and Functions

  • GET_TEMPLATE_INFORMATION — The primary public entry point. It determines the complete template information needed for OPP processing, accepting NLS language and territory parameters (both current and session-level) and returning template name, template language, format, request language, ISO language, ISO territory, template application name, template code, and format type. It reads the FND_DEF_TEMPL_OUTPUT_TYPE profile option to allow a default output type override, and internally delegates to the ISO conversion and template fill routines. This is the procedure in which nls_lang and nls_terr appear as formal parameters.
  • FILL_NO_DEF_TEMPLATE — Handles the case where no default template is defined for the concurrent program, supplying fallback template information.
  • FILL_DEFAULT_TEMPLATE — Populates the output parameters from the default template configured for the program.
  • FILL_SPECIAL_DEF_TEMPLATE — Applies the special template case logic, using the private l_special_template_case variable to select an alternate template path.
  • FIND_THE_FORMAT — Locates the output format applicable to the resolved template.
  • GET_ISO_LANG_AND_TERR — Converts an NLS language and territory pair into ISO language and ISO territory codes, which are required for XDO template localization matching.
  • GET_DEF_ISO_TERR — Determines the default ISO territory when an explicit mapping is unavailable.
  • GET_TEMPLATE_INFO_OPTIONS — Retrieves template-related options, including profile-driven overrides.
  • DEF_TEMPLATE_CHECK — Validates whether a default template exists and is usable.
  • NO_DEF_TEMPLATE_CHECK — Validates the no-default-template condition.

Tables Accessed

  • FND_APPLICATION — Resolves application short names used as template application identifiers, consistent with the private variables typed on fnd_application.application_short_name%TYPE.
  • FND_CONCURRENT_PROGRAMS — Identifies the concurrent program whose template assignment is being resolved.
  • FND_LANGUAGES — Supports language and territory validation and mapping used in the ISO conversion routines.
  • XDO_TEMPLATES_B — The XML Publisher template definition table from which template code, name, and language are read.
  • XDO_LOBS — Stores the template file content (LOB) referenced during OPP processing.
  • ALL_TAB_COLUMNS / USER_TAB_COLUMNS — Used as documented by the private xdo_columns_cntr variable to detect whether the newer XDO columns exist, supporting backward compatibility across patch levels.
  • USER_SYNONYMS — Used for object availability and synonym resolution checks.

Usage Notes

FND_CONC_TEMPLATES is an internal API and is not intended for direct customer invocation. It is called by the Oracle Publishing / concurrent processing infrastructure when a request is submitted for a program that produces template-driven output. The package is referenced by one other documented package, reinforcing its role as a lower-level utility. Because template resolution depends on nls_lang and nls_territory, requests submitted under different NLS_LANG session settings may resolve to different localized templates; misconfigured or unsupported NLS_LANG values can therefore produce unexpected template selection or format results. Custom code should not call this package directly; rather, template behavior should be influenced through concurrent program template definitions and the FND_DEF_TEMPL_OUTPUT_TYPE profile option, which the package honors during resolution.