Search Results refresh_all_app_level_acc

Overview

CSM_SETUP_JTMCONC is a diagnostic test package body owned by APPS and classified under the ETRM taxonomy as OTHER. Its documented purpose is to validate the configuration and runtime behavior of the Oracle EBS concurrent processing infrastructure, specifically as it relates to the JTM (Territory Manager / Service) module. The package name combines "CSM_SETUP" (a setup verification family) with "JTMCONC" (JTM concurrent), indicating it is a setup-diagnostic utility rather than a transactional API.

The package body follows the standard Oracle Diagnostics (JTF_DIAG) test framework. Each diagnostic package in this framework supplies a set of well-known entry points that the Diagnostics launch pad uses to initialize test data, execute the test, and clean up afterward. The header comment (identifying the PL/SQL file as csmdjcrb.pls, revision 120.1, dated 2005) and the embedded template notes confirm that this package was generated for the Diagnostics repository and populated by a test author.

Notably, the body's initial code shows that init and cleanup are currently stubbed with NULL statements and are explicitly marked "not currently being called." The substantive logic therefore resides in the test execution path, which inspects concurrent manager / concurrent request configuration for the JTM schema.

Key Procedures and Functions

• INIT — Pre-test setup hook. Documented as intended to initialize test data structures before a diagnostic run. The body currently contains no executable logic.
• CLEANUP — Post-test teardown hook. Documented as intended to remove any structures created during INIT. Also currently a null stub.
• RUNTEST — The core diagnostic routine. It accepts diagnostic inputs, writes into a report object, and returns a CLOB report. Inside, it declares a local record/table type used to collect concurrent package and procedure names, then builds the result set presented to the user. This is the procedure invoked when a user selects the test and presses "Run."
• GETCOMPONENTNAME — Returns the display name of the component (product/application grouping) to which the test belongs, so the Diagnostics UI can categorize it.
• GETTESTNAME — Returns the unique name of the individual test, used as the identifier in diagnostic output and logs.
• GETTESTDESC — Returns the human-readable description of the test, shown to the user before execution so the purpose of the check is understood.

These six procedures are the standard Diagnostics contract. No parameter lists are documented in the metadata beyond the RUNTEST signature shown in the source excerpt.

Tables Accessed

• JTM_CON_REQUEST_DATA — The primary data source. RUNTEST queries this JTM concurrent request data table to gather the concurrent request package/ procedure information it evaluates, populating the local concTable collection shown in the source.
• PLITBLM — A standard Oracle Utilities/Diagnostics support table accessed via APPS synonym, typically used for line/item intermediate storage or DDL/temp processing in SR-based diagnostics.

Both are accessed through APPS synonyms, so no direct schema qualification is required when the package executes as APPS.

Usage Notes

CSM_SETUP_JTMCONC is not called by any other PL/SQL package in the ETRM dependency graph (referenced by zero packages). It is designed to be invoked exclusively through the Oracle Diagnostics framework, reached from the Diagnostics launch pad in HTML-based EBS or through the "Diagnostics" menu in the System Administrator responsibility. In 12.1.1 and 12.2.2 alike, this package is shipped as an APPS-owned, non-customized diagnostic artifact.

Because the search term "refresh_acc" appears in the user query, it is worth noting that this package does not expose a documented refresh or accounting refresh routine; it is a read-oriented setup/concurrent diagnostic. Any expectation of an accounting refresh API should be redirected to the appropriate accounting setup packages. Custom code should not depend on INIT, CLEANUP, or RUNTEST signatures directly, as the Diagnostics contract is internal and subject to change across patch levels.