Search Results fnd_file_temp




Overview
Explore in AI Chat

Overview

FND_FILE_TEMP is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is a transient staging structure used by the Concurrent Manager's file transfer and report distribution infrastructure. The table tracks temporary files generated during concurrent program execution — typically log and output files, spooled report artifacts, and files staged for delivery to a destination node or the Web-based Oracle Forms/BI Publisher output directories. Because concurrent programs frequently run across multiple middle-tier nodes, FND_FILE_TEMP records the location, size, encoding, and expiry metadata required to move or purge these artifacts reliably.

The documented ETRM metadata classifies this object heuristically as standalone under a Data Vault model — meaning it does not carry a natural foreign-key relationship to other Vault hubs and would most plausibly be modeled as an independent hub (or a satellite of the concurrent request hub) rather than as a link table. In practice this reflects that the table is a self-contained file registry keyed solely by its own surrogate identifier.

Key Information Stored

The primary key is FND_FILE_TEMP_PK, defined on the single column FILE_ID, a system-generated surrogate identifier assigned to each temporary file row. The remaining columns describe the file, its origin, and its intended destination:

Common Use Cases and Queries

DBAs and EBS administrators query FND_FILE_TEMP to diagnose concurrent program output problems, trace lost report files, and audit disk consumption by request. A typical diagnostic query joins the staged file rows to their originating concurrent request:

SELECT f.FILE_ID, f.FILENAME, f.NODE_NAME,
       f.DESTINATION_NODE, f.FILE_SIZE, f.EXPIRES,
       r.CONCURRENT_PROGRAM_ID, r.PHASE_CODE
FROM   APPLSYS.FND_FILE_TEMP f,
       APPLSYS.FND_CONCURRENT_REQUESTS r
WHERE  f.REQUEST_ID = r.REQUEST_ID
AND    f.EXPIRES < SYSDATE;

Common reporting scenarios include identifying expired files still occupying space, listing oversized outputs by concurrent program, and verifying that NLS code-set conversions match the target node's character set. Automated purge scripts frequently delete rows where EXPIRES has passed and the corresponding physical file has already been removed from disk.

Related Objects

The metadata documents FND_FILE_TEMP as standalone at the FK level, so relationships are largely logical rather than enforced:

  • FND_CONCURRENT_REQUESTS — joined via REQUEST_ID; the primary parent of each staged file record.
  • FND_CONCURRENT_PROGRAMS — resolves the producing program through the request.
  • FND_CP_GSM_IPC — the Concurrent Manager IPC table used during file handoff.
  • FND_NODES — validates NODE_NAME and DESTINATION_NODE entries against registered application-tier nodes.
  • FND_CONCURRENT_WORKER_REQUESTS — correlates worker assignment with staged outputs.
  • FND_FILE — the runtime PL/SQL package that writes and reads files tracked here.
  • FND_CP_LOGS / FND_CP_OUTPUTS patterns in R12.2.x — the request-log/output retrieval interfaces that consume these staged artifacts.