Results for “ad_files”

50+ results




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

Overview

AD_FILES is the central files repository for Oracle Applications, residing in the APPLSYS schema and belonging to the AD (Applications DBA) product group. It catalogs files known to the EBS file system and patch infrastructure, providing a single registration point for objects referenced by patching, checking, snapshot, and versioning operations. Within the EBS 12.1.1 and 12.2.2 environments, this table is a foundational metadata store used by AD utilities such as AutoPatch and AD CheckFile, which rely on it to track file identity, location, and revision across the application tier.

Under the heuristic Data Vault classification derived from its foreign key structure, AD_FILES functions as a hub. It supplies the durable business key (FILE_ID) to which multiple dependent tables attach as satellites or links, such as AD_FILE_VERSIONS, AD_CHECK_FILES, and AD_SNAPSHOT_FILES. This modeling suggestion reflects the table's role as a stable anchor rather than a transactional or descriptive record.

Key Information Stored

AD_FILES carries ten documented columns. The primary key is the surrogate identifier FILE_ID, enforced by the unique index AD_FILES_PK. Business-key uniqueness is enforced by AD_FILES_U2 across the combination of FILENAME, SUBDIR, and APP_SHORT_NAME, which together describe the physical location and logical application context of each file.

  • FILE_ID — Surrogate primary key; the anchor referenced by all dependent FK tables.
  • APP_SHORT_NAME — Short name of the owning Oracle application (for example, FND, GL, or AD).
  • SUBDIR — Directory path relative to the application base, identifying file placement.
  • FILENAME — Name of the registered file, used with SUBDIR and APP_SHORT_NAME as the business key.
  • CREATION_DATE / CREATED_BY — Audit columns capturing who registered the file and when.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — Audit columns reflecting the most recent modification.
  • IS_FLAGGED_FILE — Indicator that the file has been flagged for special attention.
  • FLAGGED_FILE_COMMENTS — Free-text remarks associated with a flagged file.

Absent from the documented column set are explicit version, size, or checksum attributes; those are captured in dependent tables such as AD_FILE_VERSIONS.

Common Use Cases and Queries

Administrators and developers query AD_FILES to resolve a file path to its internal identifier, to enumerate files for a given application, or to locate files flagged during patching. A typical lookup by business key is:

  • SELECT file_id, app_short_name, subdir, filename FROM applsys.ad_files WHERE filename = :p_name AND subdir = :p_subdir;
  • SELECT file_id, filename, subdir FROM applsys.ad_files WHERE is_flagged_file = 'Y'; — list flagged files and their comments.
  • SELECT f.file_id, f.filename, v.version FROM applsys.ad_files f JOIN applsys.ad_file_versions v ON v.file_id = f.file_id WHERE f.app_short_name = :app; — join to version history.

Reporting use cases include auditing registered files per application, reconciling snapshot contents, and tracing patch actions back to the files they touched.

Related Objects

Several AD tables depend on AD_FILES through foreign keys, confirming its hub position:

  • AD_FILE_VERSIONS — joins on FILE_ID; maintains revision history for each registered file.
  • AD_CHECK_FILES — joins on FILE_ID; supports AutoPatch check-file validation.
  • AD_SNAPSHOT_FILES — joins on FILE_ID and CONTAINING_FILE_ID; links snapshot contents, including archive containment.
  • AD_PATCH_COMMON_ACTIONS — joins on LOADER_DATA_FILE_ID; associates patch actions with their data files.
  • AD_PATCH_RUN_BUG_ACTIONS — joins on FILE_ID; ties patch run actions to specific files.

Together these relationships establish AD_FILES as the authoritative registration point for Oracle Applications file metadata across the AD product suite.