Search Results use_current_notification

Overview

APPS.FND_REQUEST is the core public PL/SQL package in Oracle E-Business Suite that provides concurrent processing utilities. It is owned by the Application Object Library (product FND) and is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer. The package carries the display name "Concurrent Request" and is classified under the business entity FND_CP_REQUEST with a public scope, active lifecycle, and "S" (supported) compatibility rating. Its header identifies the file as AFCPREQS.pls.

FND_REQUEST serves as the programmatic entry point for submitting and configuring concurrent requests. Every concurrent program submitted from PL/SQL, forms, or database triggers relies on this package to establish submission context — mode, request attributes, organization, printing, notifications, and delivery — before invoking the actual submit routine. It is one of the most heavily depended-upon objects in EBS: the metadata records that it is referenced by 936 other packages.

Key Procedures and Functions

The package exposes 35 documented procedures and functions. They fall into two broad groups: option-setting routines called before submission, and request-submission routines.

• SET_MODE — Called before submitting a request to place the package in database trigger mode.
• SET_OPTIONS — Sets miscellaneous request attributes such as implicit submission behavior, protected status, NLS language, territory, data group, and numeric characters.
• SET_DEST_OPS — Establishes destination-related options for the request.
• SET_ORG_ID — Sets the organization context for the request.
• SET_REPEAT_OPTIONS — Controls resubmission/repeat scheduling behavior.
• SET_INCREMENT_DATES_OPTION — Controls the increment-dates behavior for repeating requests.
• SET_REL_CLASS_OPTIONS — Sets release class options governing when a request becomes runnable.
• SET_TARGET_OPTIONS — Sets target (node/queue) options for request execution.
• SET_PRINT_OPTIONS — Configures printing behavior for the request output.
• USE_CURRENT_NOTIFICATION — Directs the request to use the current notification context.
• ADD_PRINTER, ADD_NOTIFICATION, ADD_LAYOUT, ADD_LANGUAGE, ADD_DELIVERY_OPTION — Incrementally add printers, notification recipients, layouts, languages, and delivery options to the pending request.
• SUBMIT_REQUEST — The principal submission routine that creates the concurrent request.
• SUBMIT_SVC_CTL_REQUEST, SUBMIT_SVC_CTL_BY_APP, SUBMIT_SVC_CTL_BY_SVC — Variants for submitting service control requests, by application or by service.
• INTERNAL — An internal supporting routine.

Tables Accessed

The package reads and writes through APPS synonyms. The primary transactional table is FND_CONCURRENT_REQUESTS, with FND_CONCURRENT_REQUESTS_S supplying the sequence for request IDs. Request definition and validation rely on FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_PROGRAMS_TL, FND_APPLICATION, FND_CONCURRENT_QUEUES, FND_CONC_RELEASE_CLASSES (plus _S and _TL), FND_DATA_GROUPS, FND_CP_SERVICES, FND_CONC_PROG_ONSITE_INFO, and FND_CONC_PP_ACTIONS. Arguments are handled through FND_CONC_DEFERRED_ARGUMENTS and FND_CONC_REQUEST_ARGUMENTS. Together these tables store program metadata, queue and release-class definitions, submitted request rows, and parameter values.

Usage Notes

FND_REQUEST is typically invoked from concurrent program forms, database triggers, and custom PL/SQL. The standard pattern is to call SET_OPTIONS and any additional SET_* routines (organization, printing, repeat, release class, target, delivery) before SUBMIT_REQUEST, which commits the request row. Because the package is AUTHID CURRENT_USER and granted to APPS, custom code should qualify it as APPS.FND_REQUEST. The presence of SET_INCREMENT_DATES_OPTION reflects the fine-grained control Oracle exposes over repeat scheduling. Given its 936 dependent packages, changes to its behavior should be treated as high-impact.