Results for “app_short_name”

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

Overview

FND_IMP_PSNEW is a table owned by the APPLSYS schema within the FND (Application Object Library) product in Oracle E-Business Suite. It is a standalone, internally oriented data object that supports Oracle's patch and file-version tracking infrastructure, most likely the mechanism Oracle Applications uses to stage information about files delivered or replaced during patching operations (for example, during the application of an Oracle patch through AD utilities). The table references AHL_SNAPSHOTS through SNAPSHOT_ID, which strongly suggests the rows are tied to a captured configuration snapshot. Such snapshots are used by Oracle's patch analysis and configuration-management tooling to reconcile the state of delivered files with the versions recorded in a patch shipment.

The metadata classifies FND_IMP_PSNEW using a heuristic Data Vault model, and the result is standalone. In modeling terms, this suggests FND_IMP_PSNEW behaves neither as a hub (no absorbed business key from an upstream source), nor as a link (no multiple foreign-key relationships defining a many-to-many association), nor as a classic satellite with a single parent. Its single foreign key (SNAPSHOT_ID to AHL_SNAPSHOTS) points to it as auxiliary or staging data, likely populated only transiently during patch processing.

Key Information Stored

The documented physical schema exposes eight columns in ETRM 12.2.2. The essential columns are:

• BUG_NO — identifies the bug or patch record to which the file change is associated, effectively acting as a business reference to the patch delivery.
• SNAPSHOT_ID — the foreign key to AHL_SNAPSHOTS, linking this record to a captured configuration or implementation snapshot.
• APP_SHORT_NAME — the application short name (e.g., FND, INV) of the file's owning product, used to disambiguate filenames across applications.
• DIRECTORY — the $APPL_TOP-relative directory path in which the file resides.
• FILENAME — the physical filename delivered or replaced by the patch.
• NEW_VERSION — the version of the file introduced by the patch, enabling before/after reconciliation.
• IS_FLAGGED_FILE — a flag indicating whether the file was identified for special handling by the patching tool.
• PATCH_ID — the patch identifier under which the file change was applied, supporting traceability back to the patch shipment.

No surrogate primary key column is documented in the ETRM metadata, nor is a unique index listed. The combination of SNAPSHOT_ID, APP_SHORT_NAME, DIRECTORY, and FILENAME is the most likely natural/business key candidate, while PATCH_ID and BUG_NO function as external references to Oracle's patch management records.

Common Use Cases and Queries

FND_IMP_PSNEW is rarely queried directly by end users; it is typically accessed by DBAs and technical consultants investigating patch behavior. Typical queries include:

• Identifying which files a given patch delivered: SELECT app_short_name, directory, filename, new_version FROM fnd_imp_psnew WHERE patch_id = :patch_id;
• Finding all patch activity against a snapshot: SELECT bug_no, patch_id, filename FROM fnd_imp_psnew WHERE snapshot_id = :snapshot_id;
• Locating flagged files that require manual attention: SELECT * FROM fnd_imp_psnew WHERE is_flagged_file = 'Y';
• Auditing version drift between delivered and installed files using NEW_VERSION.

Reporting use is mostly operational (patch inventory, file reconciliation) rather than analytical. Because the table is standalone and transient, snapshot-like volume is expected to be small and lifecycle-bound to the patch operation.

Related Objects

• AHL_SNAPSHOTS — referenced via FND_IMP_PSNEW.SNAPSHOT_ID; the parent snapshot defining the configuration context.
• FND_PATCH_HISTORY / AD_PATCH_RUNS — patch execution history typically correlated with PATCH_ID.
• FND_BUG_PATCH_MAP — mapping between bugs (BUG_NO) and patches, useful for reconciliation.
• FND_APPLICATION — to resolve APP_SHORT_NAME into a full application name.
• AD_FILE_VERSIONS / FND_FILE_VERSIONS — related file-version tracking tables used by AD utilities.
• FND_IMP_PS — a closely related staging table with an analogous name, often paired with FND_IMP_PSNEW in patch internals.

Because this is a proprietary APPLSYS object, direct DML should be avoided. Any inspection should be read-only and limited to technical diagnostics or patch-audit reporting.