Search Results fnd_deferred_load_files_pk

Overview

The FND_DEFERRED_LOAD_FILES table is a core repository within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as a metadata registry for files designated for deferred or batch loading processes. This table is integral to the architecture of data import utilities, such as FNDLOAD and related concurrent programs, where it tracks the source files, their associated applications, and the target programs responsible for their processing. Its primary role is to manage and coordinate the execution of these deferred data loads, ensuring that the correct files are processed by the appropriate application modules in a controlled manner.

Key Information Stored

The table's structure is defined by a composite primary key, which underscores the uniqueness of each deferred load file entry. The key columns, as documented, are:

• FILE_PRODUCT: Identifies the Oracle EBS product or module (e.g., FND, HR, PO) that owns or is the primary consumer of the data file.
• FILE_PATH: Stores the directory or logical path where the source data file is located or expected to be found by the loading program.
• FILE_NAME: Specifies the name of the actual data file to be loaded.
• PROGRAM_NAME: The name of the concurrent or batch program (e.g., a specific FNDLOAD command or custom executable) responsible for processing the file.
• PROGRAM_APP: The application short name associated with the loading program, linking it to its parent application in FND_APPLICATION.

Together, these columns provide a complete map from a physical data file to the software component that will ingest it.

Common Use Cases and Queries

A primary use case is auditing and managing the queue of pending data loads. System administrators can query this table to review all registered load files, troubleshoot failed processes by verifying file metadata, or generate deployment scripts. A typical query to list all deferred files for a specific product would be:

SELECT file_path, file_name, program_name, program_app
FROM fnd_deferred_load_files
WHERE file_product = 'FND';

Another common scenario involves verifying the existence of a registration for a specific data migration or patch file before execution. A join with FND_CONCURRENT_PROGRAMS may be used to get more details on the loading program itself, though this relationship is not explicitly defined in the provided metadata.

Related Objects

The provided metadata specifies the primary key constraint FND_DEFERRED_LOAD_FILES_PK on the columns FILE_PRODUCT, FILE_PATH, and FILE_NAME. This indicates the table is designed to be referenced by other objects via foreign keys, though specific related tables are not listed. In a typical EBS environment, this table is logically related to:

• FND_APPLICATION: Through the FILE_PRODUCT and PROGRAM_APP columns, which likely correspond to the APPLICATION_SHORT_NAME.
• FND_CONCURRENT_PROGRAMS: The PROGRAM_NAME and PROGRAM_APP columns may relate to CONCURRENT_PROGRAM_NAME and APPLICATION_ID, linking to the executable scheduled to perform the load.

It is a foundational table for the deferred loading subsystem, and any custom or standard APIs that schedule or monitor batch data loads would reference it.