Search Results call_pp_plsql




Overview
Explore in AI Chat

Overview

FND_CONC_PRIVATE_UTILS is an internal, Oracle-owned PL/SQL package in the APPS schema that supplies low-level infrastructure services to the Oracle E-Business Suite Concurrent Processing framework. As the "PRIVATE" designation implies, it is not a published extension API and carries an API classification of OTHER in the ETRM repository. Its responsibilities cluster around three areas: resolving and sequencing concurrent manager runtime state (service names, resubmission timing, manager recovery, and multi-organization session context), dispatching PL/SQL execution requests on behalf of the concurrent managers (notably for concurrent programs whose execution method is PL/SQL Stored Procedure), and governing the use of temporary files created by concurrent programs through FND_FILE. Because FND_FILE itself is listed as a dependent object, the package forms part of the plumbing beneath the standard FND_FILE.PUT_LINE, FND_FILE.PUT, and FND_FILE.CLOSE logging and output interfaces used by virtually every concurrent program.

Key Procedures and Functions

  • GET_FS_SVC_NAME — Returns the file-system service name associated with the current concurrent manager context, used to identify where output and log files are physically written.
  • GET_RESUB_TIME — Calculates the next resubmission time for recurring concurrent requests, applying the release class, release period, and conjunction/disjunction member rules.
  • SEND_SIMPLE_DONE_MSG — Sends a simple completion notification (typically via Workflow notifications) indicating that a concurrent request has finished.
  • RECORD_TEMP_FILE_USE — Registers a temporary file created by a concurrent program so that the framework can track its existence and eventual cleanup.
  • ERASE_TEMP_FILE_USE — Removes a temporary file's tracking record, normally after the file has been deleted or is no longer needed.
  • CHECK_TEMP_FILE_USE — Validates whether a given temporary file is currently registered as in use, preventing premature deletion.
  • CALL_PP_PLSQL — Invokes the PL/SQL stored procedure associated with a concurrent program, serving as the bridge between the concurrent manager and the program's executable logic.
  • SET_MGR_RCG — Establishes manager recovery information so that a concurrent manager can be restarted or recognized after failure.
  • SET_MULTIORG_CONTEXT — Sets the multi-organization (MO) session context, ensuring that concurrent programs execute against the correct operating unit or inventory organization.

A tenth routine is documented in the ETRM metadata but is not individually described in the excerpt; the nine above represent the substantive functional surface.

Tables Accessed

The package reads and writes core Concurrent Processing tables through APPS synonyms. FND_CONCURRENT_QUEUES and FND_CONCURRENT_REQUESTS provide manager and request state. FND_CONC_RELEASE_CLASSES, FND_CONC_RELEASE_PERIODS, FND_CONC_REL_CONJ_MEMBERS, and FND_CONC_REL_DISJ_MEMBERS drive recurring-request resubmission logic. FND_TEMP_FILES backs the temporary-file tracking procedures. FND_USER and WF_NOTIFICATIONS support completion messaging. DBMS_SESSION and DUAL are used for session context and utility operations, while V$SESSION is referenced for session-level runtime information.

Usage Notes

This package is invoked internally by the concurrent manager and by FND_FILE rather than by direct customer calls. Custom code should not call FND_CONC_PRIVATE_UTILS routines directly, as they are subject to change between releases (12.1.1 and 12.2.2 in this context) without notice. Administrators encountering it will typically do so when diagnosing concurrent manager startup, resubmission, multi-org context, temporary file, or output/log file issues. The package is referenced by only one other package in the repository, reflecting its narrow, framework-internal role.