Search Results bug_no




Overview
Explore in AI Chat

Overview

APPS.FND_IMP_PISUMMARY_VL is a reporting view in the Oracle E-Business Suite Applications (APPS) schema that consolidates the results of patch impact analysis performed by the Patch Information System (PIS). It presents a per-bug, per-patch, per-snapshot summary of how a given patch or bug fix affects the file system, applications, and responsibilities within an EBS instance. The view is a key object in the patch impact and dependency reporting infrastructure used by Applications DBA (AD) utilities when assessing the scope of a patch before it is applied.

The name suffix _VL denotes a "view with language" convention, although in this instance the view does not expose a translated (MLS) column set. Instead, it serves as a summarized, presentation-oriented view intended to be queried directly by reports or diagnostic scripts. Its principal identification key is BUG_NO, which is why searches focused on a specific bug number — the exact term used in this article's originating query — return results directly from this view.

Underlying Base Objects

The view is defined over three documented base objects, all exposed through APPS synonyms:

  • FND_IMP_PSMASTER2 — the master patch information table, containing one row per file/object with a TYPEID of new, upgrade, overwrite, or not applied. This is the driving table (aliases a and b).
  • FND_IMP_AFFECTEDFILES — holds the affected (dependent) filenames associated with a bug and patch (alias d).
  • FND_IMP_MENU_DEP_SUMMARY2 — the menu/responsibility dependency summary, providing responsibility and path counts (alias c).

The view text joins these inline subqueries on BUG_NO, PATCH_ID, and SNAPSHOT_ID, using outer joins (the (+) operator) so that a bug is still reported even when affected-file, application, responsibility, or path data is absent.

Key Columns

  • BUG_NO — primary identifier of the bug or patch being summarized.
  • SNAPSHOT_ID — identifies the instance snapshot against which the impact was collected.
  • PATCH_ID — the patch associated with the summarized rows.
  • NEW, UPGRADE, OVERWRITE — counts of files by TYPEID classification.
  • NOT_APPLIED — count of files flagged as not applied.
  • INSTALL_CNT — derived sum of new, upgrade, and overwrite files that will actually be installed.
  • FILES_CNT — total of install count plus not-applied files.
  • AFFECTED — count of distinct dependent filenames from FND_IMP_AFFECTEDFILES.
  • APP_CNT — distinct application short names touched.
  • RESP_CNT / PATH_CNT — distinct responsibilities and total menu paths affected.
  • IS_FLAGGED_FILE — count of upgrade/overwrite files carrying a flagged status.

Common Use Cases and Queries

This view is typically queried to answer "what will this patch do to my system?" questions. A common pattern filters by bug number:

  • Impact sizing: SELECT bug_no, install_cnt, files_cnt, app_cnt, resp_cnt FROM fnd_imp_pisummary_vl WHERE bug_no = :bug_no ORDER BY snapshot_id;
  • Cross-snapshot comparison: grouping by snapshot_id to compare patch impact before and after a snapshot refresh.
  • Dependency triage: selecting rows where affected > 0 or is_flagged_file > 0 to highlight patches with downstream file or menu dependencies.
  • Reporting on responsibility exposure: ordering by resp_cnt DESC to prioritise patches with the widest functional footprint.

Because the view already aggregates the detail tables, it is well suited to direct report queries without additional GROUP BY clauses, and to feeding patch review dashboards. Analysts should note that counts depend on a valid, current snapshot; stale SNAPSHOT_ID values will understate impact.