Search Results csm_setup_jtmconc




Overview
Explore in AI Chat

Overview

CSM_SETUP_JTMCONC is a diagnostic support package owned by the APPS schema and declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the calling user rather than the definer. It is part of the Oracle E-Business Suite diagnostic infrastructure associated with Oracle Common Modules and the JTF (Java/Task Framework) diagnostics framework. The package name combines the CSM product prefix with "SETUP_JTM" and "CONC," indicating that it is a setup or configuration verification test ("concurrent" or "constructor" style) built against the JTM concurrent-request data structures.

The package serves as a diagnostic test implementation. It conforms to the standard JTF diagnostic test shape, exposing the initialization, cleanup, execution, and descriptive-metadata entry points that the diagnostics engine requires in order to register and run a test. It does not implement business transactions, order processing, or any user-facing logic; its role is to validate that a particular configuration area of the E-Business Suite installation is reachable and internally consistent.

The user search term "TSM jdo isp" reflects the common confusion in this area: these acronyms (TSM, JDO, ISP) appear in Oracle's telecommunications service-management and Java Data Object integration layers, whose diagnostic and setup packages share the CSM/JTM naming patterns. CSM_SETUP_JTMCONC is one of the setup-level diagnostic packages in that family rather than a runtime provider for those services.

Key Procedures and Functions

  • INIT — Initialization entry point invoked by the diagnostics framework before the test body executes. Typically establishes session state, prepares any temporary structures, and performs precondition checks.
  • CLEANUP — Counterpart to INIT; releases session state and removes temporary objects created during the test so the diagnostic run leaves no residue.
  • RUNTEST — The principal test procedure. It runs the actual configuration check and populates the diagnostic report structures passed to it. Parameters are not documented in the available metadata and should be treated as the standard diagnostic input table and report outputs.
  • GETCOMPONENTNAME — Returns the component label under which this test is grouped in the diagnostics user interface.
  • GETTESTNAME — Returns the short name of the test as presented to the user.
  • GETTESTDESC — Returns the descriptive text explaining what the test verifies, which appears alongside the test name in the diagnostic output.

Tables Accessed

Two objects are referenced through APPS synonyms:

  • JTM_CON_REQUEST_DATA — The concurrent-request data store for the JTM layer. The package reads this table to confirm that setup and request-side records exist and are in an expected state as part of its verification logic.
  • PLITBLM — A PL/SQL internal table type used to marshal multi-row diagnostic result data (message lines) into the report. Its use reflects the standard diagnostics reporting convention rather than a persistent application table.

Usage Notes

The package is not intended to be called directly from a form or by custom application code. It is invoked by the Oracle EBS diagnostics framework (Oracle Applications Manager / Diagnostic Tests), which calls INIT, RUNTEST, and CLEANUP in sequence and interrogates GETCOMPONENTNAME, GETTESTNAME, and GETTESTDESC to present the test in the UI. There are no concurrent programs or forms documented as directly referencing this package, and no other packages reference it, confirming its role as a leaf-level diagnostic unit. Custom code should not depend on its procedures; use the standard diagnostics APIs instead. The header revision ($Header: csmdjcrs.pls 120.1, 2005) places the current implementation as stable since the 11i era, carried forward unchanged into 12.1.1 and 12.2.2.