Search Results old_version




Overview
Explore in AI Chat

Overview

FND_IMP_PSMASTER_VL is a database view owned by the APPS schema in Oracle E-Business Suite, classified under the FND – Application Object Library product. Its status is VALID on both Oracle EBS 12.1.1 and 12.2.2. The view consolidates patch-file inventory data used during the Online Patching and patching-file tracking process, exposing a unified list of files that have been applied, are pending application, or are newly introduced by a patch or snapshot. The "_VL" suffix conventionally denotes a view layered over a translation or validation wrapper, though in this case the view is a union-based reporting construct rather than a translated (TL) entity; it presents a denormalized, human-readable projection of patch-state master data.

The view plays a diagnostic and reconciliation role. Database administrators, patch analysts, and technical consultants query it to determine which version of a file was captured in a prior snapshot, whether that file represents an upgrade, whether it was skipped, and whether branching has occurred between the old and new file versions.

Underlying Base Objects

FND_IMP_PSMASTER_VL is defined over the following documented base objects:

  • FND_IMP_PSCOMMON (synonym) – the primary source of patch-file comparison records, aliased as X in the view definition.
  • FND_IMP_PSNEW (synonym) – the source of newly introduced files, aliased as Y and combined via UNION ALL.
  • FND_IMP_CONV_PKG (package) – a PL/SQL package supplying two functions invoked directly in the view text: COMPARE_RCSID and CHECK_BRANCHING.

The view therefore performs no independent storage; it derives all content at runtime through the UNION ALL of FND_IMP_PSCOMMON and FND_IMP_PSNEW, with row classification computed by calls into FND_IMP_CONV_PKG. Because the base objects are referenced as synonyms, the view resolves them through the APPS synonym layer, consistent with EBS naming standards.

Key Columns

The view exposes the following columns, each carrying specific patch-tracking meaning:

  • BUG_NO – the bug or patch number associated with the file record.
  • SNAPSHOT_ID – the identifier of the snapshot under which the file was captured.
  • APP_SHORT_NAME – the short name of the application owning the file.
  • DIRECTORY – the file system directory path of the tracked file.
  • FILENAME – the name of the file.
  • TYPEID – a derived classification. For records from FND_IMP_PSCOMMON, FND_IMP_CONV_PKG.COMPARE_RCSID returns 1 or 2, mapped to 'UPGRADE'; 3 mapped to 'NOT APPLIED'; otherwise 'UNKNOWN'. Records from FND_IMP_PSNEW are hardcoded as 'NEW'.
  • NEW_VERSION – the incoming or current file version.
  • OLD_VERSION – the previously captured file version. This column is NULL for records sourced from FND_IMP_PSNEW, since those files have no prior version.
  • IS_FLAGGED_FILE – an indicator marking the file as flagged for attention.
  • BRANCH_TYPE – derived from FND_IMP_CONV_PKG.CHECK_BRANCHING, which evaluates branching between OLD_VERSION and NEW_VERSION. A literal -1 is returned for new files.
  • PATCH_ID – the identifier of the patch that introduced or affected the file.

Common Use Cases and Queries

The view is used chiefly to audit patch application state, verify whether files were upgraded, skipped, or newly added, and to detect version branching that may indicate merge conflicts. A typical query filtering upgraded files is:

SELECT BUG_NO, APP_SHORT_NAME, DIRECTORY, FILENAME, NEW_VERSION, OLD_VERSION, PATCH_ID FROM APPS.FND_IMP_PSMASTER_VL WHERE TYPEID = 'UPGRADE';

To isolate files that were not applied during a patch cycle:

SELECT BUG_NO, FILENAME, NEW_VERSION, OLD_VERSION FROM APPS.FND_IMP_PSMASTER_VL WHERE TYPEID = 'NOT APPLIED';

To review newly introduced files for a given application:

SELECT BUG_NO, DIRECTORY, FILENAME, NEW_VERSION, PATCH_ID FROM APPS.FND_IMP_PSMASTER_VL WHERE TYPEID = 'NEW' AND APP_SHORT_NAME = 'FND';

Because TYPEID and BRANCH_TYPE are computed per row through calls into FND_IMP_CONV_PKG, queries that filter on these columns still incur the underlying PL/SQL evaluation cost, so restricting by BUG_NO, SNAPSHOT_ID, or APP_SHORT_NAME first is advisable on large volumes.