Search Results get_request_status

Overview

ZPB_FND_UTIL is a utility package body owned by the APPS schema and classified in the ETRM repository as a UTIL (utility) API. Its purpose is to provide shared helper routines that wrap or simplify standard Oracle E-Business Suite foundation services for use by other custom code. In the Oracle EBS 12.1.1 and 12.2.2 environments, packages of this nature are typically created by implementation or development teams to centralize frequently repeated low-level calls, reduce code duplication, and standardize error handling across concurrent programs, forms, and custom PL/SQL routines.

The package header line, as documented, lists a single exposed function, GET_REQUEST_STATUS, and the body contains no additional private or public subprograms. The package therefore acts as a thin, single-purpose façade over the Oracle Application Object Library concurrent manager API. The package header revision string (ZPBFNDUB.pls 120.0.12010.2) and the "noship" designation indicate this is a custom, non-shipped object rather than a seeded Oracle product component.

Key Procedures and Functions

The documented function for this package is GET_REQUEST_STATUS. It is explicitly described in the source as a "wrapper function to fnd_concurrent.get_request_status," meaning it delegates the underlying work to the standard Oracle concurrent manager API of the same conceptual name rather than reimplementing any logic itself.

• GET_REQUEST_STATUS — A function that returns a numeric return code. Internally it calls fnd_concurrent.get_request_status, passing through the request identifier and the various optional application, program, phase, status, and message parameters. It converts the Boolean result of the underlying FND call into a numeric convention: it returns 0 when the underlying call succeeds and -1 when it fails. The signature uses IN OUT NOCOPY and OUT NOCOPY parameter modes, a common performance pattern in EBS PL/SQL to avoid unnecessary parameter copying for larger values.

No other functions or procedures are documented for this package body. The absence of additional subprograms reinforces that the package exists solely to normalize the return value of the concurrent request status query for downstream callers.

Tables Accessed

The ETRM metadata for ZPB_FND_UTIL does not document any direct table references via APPS synonyms. This is consistent with the package's role as a wrapper: all data access is performed indirectly by the underlying fnd_concurrent.get_request_status API, which queries the standard Oracle Application Object Library concurrent request views and tables (such as FND_CONCURRENT_REQUESTS and related views) on behalf of the caller. The wrapper package itself neither issues direct DML nor maintains its own persistent state, and it is not referenced by any other package according to the repository metadata, confirming it is a leaf-level utility with no downstream dependents tracked in ETRM.

Usage Notes

Because GET_REQUEST_STATUS is a utility wrapper, it is typically invoked from custom concurrent programs, forms, or PL/SQL batch logic that needs to determine whether a submitted concurrent request has completed and what its phase, status, and completion message are. Callers pass a request identifier and receive both the out parameters describing phase and status and a simple numeric return code (0 for success, -1 for failure) that is convenient for branching and for populating a standard return-status variable.

The returned phase and development status values follow the Oracle concurrent manager conventions (for example, Pending, Running, Completed, and the corresponding normal, warning, or error development statuses), and the message parameter carries the completion message when available. Developers should note that the function relies entirely on the FND concurrent manager infrastructure, so the applicability of results depends on the concurrent manager being available and the request being visible to the calling session. As a custom, non-shipped object, it should be reviewed and potentially revalidated during upgrades from 12.1.1 to 12.2.2 to confirm continued compatibility with the underlying FND API signature.