Search Results insert_html

Overview

APPS.JTF_DIAGNOSTIC_COREAPI is the central rendering and diagnostic utility package within the Oracle E-Business Suite diagnostic framework (Oracle Diagnostics / "Diagnostics" test scripts). Its principal business function is to provide a standardized, HTML-aware output API that diagnostic test scripts invoke to produce formatted results, while simultaneously exposing a set of reusable environment validation routines used to assert preconditions before a diagnostic or setup check is executed. In Oracle EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and is classified as an "OTHER" API, indicating it is not a public business-object API but an internal framework service intended to be called by other diagnostics and setup-validation packages. The Source excerpt confirms it is a PL/SQL package specification ($Header: jtfdiagcoreapi_s.pls, dated 2006) with declared global variables, collection types, and a large set of public procedures used across the diagnostics codebase. Because the package is referenced by 82 other packages, it effectively acts as the shared presentation and assertion layer for diagnostic output across all EBS modules.

Key Procedures and Functions

The documented procedures, all exposed in the package specification, fall into several functional groups. The output/rendering group includes LINE_OUT, INSERT_STYLE_SHEET, INSERT_HTML, BRPRINT, SECTIONPRINT, and the indentation helpers TAB0PRINT, TAB1PRINT, TAB2PRINT, and TAB3PRINT. INSERT_STYLE_SHEET — the object of the user's search — emits the cascading style sheet markup used to style the diagnostic HTML report; it is normally called once near the beginning of a report so that subsequent output procedures inherit consistent formatting. INSERT_HTML writes raw HTML fragments, while LINE_OUT writes a plain line of text.

A second group handles severity-tagged messaging: ERRORPRINT, WARNINGPRINT, ACTIONPRINT, ACTIONERRORPRINT, ACTIONWARNINGPRINT, and the corresponding link variants ACTIONERRORLINK and ACTIONWARNINGLINK. These produce color-coded or action-oriented entries, with the link procedures embedding hyperlinks or notes directly into the report.

A third group performs environment and configuration validation: CHECKFINPERIOD (verifies GL period status), CHECKKEYFLEXFIELD (validates key flexfield setup), CHECKPROFILE (validates a profile option value), and BEGIN_PRE (a setup/precondition helper). Collectively these support the "assert then report" pattern typical of diagnostic scripts.

Tables Accessed

The package reads from a broad set of FND and GL tables through APPS synonyms. FND_USER, FND_ORACLE_USERID, and FND_RESPONSIBILITY_TL support identification of the current user and responsibility context set by Set_Client (g_user_id, g_resp_id, g_appl_id, g_org_id). FND_APPLICATION_TL and FND_PRODUCT_GROUPS supply application and release information used by Show_Header to populate g_appl_version. FND_PROFILE_OPTIONS, FND_PROFILE_OPTIONS_TL, and FND_PROFILE_OPTION_VALUES support CHECKPROFILE. FND_ID_FLEXS, FND_FLEX_VALUE_SETS, FND_FLEX_VALUE_RULE_USAGES, FND_SEGMENT_ATTRIBUTE_TYPES, and FND_SEGMENT_ATTRIBUTE_VALUES support CHECKKEYFLEXFIELD and flexfield-related validation. GL_PERIOD_STATUSES and GL_PERIOD_TYPES support CHECKFINPERIOD.

Usage Notes

JTF_DIAGNOSTIC_COREAPI is not invoked directly by end users. It is called from diagnostic test scripts, setup-validation programs, and other PL/SQL packages that generate HTML diagnostic reports; the metadata notes it is referenced by 82 other packages. Typical invocation is from concurrent programs and internal diagnostic runners that first call Set_Client and Show_Header to populate global context, then INSERT_STYLE_SHEET to initialize report styling, followed by the various print, tab, and validation routines. Custom diagnostic extensions should follow the same pattern, calling INSERT_STYLE_SHEET exactly once per report and using the validation procedures to assert environment prerequisites before rendering results.