26-12 Oracle E-Business Suite Developer's Guide
Use this procedure to close open files.
Important: Use FND_FILE.CLOSE only in
command lines sessions.
FND_FILE.CLOSE should not be called
from a concurrent program.
/* Some logic here... */
fnd_file.put_line(fnd_file.output, 'Reached point A');
/* More logic, etc... */
The FND_FILE package can raise one exception, FND_FILE.UTL_FILE_ERROR, which
is raised to indicate an UTL_FILE error condition. Specifically, the procedures
FND_FILE.PUT, FND_FILE.PUT_LINE and FND_FILE.NEW_LINE can raise
FND_FILE.UTL_FILE_ERROR if there is an error. In addition to this package exception,
FND_FILE can also raise predefined PL/SQL exceptions such as NO_DATA_FOUND or
FND_FILE will raise a UTL_FILE_ERROR if it is not able to open or write to a
temporary file. It is up to the concurrent program to error out or complete normally,
after the FND_FILE.UTL_FILE_ERROR exception is raised. FND_FILE keeps the
translated message in the message stack before raising the UTL_FILE_ERROR
exception. Developers can get the message for FND_FILE errors and use it as a Request
Completion text. It is up to the caller to get the message from the message stack by
using the FND_MESSAGE routine within an exception handler.
The concurrent manager will keep all the temporary file creation errors in the request
FND_PROGRAM: Concurrent Program Loaders
The FND_PROGRAM package includes procedures for creating concurrent program
executables, concurrent programs with parameters and incompatibility rules, request
sets, and request groups. The FND_PROGRAM package also contains functions you can
use to check for the existence of concurrent programs, executables, parameters, and
The arguments passed to the procedures correspond to the fields in the Oracle