Search Results fnd_imp_pscommon




Overview
Explore in AI Chat

Overview

FND_IMP_PSCOMMON is a table owned by the APPLSYS schema within the FND (Application Object Library) product of Oracle E-Business Suite. The table is documented as VALID in both ETRM 12.1.1 and 12.2.2 releases and serves as a staging or infrastructure repository for the Oracle Applications patching and file reconciliation subsystem. Its name identifies it as a common ("PSCOMMON") implementation table ("IMP") under the FND umbrella, and its column set shows that it tracks files delivered by patches, together with the snapshot identifiers and version metadata that drive file-level comparison during patch application or upgrade activities.

From a Data Vault modeling perspective, the mined FK structure classifies FND_IMP_PSCOMMON as a standalone object — no downstream tables reference it. Its single outgoing foreign key to AHL_SNAPSHOTS suggests it could be modeled as a satellite attached to the AHL_SNAPSHOTS hub, carrying descriptive patch-file attributes rather than acting as an independent hub or a link between multiple hubs. This classification is a heuristic suggestion only; the table is a standard relational structure in the EBS schema.

Key Information Stored

The documented physical schema of FND_IMP_PSCOMMON contains nine columns. The most significant are:

  • SNAPSHOT_ID — The foreign key to AHL_SNAPSHOTS. It ties each patch-file record to a specific snapshot taken by the AHL (Oracle Applications Online Help / patch snapshot) subsystem.
  • BUG_NO — The bug or patch identifier associated with the delivered file, enabling traceability back to the originating patch.
  • PATCH_ID — An internal patch reference used by AutoPatch and related utilities to link file entries to patch drivers.
  • APP_SHORT_NAME — The application short name (e.g., FND, APPLSYS-adjacent modules) that owns the file, used for filtering and routing.
  • DIRECTORY — The target file-system directory where the delivered file resides or is expected to reside.
  • FILENAME — The actual delivered file name; combined with DIRECTORY, it forms the logical business key of a file entry.
  • NEW_VERSION — The patch-delivered version number of the file after application.
  • OLD_VERSION — The pre-patch on-disk version of the file, retained for rollback and comparison.
  • IS_FLAGGED_FILE — A flag indicating whether the file has been marked for special handling (for example, manual merge, review, or exclusion).

The surrogate primary key is not explicitly documented in the provided metadata, but the FK relationship to AHL_SNAPSHOTS plus the combination of SNAPSHOT_ID, DIRECTORY, and FILENAME strongly suggests the uniqueness is enforced over the snapshot/file pair rather than a single surrogate column. Bug number and patch ID are business-key candidates for tracing.

Common Use Cases and Queries

Typical usage centers on patch-file reconciliation during an upgrade or patch cycle. A DBA or EBS technical consultant may query FND_IMP_PSCOMMON to list all files delivered by a specific patch that are flagged for manual intervention:

  • Flagged-file report: SELECT APP_SHORT_NAME, DIRECTORY, FILENAME, OLD_VERSION, NEW_VERSION FROM FND_IMP_PSCOMMON WHERE IS_FLAGGED_FILE = 'Y' AND BUG_NO = :bug_no;
  • Snapshot traceability: SELECT p.DIRECTORY, p.FILENAME, s.* FROM FND_IMP_PSCOMMON p, AHL_SNAPSHOTS s WHERE p.SNAPSHOT_ID = s.SNAPSHOT_ID AND p.PATCH_ID = :patch_id;
  • Version drift analysis: Comparing OLD_VERSION against NEW_VERSION to identify files where the patch overwrites a custom or previously patched version.
  • Rollback preparation: Extracting OLD_VERSION details per file prior to applying a patch, so the previous file state can be restored if required.

Related Objects

The principal related objects are:

  • AHL_SNAPSHOTS — Referenced through FND_IMP_PSCOMMON.SNAPSHOT_ID. This is the documented FK target and the anchor of the snapshot/file relationship.
  • FND_IMP_PSFILE — Closely associated sibling implementation table in the same patching subsystem, typically holding per-file execution or processing status.
  • FND_IMP_PSFILEHEAD or equivalent header tables — Provide the patch/run header context for the file rows stored in FND_IMP_PSCOMMON.
  • AD_PATCH_RUN_BUGS / AD_BUGS — Patch-layer tables that resolve BUG_NO and PATCH_ID into the AutoPatch tracking model.
  • AHL_SNAPSHOT_DETAILS — Detail table under AHL_SNAPSHOTS that stores individual snapshot artifacts, useful for deeper snapshot-to-file joins.

No downstream tables declare a foreign key into FND_IMP_PSCOMMON in the mined relationship data, confirming its role as a descriptive satellite rather than a referenced parent.