Search Results execute_plsql




Overview
Explore in AI Chat

Overview

FND_OAM_DSCRAM_PLSQLS_PKG is an internal Oracle E-Business Suite package owned by the APPS schema and classified under the OTHER API category. It forms part of the Oracle Applications Manager (OAM) Diagnostic Script (DSCRAM) framework, a diagnostic and data-collection utility that executes predefined PL/SQL blocks against an EBS instance for troubleshooting and health-check purposes. This package specifically manages the PL/SQL execution units that comprise individual diagnostic scripts. It tracks which PL/SQL statements belong to a diagnostic run, executes them over defined data ranges, maintains a writable-argument cache, and disposes of cache entries once execution completes. In the context of EBS 12.1.1 and 12.2.2, this package is not a public API; it is invoked internally by the DSCRAM engine and is documented in ETRM as VALID in the APPS schema.

The metadata lists eight documented procedures/functions, and the package is referenced by two other DSCRAM packages. The "dscram" naming (diagnostic script) and the presence of range-based execution and cache management confirm its role as an orchestration layer beneath the DSCRAM user interface.

Key Procedures and Functions

  • GET_CURRENT_PLSQL_ID — Retrieves the identifier of the currently active PL/SQL unit within a diagnostic script execution.
  • FETCH_PLSQL_IDS — Fetches the set of PL/SQL IDs associated with a diagnostic script or run, providing the iteration basis for execution.
  • EXECUTE_PLSQL_ON_RANGE — Executes PL/SQL over a specified range of records, supporting chunked or partitioned processing of diagnostic statements.
  • EXECUTE_PLSQL — Performs the execution of a single PL/SQL unit, serving as the core statement runner.
  • UPDATE_COMP_PLS_WRITABLE_ARGS — Updates the writable arguments associated with a PL/SQL unit, managing component argument state prior to execution.
  • COMPLETE_PLSQL — Marks a PL/SQL unit as complete, finalizing its status within the diagnostic run.
  • DESTROY_PLSQL_CACHE_ENTRY — Removes a single cache entry for a PL/SQL unit, releasing resources at the unit level.
  • DESTROY_PLSQL_CACHE — Clears the PL/SQL cache as a whole, typically invoked at the end of a diagnostic session.

These procedures are not documented with public parameter lists; they are internal DSCRAM engine calls.

Tables Accessed

The package references FND_OAM_DSCRAM_PLSQLS via APPS synonyms, the primary repository holding PL/SQL definitions and status for diagnostic scripts. It also references DBMS_SQL for dynamic SQL parsing and execution, PLITBLM for internal PL/SQL instrumentation, and STANDARD for core PL/SQL operations. These objects are read and written to resolve, execute, and track PL/SQL units during a diagnostic run.

Usage Notes

FND_OAM_DSCRAM_PLSQLS_PKG is executed indirectly through the OAM Diagnostic Scripts framework and concurrent diagnostic processing, not through EBS forms or direct user calls. It depends on FND_OAM_DSCRAM_ARGS_PKG and FND_OAM_DSCRAM_UNITS_PKG, and is itself referenced by those same packages, indicating a tightly coupled internal call graph. Custom code should not invoke this package directly; use the supported DSCRAM interfaces instead.