Search Results fnd_imp_psmaster2




Overview
Explore in AI Chat

Overview

FND_IMP_PSMASTER2 is a table owned by the APPLSYS schema within the FND – Application Object Library product of Oracle E-Business Suite. It is documented in the ETRM 12.2.2 repository as a VALID database object. The table serves as a control and staging repository for patch-file impact tracking. Its name and column set indicate that it stores metadata regarding file-level changes introduced by patches, including the version transitions applied to individual files within a patch (for example, moving from an old version to a new version), the affected file type, and the associated patch identifier. In the context of EBS 12.1.1 and 12.2.2, this object supports the AD (Applications DBA) patching and file-management infrastructure by capturing the master list of files affected by a given patch or snapshot.

From a heuristic Data Vault modeling perspective, and based on the documented foreign-key structure, the table is classified as standalone rather than a hub, link, or satellite. This suggests it holds its own descriptive and transactional content without participating in a broader hub-and-link constellation; it may be treated as an independent descriptive entity for file-patch impact.

Key Information Stored

The documented physical schema contains 15 columns. The most operationally significant include:

  • SNAPSHOT_ID — the foreign key linking each row to AHL_SNAPSHOTS. This associates the file-impact record with a specific snapshot used during patch application or file comparison.
  • BUG_NO — the bug or issue number that the affected file addresses, tying the file change to a tracked defect.
  • PATCH_ID — identifies the patch in which the file impact originated.
  • APP_SHORT_NAME — the application short name to which the file belongs.
  • DIRECTORY and FILENAME — the physical path elements that together locate the affected file.
  • TYPEID and FILE_TYPE — classification values describing the file category.
  • OLD_VERSION and NEW_VERSION — the version values before and after the patch, enabling version-transition auditing.
  • FILES_AFFECTED and TYPE_AFFECTED — flags or descriptors indicating which files and file types are impacted.
  • TRANS_NAME — the translation or transformation name associated with the file change.
  • IS_FLAGGED_FILE and BRANCH_TYPE — indicators used to mark files of special interest or specify the branch classification.

No explicit surrogate primary key or unique business-key index is documented in the supplied metadata. In practice, the combination of SNAPSHOT_ID, PATCH_ID, DIRECTORY, and FILENAME functions as the probable business-key candidate, while SNAPSHOT_ID serves as the documented foreign-key reference.

Common Use Cases and Queries

Typical usage centers on patch impact analysis and file-version reconciliation:

  • Identifying all files affected by a given patch: SELECT DIRECTORY, FILENAME, OLD_VERSION, NEW_VERSION FROM FND_IMP_PSMASTER2 WHERE PATCH_ID = :patch_id;
  • Determining which files are tied to a specific bug: SELECT * FROM FND_IMP_PSMASTER2 WHERE BUG_NO = :bug_no;
  • Joining to the snapshot table to reconcile snapshot scope: SELECT m.FILENAME, s.SNAPSHOT_ID FROM FND_IMP_PSMASTER2 m JOIN AHL_SNAPSHOTS s ON m.SNAPSHOT_ID = s.SNAPSHOT_ID;
  • Reporting version transitions for auditing patch application, filtering on OLD_VERSION != NEW_VERSION.
  • Filtering on IS_FLAGGED_FILE or BRANCH_TYPE to isolate flagged or branch-specific files for review.

Related Objects

  • AHL_SNAPSHOTS — the only documented foreign-key relationship, joined via SNAPSHOT_ID.
  • AD_PATCHES / AD_PATCH_DRIVERS — the AD patch repository, conceptually linked through PATCH_ID for identifying originating patches.
  • FND_IMP_PSMASTER and related PSMASTER variants — sibling file-impact master tables used across the patching framework.
  • FND_APPLICATION — maps APP_SHORT_NAME to application identifiers for reporting.
  • AD file-management and AutoPatch utilities that consume these impact rows during patch application and file synchronization.