Search Results fnd_imp_affectedfiles




Overview
Explore in AI Chat

Overview

FND_IMP_AFFECTEDFILES is a standalone table owned by the APPLSYS schema within the FND – Application Object Library product of Oracle E-Business Suite. It is part of the Oracle EBS patch and snapshot infrastructure that tracks the relationships between applied patches, snapshots, and the files or objects affected by those operations. In releases 12.1.1 and 12.2.2, this table serves as a repository for recording which files and database objects are impacted when a patch is applied or when a snapshot is captured, enabling the adoption and patching utilities to determine dependencies and rollback requirements.

From a data modeling perspective, the mined foreign key structure classifies this table as standalone (a hub-style classification). The only documented foreign key reference is the SNAPSHOT_ID column pointing to AHL_SNAPSHOTS. Because no other tables reference FND_IMP_AFFECTEDFILES through foreign keys, and it does not function as a link table bridging two distinct hubs, the heuristic modeling suggestion is that it behaves as a standalone hub-like entity rather than a link or satellite — its rows are independently keyed and self-contained.

Key Information Stored

The documented physical schema for FND_IMP_AFFECTEDFILES in ETRM 12.2.2 contains 13 columns. The most significant of these are:

  • BUG_NO — the bug or patch identifier associated with the affected file, serving as a primary business-key candidate.
  • PATCH_ID — the identifier of the patch context under which the affected file was recorded.
  • SNAPSHOT_ID — the foreign key to AHL_SNAPSHOTS, tying the affected file record to a snapshot.
  • DEP_APP_SHORT_NAME — the application short name of the dependent (source) file.
  • DEP_DIRECTORY — the directory path of the dependent file.
  • DEP_FILENAME — the name of the dependent file.
  • PATCHED_APP_SHORT_NAME — the application short name of the patched file.
  • PATCHED_DIRECTORY — the directory of the patched file.
  • PATCHED_FILENAME — the filename of the patched file.
  • TYPEID — a type classifier for the affected file record.
  • ACTION_REQUIRED — indicates what remedial action, if any, is needed.
  • OBJECTS_AFFECTED — describes the objects affected by the patch or snapshot.
  • OBJECT_TYPE — the category or type of the affected object.

The combination of BUG_NO, SNAPSHOT_ID, and PATCH_ID forms the natural composite business key, while SNAPSHOT_ID is the sole documented foreign key. No explicit surrogate primary key column is named in the metadata.

Common Use Cases and Queries

This table is primarily used by DBAs and patching administrators to audit which files and objects are impacted by patches or snapshots. Typical reporting includes identifying all files affected by a specific bug, or finding all snapshots that touched a given file.

  • List affected files for a given bug: SELECT * FROM APPS.FND_IMP_AFFECTEDFILES WHERE BUG_NO = :bug_no;
  • Join to snapshots: SELECT a.* , s.* FROM APPLSYS.FND_IMP_AFFECTEDFILES a, AHL_SNAPSHOTS s WHERE a.SNAPSHOT_ID = s.SNAPSHOT_ID;
  • Find files requiring action: SELECT DEP_FILENAME, PATCHED_FILENAME, ACTION_REQUIRED FROM APPLSYS.FND_IMP_AFFECTEDFILES WHERE ACTION_REQUIRED IS NOT NULL;

Related Objects

  • AHL_SNAPSHOTS — referenced via SNAPSHOT_ID; the primary documented join.
  • FND_IMP_PATCHES — related patching metadata keyed by PATCH_ID.
  • FND_IMP_BUGS — bug tracking metadata keyed by BUG_NO.
  • AD_PATCH_RUN_BUGS — patch run history in AD utilities.
  • AD_PATCH_DRIVERS — driver file metadata for applied patches.