A script-enabled browser is required for this page to function properly.

About Stored Programs

A stored procedure or stored function is a PL/SQL subprogram in the database that can be called by name from an application. Oracle Forms supports drag and drop application partitioning by using stored PL/SQL subprograms. Applications for deployment against the Oracle Application Server can include calls to server-side stored subprograms directly in the PL/SQL code of Oracle Forms triggers and user-named subprograms. From within Oracle Forms triggers and user-named subprograms, you can execute procedures and functions defined in a PL/SQL package as well was as access any of the subprograms at either the local or remote database server.

Processing within the form is on hold until the stored procedure or function completes execution, so the network and database load must be considered with regard to response time. The first time a user executes a stored procedure or function, the executable code is cached in the Oracle Database Server SGA—the shared global area. Because the code is cached, subsequent uses of the executable are faster. The first time any subprogram within a package is referenced, the entire package is loaded and becomes shareable.

Using a stored subprogram instead of a local Oracle Forms subprogram is recommended when a procedure or function provides standard functionality that other tools can share—such as validation and calculations. Stored subprograms are also recommended when performing a significant number of DML operations that can be processed in a bundle by the server.


About default values for formal parameters

About accessing subprograms in another user's Schema

About resolving subprogram names

About stored procedure privileges

Creating a Stored Program