Results for “update_source_id”

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

Overview

AD_SNAPSHOT_FILES_TEMP is a temporary staging table owned by the APPLSYS schema within the Applications DBA (AD) product module. Its documented purpose is to serve as a transient work area during the update of the Application System snapshot. The Oracle E-Business Suite snapshot mechanism captures the state of application files across the APPL_TOP file system so that patching utilities, the AutoPatch/AD utilities, and file synchronization logic can determine which files have changed, been added, or become inconsistent between successive maintenance cycles. Records are written to AD_SNAPSHOT_FILES_TEMP during the comparison and reconciliation phase and are subsequently merged into or reconciled against the permanent AD_SNAPSHOT_FILES table before being purged.

The ETRM metadata classifies this object heuristically as standalone in Data Vault terms. As a modeling suggestion, this reflects the fact that it functions as a staging or scratch satellite rather than a durable hub or link: it holds descriptive attributes and version references that support a snapshot-delta process, and it is not intended to persist long-term business entities of its own.

Key Information Stored

The table is documented with twelve columns in ETRM 12.2.2. The most significant of these are:

• SNAPSHOT_FILE_ID — The identifier linking each staging row back to its counterpart header record in AD_SNAPSHOT_FILES; this is the primary foreign-key join path.
• FILE_ID — The application file identifier being snapshotted.
• DEST_FILE_ID — The destination file identifier, used where a snapshot row describes a file that is relocated or copied during an APPL_TOP synchronization.
• FILE_VERSION_ID — Reference to AD_FILE_VERSIONS, capturing the version of the file at the point of snapshot.
• APPL_TOP_ID — Reference to AD_APPL_TOPS, identifying which APPL_TOP the file belongs to; essential in multi-node or multi-APPL_TOP environments.
• UPDATE_SOURCE_ID — Identifies the source of the update that produced the row (for example a patch or an AD utility run).
• UPDATE_TYPE — Classifies the nature of the change (new, modified, deleted, or similar).
• INCONSISTENT_FLAG — Flags rows where the on-disk file state does not match the expected snapshot state, driving reconciliation.
• CONTAINING_FILE_ID — Records the parent or containing file (for example an archive or jar) in which the file resides.
• FILE_SIZE — Size of the file, used for delta detection and size-based comparison.
• CHECKSUM — Digest of file contents, the primary mechanism for detecting changes between snapshot generations.
• FILE_TYPE_FLAG — Indicates the file type classification (for example Java, form, report, or executable).

FROM the documented schema, SNAPSHOT_FILE_ID is the surrogate key candidate for this staging table; because the table is transient, business-key uniqueness is maintained instead through the combination of FILE_ID, APPL_TOP_ID, and FILE_VERSION_ID at the point of merge into AD_SNAPSHOT_FILES.

Common Use Cases and Queries

Typical scenarios involve troubleshooting patch failures, diagnosing file-synchronization mismatches, and validating that an APPL_TOP is consistent before or after an upgrade. A representative query identifies inconsistent staging rows for a given APPL_TOP:

• SELECT t.snapshot_file_id, t.file_id, t.update_type, t.file_size, t.checksum FROM applsys.ad_snapshot_files_temp t WHERE t.inconsistent_flag = 'Y' AND t.appl_top_id = :appl_top_id;
• Joining to version and top metadata to trace a file's provenance: SELECT f.file_name, v.version, a.appl_top_name FROM ad_snapshot_files_temp t, ad_file_versions v, ad_appl_tops a WHERE t.file_version_id = v.file_version_id AND t.appl_top_id = a.appl_top_id;
• Aggregate reporting of pending changes by update type, useful before committing a snapshot refresh: SELECT update_type, COUNT(*), SUM(file_size) FROM ad_snapshot_files_temp GROUP BY update_type;

Because contents are transient, any reporting should be scoped to an active snapshot run window; long-running queries against this table while a snapshot update is in progress may observe partial state.

Related Objects

The foreign-key relationships documented in ETRM establish the principal dependencies:

• AD_SNAPSHOT_FILES — Joined via SNAPSHOT_FILE_ID; the permanent snapshot header/detail table into which staging rows are eventually merged.
• AD_FILE_VERSIONS — Joined via FILE_VERSION_ID; supplies version metadata for each snapshotted file.
• AD_APPL_TOPS — Joined via APPL_TOP_ID; defines the application top ownership of each file.
• AD_FILE_SYSTEM and related AD file tables — Provide the file inventory against which snapshot deltas are compared.
• AD_SNAPSHOT — The parent snapshot run entity that gives context to SNAPSHOT_FILE_ID values.
• AD utilities (adpatch, adadmin, adpreclone) — Consume and populate these structures during snapshot creation and refresh operations.