Search Results fnd_imp_sfiledep




Overview
Explore in AI Chat

Overview

FND_IMP_SFILEDEP is a table in the APPLSYS schema of the Oracle E-Business Suite Application Object Library (FND). It is used by the Oracle EBS interface/import infrastructure to track file dependency relationships between staged files and dependent files associated with a snapshot. The table records the mapping between a "source" file (directory and filename combination) and a dependent file (a second directory and filename combination), scoped to an application short name and a snapshot identifier. This enables the import framework to determine ordering and prerequisite relationships when processing multiple files as part of a bulk import or data load operation.

From a Data Vault modeling perspective, the metadata classifies FND_IMP_SFILEDEP as standalone, meaning it carries no enforced dependencies on other link or hub structures within the modeling heuristic. In practice, however, the presence of a foreign key on SNAPSHOT_ID referencing AHL_SNAPSHOTS indicates that the table functions as a dependent or satellite-like structure relative to the snapshot entity, even though the heuristic did not classify it as such.

Key Information Stored

The table contains seven documented columns. The most significant are:

  • SNAPSHOT_ID — The foreign key linking each dependency record to a snapshot in AHL_SNAPSHOTS. This identifies the import/interface snapshot context under which the file dependency was captured.
  • APP_SHORT_NAME — The application short name (e.g., INV, AP, AR) to which the source file belongs.
  • DIRECTORY — The directory path or logical directory reference for the source file.
  • FILENAME — The name of the source file whose dependency is being declared.
  • DEP_APP_SHORT_NAME — The application short name of the dependent file. Together with DIRECTORY and FILENAME, this defines the second file in the dependency pair.
  • DEP_DIRECTORY — The directory reference for the dependent file.
  • DEP_FILENAME — The name of the dependent file that must be processed in relation to the source file.

The surrogate/business key for this table is not explicitly documented in the provided metadata. Based on the column composition, the logical business key is likely the composite of SNAPSHOT_ID, APP_SHORT_NAME, DIRECTORY, FILENAME, DEP_APP_SHORT_NAME, DEP_DIRECTORY, and DEP_FILENAME, which uniquely identifies a file dependency pair within a snapshot. No unique index columns are documented beyond this implied composite.

Common Use Cases and Queries

Typical use cases include diagnosing import sequencing failures, auditing which files were staged with dependencies for a given snapshot, and reporting on dependency chains across applications. A common SQL pattern retrieves all dependencies for a snapshot:

  • SELECT snapshot_id, app_short_name, directory, filename, dep_app_short_name, dep_directory, dep_filename FROM applsys.fnd_imp_sfiledep WHERE snapshot_id = :p_snapshot_id;
  • Finding all dependents of a specific source file: SELECT dep_filename FROM applsys.fnd_imp_sfiledep WHERE app_short_name = :app AND filename = :fname;
  • Joining to AHL_SNAPSHOTS to obtain snapshot metadata: SELECT s.*, d.* FROM applsys.fnd_imp_sfiledep d, ahl_snapshots s WHERE d.snapshot_id = s.snapshot_id;

These queries support import validation, dependency resolution, and troubleshooting of file-based concurrent program loads.

Related Objects

The primary documented relationship is the foreign key from FND_IMP_SFILEDEP.SNAPSHOT_ID to AHL_SNAPSHOTS. Other significant related objects in the FND import framework include FND_IMP_SFILE (staged file definitions), FND_IMP_SFILECOL (file column definitions), and the concurrent program infrastructure tables that orchestrate import processing. Additionally, application short name references connect indirectly to FND_APPLICATION, while directory references tie to FND_IMP_SFILE_DIRECTORY or equivalent logical directory definitions. These relationships make FND_IMP_SFILEDEP an integral part of the file-based staging and import subsystem.