Search Results fnd_amp_private




Overview
Explore in AI Chat

Overview

FND_AMP_PRIVATE is a private PL/SQL package body in the APPS schema that supports Oracle EBS Application Management Pack (AMP) integration for concurrent processing. It exposes low-level administrative routines that allow external management tooling — most notably Oracle Enterprise Manager's Application Management Pack and the concurrent manager console — to observe, control, and manipulate concurrent requests and their associated database sessions. The package status is VALID, and its API classification is OTHER, indicating it is not a public, documented extension API but an internal implementation package used by Oracle's own management framework.

The package isolates privileged session- and request-manipulation logic into a single module, allowing the Application Management Pack to perform actions such as diagnosing why a request is waiting, determining the phase and status of a running request, terminating a database session, cancelling a concurrent request, toggling a request hold, and changing a request's priority. Because these operations are sensitive, they are held privately and are not intended for direct customer invocation.

Key Procedures and Functions

Seven documented routines comprise the package. They are described below; parameter signatures are not published.

  • WHY_WAIT — Determines and reports the reason a concurrent request is in a waiting state, enabling administrators to diagnose contention, serialization, or resource-lock conditions.
  • GET_PHASE — Retrieves the current phase of a concurrent request (for example, Pending, Running, or Completed) as maintained by the concurrent manager.
  • GET_STATUS — Returns the current status code of a concurrent request, complementing phase information for full lifecycle tracking.
  • KILL_SESSION — Terminates the database session associated with a runaway or hung concurrent request, drawing on session information from GV$SESSION.
  • CANCEL_REQUEST — Cancels an active concurrent request, updating the request records through the concurrent request interfaces.
  • TOGGLE_REQUEST_HOLD — Places a request on hold or releases an existing hold, allowing administrative control over request scheduling.
  • ALTER_REQUEST_PRIORITY — Changes the priority of a queued or pending concurrent request, influencing the order in which the concurrent manager processes it.

Tables Accessed

The package reads and writes a small set of documented objects, referenced through APPS synonyms:

  • FND_CONCURRENT_REQUESTS — The primary repository of concurrent request state, phase, status, priority, and hold flags. Most routines read from and update this table.
  • FND_CONCURRENT_PROGRAM_SERIAL — Used to evaluate serialization and incompatibility rules that determine why a request may be waiting (relevant to WHY_WAIT).
  • DBMS_SQL — Utilized for dynamic SQL execution, supporting flexible query construction at runtime.
  • GV$SESSION — Provides the session-level information required by KILL_SESSION to identify and terminate the owning database session.

In addition, dependencies include FND_CONC, FND_CONC_REQUEST_PKG, FND_GLOBAL, FND_LOG, FND_MESSAGE, and FND_PROFILE, which supply concurrent manager access, request APIs, session/global context, logging, message retrieval, and profile option values respectively.

Usage Notes

FND_AMP_PRIVATE is not referenced by any other database object and is not intended as a public API. It is invoked indirectly through Oracle's Application Management Pack and concurrent manager administrative interfaces rather than from customer forms or concurrent programs. Custom code should generally avoid direct calls to this package, since its routines are private, unsupported, and subject to change without notice. Where equivalent functionality is required, developers should use supported public APIs such as FND_REQUEST or the documented FND_CONC_REQUEST_PKG interfaces instead.