Search Results fnd_webfile




Overview
Explore in AI Chat

Overview

FND_WEBFILE is a public PL/SQL package owned by the APPS schema and deployed across Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to translate the internal identifiers used by Oracle Concurrent Processing into externally consumable URLs, primarily so that users, forms, and OAM (Oracle Applications Manager) screens can view or download log files, report output files, trace files, and configuration files generated on the application tier. The package abstracts the physical location of files managed by the ICM (Internal Concurrent Manager) and the concurrent managers, presenting a single, stable entry point for constructing file URLs regardless of whether the deployment uses a single node or a multi-node shared file system topology.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking user rather than the definer, and all callers must therefore possess the appropriate grants on the underlying concurrent processing tables. The packaged constants define the enumerated file types that the GET_URL interface accepts, covering process logs, ICM logs, request logs and outputs, request manager logs, forms process logs, and a range of generic file classes including trace, ora, configuration, context, text, binary, and XML output files.

Key Procedures and Functions

The ETRM documentation identifies four documented program units within FND_WEBFILE.

  • GET_URL — The core function of the package. It constructs and returns the URL for a concurrent processing log or output file based on the supplied file type and identifier. The file type argument selects among the packaged constants (process_log, icm_log, request_log, request_out, request_mgr, frd_log, generic_log, generic_trc, generic_ora, generic_cfg, context_file, generic_text, generic_binary, and request_xml_output), each of which maps to a specific physical file class and transfer mode.
  • GET_REQ_LOG_URLS — Returns the log URLs associated with a concurrent request, allowing callers to retrieve multiple log references in a single invocation and thereby avoiding repeated round trips when several logs must be presented together.
  • CREATE_ID — Registers or generates an identifier, typically for a generic file, so that it can subsequently be resolved by GET_URL. This supports scenarios in which a file is not already known to the concurrent processing tables and must be introduced before a URL can be produced.
  • SET_DEBUG — Controls diagnostic behaviour within the package, enabling callers or administrators to switch debug output on or off for troubleshooting URL construction issues.

Tables Accessed

FND_WEBFILE reads from a defined set of Applications Foundation tables through APPS synonyms. FND_CONCURRENT_REQUESTS, FND_CONCURRENT_PROCESSES, FND_CONCURRENT_PROGRAMS, and FND_CONC_PP_ACTIONS supply the request, process, program, and post-processing context needed to locate logs and outputs. FND_CONC_REQ_OUTPUTS and FND_FILE_TEMP identify the stored output and temporary file records. FND_NODES resolves the node on which the concurrent process executed, which is essential for constructing a correct URL in multi-node environments. FND_APPLICATION and FND_APPL_TOPS determine the application and its top-level directory mapping, while FND_OAM_CONTEXT_FILES provides access to the Applications context file referenced by the context_file file type.

Usage Notes

FND_WEBFILE is normally invoked indirectly rather than by end users. The standard Oracle EBS "View Log" and "View Output" actions, the Concurrent Requests form, and the OAM concurrent processing pages all rely on GET_URL to build hyperlinks to the relevant files. The package is referenced by five other packages within the Applications schema, indicating that it serves as a lower-level utility for higher-level diagnostic and file-retrieval APIs. Custom concurrent programs and extensions that need to publish links to log or output files should call GET_URL with the appropriate file type constant, using the documented enumerated constants rather than literal numbers to preserve readability and forward compatibility. Because the package operates under AUTHID CURRENT_USER, custom code executed as a user without direct table privileges may fail; in such cases the call should be routed through the standard concurrent processing interfaces or the caller granted the necessary access.