Search Results delete_executable

Overview

APPS.FND_PROGRAM is an Oracle E-Business Suite database package classified as a Concurrent Program Loader. It belongs to the FND product and is owned by the APPS schema, with an AUTHID CURRENT_USER declaration. The package provides the programmatic foundation for creating and maintaining the metadata that drives the Oracle Concurrent Manager: concurrent program executables, concurrent programs with their parameters and incompatibility rules, request sets, and request groups. Its documented display name, "Concurrent Program Loaders," reflects this role as an administrative loader interface rather than a runtime execution API. The package is lifecycle-active and rated "S" (supported) for compatibility, and its header dates to a 2012 revision delivered through patch 120.2.12020000.3. In practice, FND_PROGRAM is the API surface that allows developers and administrators to seed or update concurrent program definitions without navigating every individual setup form.

Key Procedures and Functions

The package exposes 27 documented procedures and functions, 21 of which are enumerated in the ETRM metadata. They fall into several functional clusters.

• Session and diagnostics: DEBUG_ON and DEBUG_OFF toggle diagnostic output, while SET_SESSION_MODE establishes the package mode for the current session, accepting a seed_data value for datamerge operations and customer_data as the default.
• Error retrieval: MESSAGE returns the error message text set when validation errors occur during processing of other routines in the package.
• Definition creation: EXECUTABLE creates a concurrent program executable; REGISTER registers a concurrent program; PARAMETER creates a parameter for a specified concurrent program; INCOMPATIBILITY defines incompatibility rules; REQUEST_GROUP creates a request group; and ADD_TO_GROUP and REMOVE_FROM_GROUP manage membership within a request group.
• Deletion: DELETE_PROGRAM, DELETE_PARAMETER, DELETE_EXECUTABLE, DELETE_GROUP, and DELETE_INCOMPATIBILITY remove the corresponding definitions.
• State change and validation: ENABLE_PROGRAM toggles a program's enabled status, while PROGRAM_EXISTS, PARAMETER_EXISTS, and INCOMPATIBILITY_EXISTS provide existence checks used to avoid duplicate definitions or to confirm setup before further processing.

No parameter lists are documented in the available metadata beyond the excerpted PARAMETER signature, so the routines are described here by purpose only.

Tables Accessed

The package operates against the core concurrent processing data model through APPS synonyms, covering both definitional and runtime-adjacent structures.

• Concurrent program definitions: FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_PROGRAMS_S, and FND_CONCURRENT_PROGRAMS_TL hold the base, sequence, and translation records for registered programs.
• Executables and parameters: FND_CONC_PP_ACTIONS and FND_CONCURRENT_PROGRAM_SERIAL support parameter and executable assignment behavior.
• Release and request classes: FND_CONC_RELEASE_CLASSES, FND_CONC_RELEASE_CLASSES_TL, FND_CONC_RELEASE_DISJS, FND_CONC_RELEASE_DISJS_TL, and FND_CONC_RELEASE_PERIODS define release class details, disjointness rules, and period constraints used for scheduling and incompatibility logic.
• Requests and lookup support: FND_CONCURRENT_REQUESTS and FND_CONCURRENT_REQUEST_CLASS are referenced for request context, while FND_APPLICATION, FND_APPLICATION_TL, and FND_COLUMNS provide application ownership and value-set column metadata.

Usage Notes

FND_PROGRAM is typically invoked from custom PL/SQL loaders, installation or upgrade scripts, and datamerge seed-data routines rather than from end-user forms; SET_SESSION_MODE explicitly distinguishes seed_data from customer_data to control this behavior. The package is referenced by 26 other packages, indicating broad internal reuse across the FND loaders. Because its routines write directly to concurrent program and request group metadata, callers should validate existence using the *_EXISTS functions, check MESSAGE after failures, and enable diagnostics with DEBUG_ON during troubleshooting. Direct DML against the underlying FND_CONCURRENT_* tables is discouraged in favor of this API, which enforces the expected validation and consistency rules.