Search Results release_names

Overview

FND_FILE is the Oracle E-Business Suite core PL/SQL package responsible for writing text to the log and output files associated with concurrent program execution. Any concurrent program, report, or custom process registered in Oracle EBS relies on this package to emit diagnostic messages, status information, and report content to the standard log and output destinations managed by the Concurrent Manager. The package abstracts the underlying UTL_FILE layer, insulating developers from platform-specific directory paths, file naming conventions, and buffer handling. In both Oracle EBS 12.1.1 and 12.2.2, FND_FILE is declared with AUTHID CURRENT_USER and is classified as a public API (API classification OTHER), indicating broad, supported use across the application. It supports a maximum buffer line size of 32 KB, which is a critical constraint for developers writing large record sets. The package is declared constant-valued: LOG (1) and OUTPUT (2) identify the target file for every write operation, and the package defines the UTL_FILE_ERROR exception mapped to Oracle error -20100 for error handling.

Key Procedures and Functions

The documented API surface comprises eight procedures and functions:

• PUT — Writes text to the specified file (log or output) without appending any new line character. Used for building lines incrementally.
• PUT_LINE — Writes text to the specified file followed by a new line character; the most commonly used routine for emitting complete lines.
• NEW_LINE — Writes line terminators (new line characters) to a file, with a line count parameter defaulting to one, to produce blank lines.
• PUT_NAMES — Sets the temporary log filename, output filename, and temporary directory to user-specified values.
• RELEASE_NAMES — Releases the temporary name assignments established by PUT_NAMES, restoring default behavior.
• GET_NAMES — Retrieves the current log and output filenames and directory in use.
• CLOSE — Closes the log and/or output file handles.
• IS_OPEN — Reports whether the log or output file is currently open; relevant to the "is_open" search because it allows callers to verify file state before writing or closing.

Tables Accessed

FND_FILE operates against a small set of documented objects accessed through APPS synonyms:

• FND_TEMP_FILES / FND_TEMP_FILES_S — Store temporary file name and directory registrations used by PUT_NAMES, RELEASE_NAMES, and GET_NAMES.
• DBMS_LOCK — Provides serialization locking around file name allocation.
• DUAL — Used for trivial single-row queries during initialization.
• UTL_FILE / UTL_RAW — The underlying file I/O and raw data handling mechanisms.
• V$PARAMETER — Referenced to determine database environment settings (for example, the UTL_FILE_DIR configuration) that govern permitted file locations.

Usage Notes

FND_FILE is invoked almost universally from concurrent program logic. The standard pattern is to call FND_FILE.PUT_LINE(FND_FILE.LOG, message) for diagnostics and FND_FILE.PUT_LINE(FND_FILE.OUTPUT, text) for report content. In Oracle EBS 12.1.1, output and log are managed by the Concurrent Manager; in 12.2.2 the same API remains valid, with output optionally integrated with the BI Publisher and OAF-based concurrent request viewers. Developers should not hard-code file paths, since PUT_NAMES and RELEASE_NAMES exist precisely to override and restore the temporary naming convention managed by the Concurrent Manager. Because FND_FILE is referenced by over 2,390 other packages, it is a foundational dependency; changes to files it manages should be tested carefully. The IS_OPEN function is useful in defensive coding — for example, before issuing CLOSE or additional writes when a program may have already terminated its file handles.