Results for “fnd_request”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_REQUEST is the core Oracle E-Business Suite concurrent processing submission package. It provides the PL/SQL interface through which any application, form, concurrent program, or custom code submits a concurrent request to the Concurrent Managers for execution. The package encapsulates the logic that validates the requested concurrent program, resolves the target application, responsibility, and user context, assembles execution options such as printer, layout, language, and output delivery, and finally inserts the request record into the concurrent requests tables so that the request can be picked up by an active manager. In EBS 12.1.1 and 12.2.2, FND_REQUEST is an APPS-owned, VALID package body that is not referenced by any database object, meaning it is invoked directly by client code rather than by triggers or dependency chains. It is among the most heavily reused objects in the EBS data dictionary, being referenced by 936 other packages, which reflects its role as the universal entry point for concurrent request submission.

Key Procedures and Functions

The documented interface exposes 35 procedures and functions. The most significant is SUBMIT_REQUEST, which performs the actual submission of a concurrent program on behalf of the calling session and returns the concurrent request ID. The INTERNAL procedure supports internal submission logic used by the packaged submission flow. The SET_* family configures submission behavior prior to calling SUBMIT_REQUEST: SET_MODE, SET_OPTIONS, SET_DEST_OPS, SET_ORG_ID, SET_REPEAT_OPTIONS, SET_INCREMENT_DATES_OPTION, SET_REL_CLASS_OPTIONS, SET_TARGET_OPTIONS, and SET_PRINT_OPTIONS. Supporting procedures ADD_PRINTER, ADD_NOTIFICATION, ADD_LAYOUT, ADD_LANGUAGE, and ADD_DELIVERY_OPTION append output, notification, and delivery attributes to the pending request definition. USE_CURRENT_NOTIFICATION sets notification behavior. The service-control procedures SUBMIT_SVC_CTL_REQUEST, SUBMIT_SVC_CTL_BY_APP, and SUBMIT_SVC_CTL_BY_SVC submit requests associated with service control operations.

Tables Accessed

FND_REQUEST reads and writes the concurrent processing foundation tables through APPS synonyms. FND_CONCURRENT_REQUESTS and FND_CONCURRENT_REQUESTS_S hold the submitted request header and its sequence identifier. FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_PROGRAMS_TL validate the program definition and retrieve its translated name. FND_CONCURRENT_QUEUES and FND_CONCURRENT_QUEUES-related objects resolve the target queue and manager assignment. FND_CONC_REQUEST_ARGUMENTS and FND_CONC_DEFERRED_ARGUMENTS store argument values. FND_CONC_PP_ACTIONS and FND_CONC_PROG_ONSITE_INFO support post-processing and onsite program behavior. FND_CONC_RELEASE_CLASSES, FND_CONC_RELEASE_CLASSES_S, and FND_CONC_RELEASE_CLASSES_TL manage release class definitions. FND_APPLICATION, FND_CP_SERVICES, and FND_DATA_GROUPS provide application, service, and group context.

Usage Notes

FND_REQUEST is normally invoked from Oracle Forms at the point a user presses Submit, from concurrent programs that spawn child requests, and from custom PL/SQL that needs to schedule background work. The idiomatic pattern is to set session context, optionally call the SET_* configuration procedures, then call SUBMIT_REQUEST, which returns the concurrent request ID or zero on failure. Because the package is not referenced by other database objects, its public interface is stable and intended for direct caller use.