Search Results bug_no




Overview
Explore in AI Chat

Overview

FND_IMP_PISUMMARY_VL is a reporting view owned by the APPS schema in the FND — Application Object Library product. It consolidates the results of a patch impact analysis snapshot into a single row per patch, bug number, and snapshot identifier, giving implementers and DBAs a concise picture of what a specific Oracle patch will change before the patch is applied. The view is commonly queried when investigating the effect of an upgrade or one-off patch, and its most frequently searched attribute is PATCH_ID, which uniquely ties the summary to the patch under evaluation.

Because it is a view and not a table, FND_IMP_PISUMMARY_VL stores no data itself. Instead, it aggregates rows from three underlying patch-impact tables and joins them on BUG_NO, PATCH_ID, and SNAPSHOT_ID. The "_VL" suffix follows the standard EBS convention for a view that exposes a translated or summary representation of one or more underlying entities.

Underlying Base Objects

The view is defined over three synonyms that resolve to the patch impact analysis tables:

  • FND_IMP_PSMASTER2 — the master file-level table that records each file affected by a patch bug, along with its type (NEW, UPGRADE, OVERWRITE, or NOT APPLIED). It is the primary driving table in the view.
  • FND_IMP_AFFECTEDFILES — records dependent files affected by the patch, used to compute the AFFECTED count.
  • FND_IMP_MENU_DEP_SUMMARY2 — summarizes the menu and responsibility dependencies impacted by the patch, used to compute responsibility and path counts.

The joins are outer joins anchored on A (the aggregation of FND_IMP_PSMASTER2), so a row is always returned for each BUG_NO/PATCH_ID/SNAPSHOT_ID combination even where dependent file, affected file, or menu dependency data does not exist. This design preserves the completeness of the patch summary.

Key Columns

  • PATCH_ID — the unique identifier of the patch associated with the summary row; the primary filtering column for patch-specific analysis.
  • BUG_NO — the bug or patch number tracked in the analysis.
  • SNAPSHOT_ID — the impact analysis snapshot from which the counts were derived.
  • NEW, UPGRADE, OVERWRITE, NOT_APPLIED — counts of files in each category, computed with DECODE over TYPEID in FND_IMP_PSMASTER2.
  • INSTALL_CNT — sum of NEW, UPGRADE, and OVERWRITE; the number of files that will actually be installed or replaced.
  • FILES_CNT — INSTALL_CNT plus NOT_APPLIED; the total files examined by the analysis.
  • AFFECTED — distinct count of dependent filenames from FND_IMP_AFFECTEDFILES.
  • APP_CNT — distinct applications affected, derived from APP_SHORT_NAME values in FND_IMP_PSMASTER2.
  • RESP_CNT and PATH_CNT — distinct responsibility count and total menu path count from FND_IMP_MENU_DEP_SUMMARY2.
  • IS_FLAGGED_FILE — count of UPGRADE or OVERWRITE files marked as flagged, indicating files requiring special attention.

Common Use Cases and Queries

A typical query retrieves the full impact profile for a given patch:

  • SELECT patch_id, bug_no, install_cnt, files_cnt, affected, app_cnt FROM fnd_imp_pisummary_vl WHERE patch_id = :patch_id; — returns the headline counts for a patch.
  • SELECT patch_id, resp_cnt, path_cnt FROM fnd_imp_pisummary_vl WHERE bug_no = :bug_no ORDER BY patch_id; — examines menu and responsibility impact across patches for a bug.
  • SELECT * FROM fnd_imp_pisummary_vl WHERE is_flagged_file > 0; — identifies patches containing flagged files that warrant review.

These queries support patch impact assessment, upgrade planning, and remediation review. All access should be performed in the APPS schema context, and results apply only to the specific snapshot recorded in SNAPSHOT_ID.