Search Results csk_diag_solution_pvt




Overview
Explore in AI Chat

Overview

CSK_DIAG_SOLUTION_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Diagnostic Framework infrastructure used by the Common Support Kit (CSK, also marketed as "Support" applications) and the broader Diagnostic and Troubleshooting subsystem. The package implements the diagnostic "test" contract required by the JTF Diagnostics engine, exposing a small, standardized set of entry points that the framework calls in sequence when executing a diagnostic test from a support or troubleshooting interface.

Its role is to represent the "Solution" diagnostic test — that is, a diagnostic check whose purpose is to identify and report known solutions from the knowledge base, mapped to the observed configuration or symptom. The package encapsulates the logic, default inputs, cleanup, and reporting needed to run a single diagnostic step. Its header version (csktsols.pls 120.1) dates to 2005 and is marked noship, meaning it is shipped as part of the standard CSK diagnostic suite but is not intended for direct customer invocation.

As a _PVT package, it is an internal implementation unit. All documented procedures are intended to be invoked only by the diagnostic framework, not by customer or third-party code.

Key Procedures and Functions

Seven procedures make up the documented interface of CSK_DIAG_SOLUTION_PVT. They conform to the standard diagnostic test signature used across the support/diagnostics stack.

  • INIT — Initializes the diagnostic test, resetting package state and preparing any prerequisites before the test executes.
  • GETDEFAULTTESTPARAMS — Returns the default set of input values for the test. The framework uses this to pre-populate the diagnostic parameter screen so the user or calling program has sensible starting values.
  • GETCOMPONENTNAME — Returns the component or application name to which this diagnostic test belongs (typically a CSK/Support module identifier).
  • GETTESTNAME — Returns the human-readable name of the test, used in the diagnostics UI and report headers.
  • GETTESTDESC — Returns a description or help text for the test, displayed to the user before running.
  • RUNTEST — The core execution procedure. It accepts the input values supplied by the framework, performs the actual diagnostic logic (searching the knowledge base for applicable solutions), and populates both a structured diagnostic report and a CLOB report. The report is returned to the framework for display or logging.
  • CLEANUP — Releases resources and resets state after the test completes, ensuring repeated invocations do not leak session state.

Several package-level variables are declared to carry state across these calls, including l_statusStr, l_errStr, l_fixInfo, and l_isFatal. The report is emitted through JTF diagnostic types (JTF_DIAG_INPUTTBL, JTF_DIAG_REPORT), confirming integration with the JTF (CRM Foundation) diagnostic API.

Tables Accessed

The package touches a limited set of tables, all accessed through APPS synonyms:

  • CS_KB_SET_CATEGORIES — The Service/Knowledge Base set-category table. This is the primary data source for the Solution test: it allows the test to determine which knowledge base solution sets are relevant to the current context, so applicable solutions can be retrieved and reported.
  • DUAL — Used for simple scalar evaluations, confirmations, and to satisfy query structure where no real table is needed.
  • PLITBLM — A PL/SQL index-by table mapping helper used to manipulate the diagnostic input/report collections in memory.

No other application tables are referenced by the documented interface. Notably, the package does not perform DML on its own; it is essentially a read-and-report test.

Usage Notes

CSK_DIAG_SOLUTION_PVT is never invoked directly by end users or by custom code. It is registered as a diagnostic test with the CSK/Support diagnostic framework, and the framework drives its lifecycle: INIT is called first, then GETDEFAULTTESTPARAMS supplies the input screen, and finally RUNTEST is executed with the user's inputs, followed by CLEANUP. The GETCOMPONENTNAME, GETTESTNAME, and GETTESTDESC procedures are queried by the framework at registration or display time.

Typical invocation points include the Support Diagnostics test runner and any concurrent program or form that executes registered CSK diagnostic tests. In the ETRM metadata, the package is referenced by zero other packages, confirming it sits at the leaf of the dependency tree — a self-contained test implementation rather than a shared API. Because it is classified as a private (PVT) package and marked noship, upgrades or patches to it should be treated as support-infrastructure changes and not as targets for custom integration. Any customer extension intended to add solution diagnostics should follow the same JTF diagnostic contract and register its own test rather than calling this package.

For Oracle EBS 12.1.1 and 12.2.2, the package operates identically at the PL/SQL level; version differences in the surrounding CSK/JTF framework may affect which diagnostic tests are registered and which UI paths expose them, but the internal contract documented here remains stable.