Search Results files_affected

Overview

FND_IMP_PSMASTER2_VL is a reporting view owned by the APPS schema in Oracle E-Business Suite and registered under the FND – Application Object Library product. It is a variant of the patch snapshot master view used by the AutoPatch and patch application infrastructure. Where the underlying FND_IMP_PSMASTER_VL exposes the raw patch snapshot inventory (bug number, application short name, directory, filename, version information and branch type), FND_IMP_PSMASTER2_VL re-projects that data and adds derived attributes required by downstream patch-processing consumers.

In EBS 12.1.1 and 12.2.2 the view remains VALID and is used internally by patch-merge and file-classification logic. Its most significant characteristic is the inclusion of the literal FILES_AFFECTED column, returned as the constant value 0, and the derived TYPE_AFFECTED column returned as the literal string 'NULL'. These placeholders exist to align the view's shape with the requirements of the calling interface rather than to carry meaningful data in every deployment. In 12.2.2, where the online patching (adop) architecture changed the way file systems and editions are managed, this view continues to serve as a compatibility and reporting layer over the snapshot master data.

The view is therefore best understood as a presentation and shaping layer over the core patch snapshot inventory, not as a source of independent business data.

Underlying Base Objects

The documented base objects referenced by FND_IMP_PSMASTER2_VL are FND_IMP_PSMASTER_VL (VIEW) and FND_IMP_CONV_PKG (PACKAGE). The view text confirms a direct dependency on FND_IMP_PSMASTER_VL: the SELECT projects, without modification, the columns BUG_NO, SNAPSHOT_ID, APP_SHORT_NAME, DIRECTORY, FILENAME, TYPEID, NEW_VERSION, OLD_VERSION, IS_FLAGGED_FILE, BRANCH_TYPE, and PATCH_ID from that source view. The alias C is applied throughout.

FND_IMP_CONV_PKG is the conversion package associated with the patch snapshot import process. Its presence in the dependency metadata indicates that the view forms part of the conversion pipeline in which snapshot records are transformed into the format consumed by patch application. FND_IMP_PSMASTER_VL itself derives from the patch snapshot staging structures populated during AutoPatch processing, so the dependency chain runs from the patch snapshot base tables through FND_IMP_PSMASTER_VL to FND_IMP_PSMASTER2_VL. Because the view is defined entirely over other views and a package, it holds no storage of its own and no user-maintained data.

Key Columns

• BUG_NO – The bug or patch identifier associated with the snapshot record.
• SNAPSHOT_ID – Identifier of the patch snapshot to which the file record belongs.
• APP_SHORT_NAME – Application short name (for example FND, AP, GL) owning the file.
• DIRECTORY – The directory location of the file, used in TRANS_NAME construction.
• FILENAME – The name of the file within the snapshot.
• TYPEID – Internal type identifier inherited from the source view.
• NEW_VERSION / OLD_VERSION – The post-patch and pre-patch versions of the file.
• FILES_AFFECTED – Returned as the constant 0; a shape-compatibility placeholder.
• TYPE_AFFECTED – Returned as the literal string 'NULL'.
• FILE_TYPE – Derived from the filename extension using SUBSTR and INSTR.
• TRANS_NAME – Constructed for files with a .CLASS extension, producing an Oracle-style Java class name of the form ORACLE.APPS.<app>.<directory>.<file> after lowercasing the application short name and replacing path separators with dots.
• IS_FLAGGED_FILE – Flag indicating files of special interest to patch processing.
• BRANCH_TYPE – The branch or code-line type for the file.
• PATCH_ID – Identifier of the associated patch.

Common Use Cases and Queries

Because the view is part of the internal patch snapshot infrastructure, it is used principally for diagnostics and impact assessment rather than end-user reporting. Typical scenarios include identifying which files a patch touches, auditing file versions before and after a patch, and inspecting the derived Java class translation names for Java-based files.

Listing snapshot files for a given patch:

• SELECT bug_no, app_short_name, directory, filename, new_version FROM fnd_imp_psmaster2_vl WHERE patch_id = :patch_id;

Identifying Java class translations:

• SELECT app_short_name, filename, trans_name FROM fnd_imp_psmaster2_vl WHERE trans_name IS NOT NULL;

Reviewing file types across a snapshot:

• SELECT file_type, COUNT(*) FROM fnd_imp_psmaster2_vl WHERE snapshot_id = :snapshot_id GROUP BY file_type;

Because FILES_AFFECTED and TYPE_AFFECTED are constants, queries filtering on those columns return the full unfiltered set and should be avoided for selectivity. The view is most useful when joined back to patch and snapshot metadata by BUG_NO, PATCH_ID, or SNAPSHOT_ID.