Search Results fnd_diag_request_analyzer




Overview
Explore in AI Chat

Overview

FND_DIAG_REQUEST_ANALYZER is a diagnostic utility package in the Oracle E-Business Suite Applications (APPS) schema. It forms part of the Oracle EBS Diagnostic Framework, which supplies the runtime engine behind the "Diagnostics" and "Diagnostic Tests" functionality accessible from the Oracle Applications administrator menus. The package is declared AUTHID CURRENT_USER, meaning its unqualified database references resolve under the privileges of the invoking user rather than the definer, an important characteristic for a framework that must execute checks against concurrent manager and concurrent request data visible to the calling session.

Its documented source header places the package file (AFCPDRAS.pls) at version 120.0, dated 2009, which is consistent with its inclusion in the 12.1.1 and 12.2.2 code lines. The package is classified as OTHER in the ETRM repository and is not referenced by any other documented package, indicating that it is an end-point analyzer rather than a shared library. Its business purpose is to analyze concurrent request and concurrent manager state on behalf of the Diagnostic Framework, producing structured test output that the framework renders to the administrator. This is the package that backs the diagnostic test commonly queried as "manager_check," a name that corresponds directly to the MANAGER_CHECK procedure documented below.

Key Procedures and Functions

The package exposes twelve documented program units. The diagnostic framework contract is satisfied by the standard test interface procedures: RUNTEST executes the analyzer and returns its result through an execution object; GETTESTNAME and GETTESTDESC supply the display name and description of the test; GETDEFAULTTESTPARAMS returns default input values; GETERROR, GETFIXINFO, ISWARNING, and ISFATAL report error text, remediation information, and severity flags. GET_STATUS and GET_PHASE translate raw concurrent request status and phase codes into readable text.

The two procedures of most practical interest to administrators are MANAGER_CHECK and PRINT_MGRS. MANAGER_CHECK accepts a request identifier and a concurrent program definition identifier, then evaluates the associated concurrent manager conditions. It returns a set of boolean outcomes covering whether a manager is defined, whether that manager is active, whether it falls within its work shift, whether it is currently running, and whether the affected request is permitted to run alone. PRINT_MGRS takes a request identifier along with a diagnostic section object and report context, and formats the manager information into the diagnostic report output. Together these two units give the framework the ability to explain why a submitted concurrent request is not being picked up, the classic symptom that motivates a manager_check diagnostic run.

Tables Accessed

The package reads from the core Concurrent Processing tables through APPS synonyms. FND_CONCURRENT_PROGRAMS and FND_EXECUTABLES supply the program and executable definitions needed to identify what was submitted. FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAM_SERIAL provide the request row and its serialization information. FND_CONCURRENT_REQUEST_CLASS and FND_CONFLICTS_DOMAIN establish the request's class membership and its conflict domain, which determine manager compatibility and whether the request may run alone. FND_USER supports identification of the submitting user. DUAL and PLITBLM are used for trivial expression evaluation and for the standard PL/SQL table-management package.

Usage Notes

FND_DIAG_REQUEST_ANALYZER is generally not invoked directly by application users. It is dispatched by the Oracle EBS Diagnostic Framework when an administrator runs a concurrent manager diagnostic test from the Diagnostics responsibility, or when the framework is triggered from concurrent request troubleshooting screens. The output is surfaced through the framework's report rendering, which consumes the JTF diagnostic section and report context objects referenced in the PRINT_MGRS signature. Custom code should not rely on this package as a supported API; because it is classified OTHER and is not referenced by any other documented package, its interface may change between patch sets. When investigating a stalled request, administrators should invoke the manager_check diagnostic through the standard Diagnostics interface rather than calling MANAGER_CHECK directly, ensuring that the returned flags are interpreted and presented by the framework that expects them.