Search Results request_position

Overview

APPS.FND_CONC_REQUEST_PKG is a core Oracle E-Business Suite package that provides the underlying programmatic logic for managing concurrent requests within the Concurrent Manager infrastructure. It is a VALID object owned by the APPS schema, and it is classified under the API classification of OTHER. In the context of Oracle EBS 12.1.1 and 12.2.2, this package serves as a supporting utility layer that the Concurrent Manager, the standard concurrent request submission forms, and related maintenance programs rely upon to query request state, retrieve descriptive user and program information, and administer the parent-child relationships between concurrent requests.

The package is not a public, developer-facing API in the conventional sense. Rather, it is an internal implementation package referenced by other EBS components. ETRM documentation confirms that it is referenced by objects including FND_AMP_PRIVATE, FND_CONC_REQUESTS_FORM_V, FND_REQUEST_COPY, FND_SET_COPY, and even by itself, which illustrates its role as a shared dependency across concurrent processing utilities.

Key Procedures and Functions

The documented package exposes sixteen procedures and functions. These can be grouped by purpose:

• Information retrieval: GET_PROGRAM_INFO returns details about a concurrent program; GET_USER_NAME resolves the user associated with a request; and ROLE_INFO returns role-related information. GET_USER_PHASE_CODE, GET_USER_STATUS_CODE, GET_USER_PRINT_STYLE, and GET_PHASE_STATUS resolve the display-oriented phase, status, print style, and phase status values used when rendering request output.
• Request administration: LOCK_PARENT and RESTART_PARENT support parent-child request handling by locking or restarting a parent request. DELETE_CHILDREN removes child requests associated with a parent.
• Request listing: REQUEST_POSITION determines the position of a request; RUNNING_REQUESTS and PENDING_REQUESTS return the set of currently running or pending requests respectively.
• Supporting utilities: ENCODE_ATTRIBUTE_ORDER and FNDCPQCR_INIT are initialization and encoding helpers used internally by the concurrent request machinery.

Parameter lists are intentionally not reproduced here; the documented metadata confirms the existence and purpose of each routine but does not publish full signatures.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• FND_CONCURRENT_REQUESTS: the central table holding concurrent request records. The package queries and updates request phase, status, and parent-child relationships here.
• FND_USER: used by GET_USER_NAME and related routines to resolve the user identity for a request.
• FND_DESCR_FLEX_COLUMN_USAGES: referenced when resolving descriptive flexfield column usage related to request attributes.
• DATABASE_PROPERTIES: accessed to resolve database-level configuration values used during request processing.

Usage Notes

FND_CONC_REQUEST_PKG is normally invoked indirectly rather than by custom code. The primary entry points are the standard concurrent request forms (referenced via FND_CONC_REQUESTS_FORM_V) and maintenance utilities such as FND_REQUEST_COPY and FND_SET_COPY, which call its routines to copy, restart, or describe requests. In custom development, direct invocation should be avoided where a public API exists, because this package is an internal dependency and signatures may change across patch levels. When troubleshooting concurrent request behavior in 12.1.1 or 12.2.2, the package is most often examined through its dependent objects to understand how a request's phase, status, and parent-child relationships are being determined.