Search Results fnd_concurrent_programs_s

Overview

FND_PROGRAM is a core Oracle E-Business Suite PL/SQL package body owned by the APPS schema whose primary business function is the programmatic administration and definition of concurrent programs and their associated metadata. In Oracle EBS, a concurrent program is the fundamental executable unit that users submit through the Submit Requests form, and each program must be registered against an executable, assigned parameters, and linked to request groups before it can be run. FND_PROGRAM provides the application programming interface that allows developers and administrators to perform these registration and maintenance tasks from code rather than exclusively through the Concurrent Programs, Executables, and Request Groups forms.

The package is classified as an OTHER API within the ETRM 12.2.2 documentation, meaning it is not an Open Interface or a public business API in the sense of FND_REQUEST, but it remains a widely referenced object. According to the dependency metadata, FND_PROGRAM is referenced by twenty-six other database objects, confirming its role as a foundational utility for oracle applications concurrent processing setup.

Key Procedures and Functions

The package exposes twenty-seven documented procedures and functions. Its registration and definition routines form the largest group: REGISTER handles creation of a concurrent program definition, while EXECUTABLE supports the registration of executables. PARAMETER and DELETE_PARAMETER manage the parameter definitions attached to a program, and DELETE_PROGRAM removes a program definition. Group administration is handled by REQUEST_GROUP, ADD_TO_GROUP, REMOVE_FROM_GROUP, and DELETE_GROUP, which maintain the request group to program associations used for security and menu assignment. Incompatibility management is provided by INCOMPATIBILITY and DELETE_INCOMPATIBILITY, with DELETE_EXECUTABLE complementing the executable registration function.

Several routines support validation and querying: PROGRAM_EXISTS, PARAMETER_EXISTS, and INCOMPATIBILITY_EXISTS allow calling code to test for the existence of definitions before attempting changes. ENABLE_PROGRAM toggles a program's enabled status. Diagnostic control functions DEBUG_ON and DEBUG_OFF, together with SET_SESSION_MODE and MESSAGE, provide instrumentation and user feedback during processing. The presence of MESSAGE indicates the package follows the standard EBS convention of accumulating or emitting messages for the calling form or program.

Tables Accessed

FND_PROGRAM reads and writes a broad set of concurrent processing tables through APPS synonyms. Program and executable definitions are stored in FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_PROGRAMS_S, FND_CONCURRENT_PROGRAMS_TL, FND_EXECUTABLES, FND_EXECUTABLES_S, FND_EXECUTABLES_TL, and FND_EXECUTABLES_VL, with translated columns in the _TL tables and sequences in the _S tables. Parameter metadata resides in FND_CONC_REQUEST_ARGUMENTS and FND_DESCR_FLEX_COLUMN_USAGES, and descriptive flexfield support relies on FND_DESCRIPTIVE_FLEXS, FND_DESCRIPTIVE_FLEXS_VL, and FND_FLEX_DSC_API.

Request group and scheduling information is drawn from FND_REQUEST_GROUPS, FND_REQUEST_GROUPS_S, FND_REQUEST_GROUP_UNITS, FND_REQUEST_SETS, FND_REQUEST_SETS_TL, FND_REQUEST_SET_PROGRAMS, and FND_REQUEST_SET_PROGRAM_ARGS. Release and period definitions are covered by FND_CONC_RELEASE_CLASSES, FND_CONC_RELEASE_DISJS, FND_CONC_RELEASE_PERIODS, and FND_CONC_RELEASE_STATES along with their translated and member tables. Supporting infrastructure includes FND_CONCURRENT_REQUESTS, FND_CONCURRENT_REQUEST_CLASS, FND_CONCURRENT_PROGRAM_SERIAL, FND_CONC_PP_ACTIONS, FND_RUN_REQUESTS, FND_RUN_REQ_PP_ACTIONS, FND_PRINTER, FND_PRINTER_INFORMATION, FND_PRINTER_STYLES, FND_APPLICATION, FND_APPLICATION_TL, FND_COLUMNS, FND_TABLES, FND_FLEX_VALUE_SETS, FND_LANGUAGES, FND_LOOKUP_VALUES, FND_GLOBAL, and DUAL.

Usage Notes

FND_PROGRAM is invoked primarily by the Oracle Applications concurrent programs and executables setup forms, and by the standard concurrent manager and request submission infrastructure. Custom code should call these routines when migrating concurrent program definitions between environments or when programmatically provisioning request groups and incompatibilities. Direct DML against the underlying FND_CONCURRENT_PROGRAMS and FND_EXECUTABLES tables is discouraged; the package encapsulates the required multilingual and sequence handling. Because the package depends on FND_GLOBAL, callers should ensure the application and session context is initialized before invocation. The behavior is consistent across EBS 12.1.1 and 12.2.2.