Results for “fnd_temp_file_parameters”

37 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_TEMP_FILE_PARAMETERS is a table owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, its purpose is to serve as a temporary table for secure file upload or download operations. The object holds a VALID status in the data dictionary and is classified as a standalone entity under the heuristic Data Vault model mined from its foreign key structure. In Data Vault terms, this suggests a hub-like or independent structure rather than a link or satellite, since no inbound or outbound FK relationships were identified. Its narrow footprint — only two documented columns — reflects a focused role: persisting transient parameters that accompany a file transfer session initiated through the EBS file management infrastructure.

Key Information Stored

The table exposes an intentionally minimal physical schema, consisting of two documented columns:

  • FILE_ID — The surrogate primary key of the table, enforced by the constraint FND_TEMP_FILE_PARAM_PK. This identifier uniquely represents each temporary file-parameter record and is also the single column of the unique index FND_TEMP_FILE_PARAMETERS_U1, making it the documented business-key candidate as well as the technical key.
  • FILE_PARAMETERS — The payload column that stores the parameter content associated with the file identified by FILE_ID. This is where the secure upload/download context (such as options, flags, or serialized argument data) is persisted for the duration of the transfer operation.

Because FILE_ID serves simultaneously as primary key and unique index, there is a strict one-to-one correspondence between a file identifier and its parameter set. No additional descriptive, audit, or WHO columns are documented for this table, underscoring its nature as short-lived, operational scratch storage rather than a durable business entity.

Common Use Cases and Queries

The table is typically accessed programmatically by concurrent programs, OAF pages, and PL/SQL APIs that perform secure file handling rather than by end-user reporting. Typical scenarios include:

  • Retrieving the parameters held for a specific file before executing an upload or download: SELECT file_id, file_parameters FROM applsys.fnd_temp_file_parameters WHERE file_id = :p_file_id;
  • Diagnosing failed or stalled file transfers by inspecting the most recently created parameter records during a support investigation.
  • Housekeeping and purge routines that delete orphaned or expired temporary entries to prevent unbounded growth of the table.
  • Correlating the file identifier with the associated file entity when tracing a secure transfer end-to-end across FND file-management components.

Given its transient role, direct reporting against this table is uncommon; access is normally mediated by FND file-management APIs that insert, read, and delete rows keyed by FILE_ID.

Related Objects

The heuristic Data Vault classification is standalone, and no foreign key relationships were mined from the documented schema. Consequently, joins to other FND objects are established logically through the shared file identifier rather than through declared referential constraints. Significant related objects include:

  • FND_TEMP_FILE_PARAMETERS_U1 — the unique index on FILE_ID supporting the business-key candidate.
  • FND_TEMP_FILE_PARAM_PK — the primary key constraint on FILE_ID.
  • FND_LOBS / FND_ATTACHED_DOCUMENTS — file-management tables that store the actual file content and attachment metadata referenced by the same file identifiers.
  • FND_FILE — the PL/SQL package providing the runtime API surface for temporary file operations.
  • FND_BLOB — the related API used for handling binary large objects during secure transfers.
  • FND_ATTACHMENT_FUNCTIONS — the attachment utility layer that orchestrates upload and download flows consuming these parameters.

Because the table carries no declared outbound keys, referential integrity with these objects is maintained at the application layer, keyed by the FILE_ID surrogate.