Search Results dep_app_short_name




Overview
Explore in AI Chat

Overview

APPLSYS.FND_IMP_SFILEDEP is a VALID table in the APPLSYS schema, registered in FND Design Data as FND.FND_IMP_SFILEDEP and stored in the APPS_TS_TX_DATA tablespace with PCT Free 10. It stores dependency relationships between files captured in an AHL snapshot. Each row records a primary file (identified by application, directory, and filename) together with the file it depends upon (identified by its own application, directory, and filename). The IMP component of the name indicates its association with the import and file-processing infrastructure, while SFILEDEP denotes the snapshot file dependency construct.

Within Oracle EBS 12.1.1 and 12.2.2, the table supports snapshot-driven processing where a set of files must be resolved in dependency order — for example, loading objects whose definitions rely on other objects already present in the snapshot. The heuristic Data Vault classification mined from the FK structure is standalone, meaning the table neither functions as a hub nor as a link in a strictly conformed model; it is best treated as an independent reference table or satellite-style record set keyed by its snapshot and file identity rather than as a component of a shared business-key chain.

Key Information Stored

The table exposes seven documented columns, summarized below according to their functional role rather than as a full enumeration.

  • SNAPSHOT_ID (NUMBER, mandatory) — the surrogate identifier linking the row to a specific snapshot in AHL_SNAPSHOTS. It is the participating column in the documented foreign key and is present as the leading column in both non-unique indexes.
  • APP_SHORT_NAME (VARCHAR2 50) — the EBS application short name (for example, an application code) of the owning file.
  • DIRECTORY (VARCHAR2 256) — the directory path of the owning file within the snapshot.
  • FILENAME (VARCHAR2 128) — the name of the owning file.
  • DEP_APP_SHORT_NAME (VARCHAR2 50) — the application short name of the dependent file; this is the column most directly associated with the user search term dep_app_short_name.
  • DEP_DIRECTORY (VARCHAR2 256) — the directory path of the dependent file.
  • DEP_FILENAME (VARCHAR2 128) — the name of the dependent file.

No surrogate primary key is documented; uniqueness is enforced only through convention. The documented business-key candidates are the composite tuples of the two non-unique indexes: FND_IMP_SFILEDEP_N1 on (SNAPSHOT_ID, DEP_APP_SHORT_NAME, DEP_DIRECTORY, DEP_FILENAME) and FND_IMP_SFILEDEP_N2 on (SNAPSHOT_ID, APP_SHORT_NAME, DIRECTORY, FILENAME). The first index resolves dependents from a snapshot; the second resolves owners. Both reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

The principal use case is resolution of file load ordering. Before processing a snapshot, the dependency chain is queried so that dependent files are handled only after their owners. A typical retrieval pattern mirrors the documented query text:

  • List all file 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 = :snapshot_id;
  • Find which files depend on a given application's file: filter on DEP_APP_SHORT_NAME and the associated directory and filename columns.
  • Find the owner of a dependent file: filter on APP_SHORT_NAME, DIRECTORY, and FILENAME, exploiting index N2.
  • Detect dangling dependencies within a snapshot by joining owner and dependent tuples and identifying entries with no matching owner row.

Reporting usage is generally inventory-oriented: counts of dependency edges per snapshot, per application, or per directory, used to size and sequence import jobs.

Related Objects

  • APPLSYS.AHL_SNAPSHOTS — referenced by the documented foreign key FND_IMP_SFILEDEP.SNAPSHOT_ID → AHL_SNAPSHOTS; the authoritative source of snapshot context.
  • APPS.FND_IMP_SFILEDEP — the APPS-synonym view referenced by the dependency listing, providing the runtime access path for the table.
  • APPLSYS.FND_IMP_SFILEDEP_N1 and APPLSYS.FND_IMP_SFILEDEP_N2 — the two non-unique indexes in APPS_TS_TX_IDX that support dependency and ownership lookups.
  • FND_IMP_SFILE — the companion snapshot file table, conventionally joined on SNAPSHOT_ID, APP_SHORT_NAME, DIRECTORY, and FILENAME to enrich dependency rows with file attributes.
  • The AHL snapshot family (AHL_SNAPSHOTS and its related snapshot tables) — supplies the header and scope against which file dependencies are evaluated.

The table itself references no other database object beyond the snapshot foreign key, and is referenced externally by the APPS synonym layer described above.