Results for “ad_file_versions_u1”

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

Overview

AD_FILE_VERSIONS is a core repository table in the Applications DBA (AD) product of Oracle E-Business Suite, owned by the APPLSYS schema. It functions as the file versions repository, storing discrete versions of Oracle Applications files as they are delivered, patched, and tracked across the EBS file system. In EBS 12.1.1 and 12.2.2, the AD utilities—particularly AutoPatch (adpatch) and the file system comparison and snapshot processes—rely on this table to record which version of a given file exists at a point in time and where that version originated.

Under a heuristic Data Vault classification inferred from its foreign key structure, AD_FILE_VERSIONS is best modeled as a hub. It anchors the identity of each file version through its surrogate primary key, FILE_VERSION_ID, and is referenced by numerous dependent tables that capture check results, patch run actions, and snapshots. This hub-like position reflects its role as the stable reference point from which transactional and audit-oriented satellites are hung.

Key Information Stored

The table contains 18 documented columns. The most significant are the following:

• FILE_VERSION_ID — Surrogate primary key (AD_FILE_VERSIONS_PK) uniquely identifying each version record. This is the value propagated to all dependent tables.
• FILE_ID — Foreign key to AD_FILES, tying the version to its parent file identity. This is the first column of the business-key unique index AD_FILE_VERSIONS_U1 (FILE_ID, VERSION, TRANSLATION_LEVEL).
• VERSION — The version label of the file, forming the second business-key column and distinguishing successive deliveries of the same file.
• TRANSLATION_LEVEL — The translation level associated with the version, completing the business-key uniqueness (AD_FILE_VERSIONS_U1). This supports the multilingual nature of EBS files.
• VERSION_SEGMENT1 through VERSION_SEGMENT10 — Ten decomposed version segments, enabling structured comparison and ordering of file versions where the version string is parsed into component parts. These support AD's internal version-matching logic.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns recording who created or last modified the version row and when, essential for change tracking and troubleshooting.

The unique indexes AD_FILE_VERSIONS_U1 (FILE_VERSION_ID) and AD_FILE_VERSIONS_U2 (FILE_ID, VERSION, TRANSLATION_LEVEL) identify the surrogate versus business-key candidates respectively.

Common Use Cases and Queries

Administrators and developers use AD_FILE_VERSIONS to determine which file version is currently applied, to reconcile patch history, and to diagnose version mismatches flagged by adpatch or adchkcf. A typical query joins to AD_FILES to retrieve the file's name and application context:

• Listing all versions of a given file: SELECT v.FILE_VERSION_ID, v.VERSION, v.TRANSLATION_LEVEL FROM AD_FILE_VERSIONS v WHERE v.FILE_ID = :file_id ORDER BY v.CREATION_DATE DESC;
• Locating versions referenced during a specific patch run by joining to AD_PATCH_RUN_BUG_ACTIONS via PATCH_FILE_VERSION_ID, ONSITE_FILE_VERSION_ID, or ONSITE_PKG_VERSION_IN_DB_ID.
• Identifying files checked by the file system checker through AD_CHECK_FILES.FILE_VERSION_ID.
• Auditing snapshot contents via AD_SNAPSHOT_FILES.FILE_VERSION_ID.
• Reporting on version provenance and creation dates for change-control and compliance purposes.

Related Objects

AD_FILE_VERSIONS participates in a well-defined relationship network with the following significant objects:

• AD_FILES — Parent file identity table; joined on AD_FILE_VERSIONS.FILE_ID = AD_FILES.FILE_ID.
• AD_CHECK_FILES — References the version through FILE_VERSION_ID, recording file-system check outcomes.
• AD_PATCH_RUN_BUG_ACTIONS — References the table through three columns: PATCH_FILE_VERSION_ID, ONSITE_FILE_VERSION_ID, and ONSITE_PKG_VERSION_IN_DB_ID, linking patch actions to the versions they applied.
• AD_SNAPSHOT_FILES — References FILE_VERSION_ID, capturing versions included in application snapshots.
• AD_CHECK_FILE_TEMP, AD_SNAPSHOT_FILES_TEMP, and AD_PATCH_HIST_SNAPS_TEMP — Temporary staging tables that reference FILE_VERSION_ID during processing.

Together these relationships make AD_FILE_VERSIONS the authoritative version hub underpinning EBS file management, patching, checking, and snapshot operations.