Search Results jtf_diagnostic_coreapi




Overview
Explore in AI Chat

Overview

APPS.JTF_DIAGNOSTIC_COREAPI is a PL/SQL package body belonging to the Oracle E-Business Suite diagnostic framework, part of the CRM Foundation (JTF) product family. The package functions as the core rendering and validation engine for Oracle's built-in diagnostic test infrastructure. It is responsible for generating HTML-based diagnostic outputs, applying style sheets, emitting formatted status messages, and performing a range of environment and configuration checks against EBS setup data. The package holds a status of VALID in the APPS schema and is documented as an "OTHER" API classification within ETRM 12.2.2. It exposes 80 documented procedures and functions and is referenced by 82 other database objects, while itself depending on a broad set of both APPS and SYS-level objects, indicating a central, heavily reused role within the diagnostic subsystem.

Key Procedures and Functions

The documented program units fall into several functional groups:

  • Output rendering: LINE_OUT, INSERT_STYLE_SHEET, INSERT_HTML, SECTIONPRINT, TAB0PRINT, TAB1PRINT, TAB2PRINT, TAB3PRINT, and BRPRINT construct and format the HTML document emitted to the user, including style sheet injection, section headings, indentation levels (tab nesting), and line breaks.
  • Message emission: ACTIONPRINT, ACTIONERRORPRINT, ACTIONWARNINGPRINT, WARNINGPRINT, ERRORPRINT, ACTIONERRORLINK, and ACTIONWARNINGLINK produce status, error, and warning messages, with distinct variants for actionable links versus plain text output.
  • Validation and environment checks: CHECKFINPERIOD, CHECKKEYFLEXFIELD, and CHECKPROFILE verify open accounting periods, key flexfield configuration, and profile option values respectively.
  • Control flow: BEGIN_PRE, listed among the documented entries, manages initialization of the diagnostic run sequence.

These procedures are consumed by dependent diagnostic packages to standardize the look-and-feel and correctness of diagnostic test results.

Tables Accessed

The package reads extensively from APPS synonym-backed application tables to drive its checks. FND_PROFILE_OPTIONS, FND_PROFILE_OPTIONS_TL, FND_PROFILE_OPTIONS_VL, and FND_PROFILE_OPTION_VALUES support profile verification. FND_USER, FND_RESPONSIBILITY_TL, FND_APPLICATION_TL, and FND_APPLICATION_VL supply security and application context. Key flexfield validation draws on FND_ID_FLEXS, FND_FLEX_VALUE_SETS, FND_FLEX_VALUE_RULE_USAGES, FND_SEGMENT_ATTRIBUTE_TYPES, and FND_SEGMENT_ATTRIBUTE_VALUES. Financial period checks reference GL_PERIOD_STATUSES, GL_PERIOD_TYPES, and GL_SETS_OF_BOOKS. Additional dependencies include FND_ORACLE_USERID, FND_PRODUCT_GROUPS, HR_ALL_ORGANIZATION_UNITS, and FND_CLIENT_INFO. SYS-level dependencies include V$DATABASE, V$INSTANCE, V$PARAMETER, V$VERSION, DBMS_LOB, DBMS_SQL, UTL_SMTP, UTL_TCP, and NLS_SESSION_PARAMETERS.

Usage Notes

APPS.JTF_DIAGNOSTIC_COREAPI is invoked internally by dependent diagnostic packages (82 objects reference it) rather than being called directly by end users. It is typically reached through the Oracle Diagnostics / "Diagnostics" concurrent and form-driven framework, where a diagnostic test definition triggers the core API to render results into an HTML report. Custom diagnostic extensions that follow Oracle's JTF diagnostic conventions may call these procedures to maintain consistent formatting and to reuse the validation checks for flexfields, profiles, and financial periods. Because the package is not referenced by any database object according to the dependency data, it functions as a terminal implementation layer in the call chain. The presence of UTL_SMTP and UTL_TCP suggests optional email or socket delivery of diagnostic output. Compatibility applies to EBS 12.1.1 and 12.2.2.