Search Results fnd_temp_files_pk

Overview

FND_TEMP_FILES is a table owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite. Its documented purpose is to store the names of database server PL/SQL temporary files that are available for use by the EBS application tier. In practical terms, this table acts as a registry or catalog of temporary file handles that concurrent programs, PL/SQL procedures, and reporting components can allocate, read, or write during runtime processing.

The object is classified as VALID in ETRM 12.2.2 and is documented with six physical columns. The metadata assigns it a heuristic Data Vault classification of standalone, meaning no foreign key relationships were mined from the constraint structure. From a modeling perspective, this suggests treating FND_TEMP_FILES as an independent reference or registry table rather than a hub, link, or satellite within a Data Vault construct. The primary key FND_TEMP_FILES_PK is defined on the FILENAME column.

Key Information Stored

The documented physical schema for FND_TEMP_FILES in ETRM 12.2.2 contains six columns. The most significant of these are described below:

• FILENAME — The primary key column and the central business identifier. It holds the name of the temporary file registered on the database server. Because FND_TEMP_FILES_PK is defined on this column alone, FILENAME serves as both the surrogate and business key in the documented model; there is no separate synthetic identifier.
• TYPE — Distinguishes the category or purpose of the temporary file, allowing the application to segregate files by functional usage.
• REQUEST_ID — Associates the temporary file with a specific concurrent request, enabling traceability between a running program and the temporary artifacts it produces or consumes.
• SESSION_ID — Ties the file to a particular database session, which is essential for isolating temporary files across concurrent user sessions.
• FSIZE — Records the size of the temporary file, useful for monitoring growth, enforcing limits, and performing clean-up of orphaned or oversized files.
• NODE — Identifies the application tier node on which the temporary file resides, which is critical in multi-node (RAC or multi-middle-tier) deployments where a file is only accessible from a specific host.

Collectively, these attributes allow the EBS runtime to locate, size, scope, and clean up temporary files reliably across nodes and sessions.

Common Use Cases and Queries

The primary operational use case is managing temporary file lifecycle. Administrators query this table to identify files associated with completed concurrent requests that should be purged, or to detect files whose size (FSIZE) has grown unexpectedly. A representative query to find temporary files by request is:

• SELECT filename, type, session_id, fsize, node FROM fnd_temp_files WHERE request_id = :request_id;
• SELECT node, SUM(fsize) total_bytes FROM fnd_temp_files GROUP BY node; — aggregate storage consumption per application tier node.
• SELECT * FROM fnd_temp_files WHERE session_id = :session_id; — locate temporary artifacts for a given session, useful during diagnostics.

Reporting use cases include capacity trending of temporary storage by node and auditing which concurrent requests generate the largest temporary footprint. Because the table is small and registry-like, queries are typically lightweight, but joins to concurrent request tables (via REQUEST_ID) add operational context.

Related Objects

Given the documented heuristic classification as standalone, no foreign key relationships were mined for FND_TEMP_FILES. The following objects are nevertheless logically associated through shared columns, chiefly REQUEST_ID and SESSION_ID:

• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to link temporary files to their originating concurrent program run.
• FND_CONCURRENT_PROGRAMS — provides program definitions for the requests that generate temporary files.
• FND_CONCURRENT_PROCESSES — associates running processes with the sessions that own temporary files.
• FND_SESSIONS — joined via SESSION_ID to resolve session-level context.
• FND_NODES — joined via NODE to resolve which application tier host holds each file.
• FND_FILE — the PL/SQL package (FND_FILE.PUT_LINE, FND_FILE.CLOSE) that manages concurrent program output and temporary file handling.

These objects are the most significant context for interpreting and operating on FND_TEMP_FILES data in an Oracle EBS 12.1.1 or 12.2.2 environment.