Search Results fnd_imp_menu_dep_summary3_vl




Overview
Explore in AI Chat

Overview

FND_IMP_MENU_DEP_SUMMARY3_VL is a reporting view in the APPS schema of Oracle E-Business Suite, owned by the FND (Application Object Library) product. It is an aggregate summary view built on top of the FND_IMP_MENU_DEP_SUMMARY2 base object and is used during Oracle EBS release 12.1.1 and 12.2.2 upgrade and patching cycles to analyze responsibility-level menu dependency data. Specifically, the view condenses the detailed menu dependency rows into one summarized row per snapshot, bug number, patch identifier, and application short name, exposing a distinct responsibility count (RESP_CNT) and a total path count (PATH_CNT).

This object belongs to the family of FND implementation/analysis views used by the Applications DBA (AD) and upgrade utilities to report how many distinct responsibilities are affected by menu hierarchy dependencies, thereby helping assess the impact of a patch or upgrade on navigation structures. Because it is a summary (VL, or "view/summary" style) view rather than a transactional table, it is read-only and intended for diagnostics, reporting, and integration into custom analysis queries rather than for direct maintenance.

Underlying Base Objects

The view is defined over a single documented base object: FND_IMP_MENU_DEP_SUMMARY2, which is referenced through a synonym. The view performs no joins across multiple tables; instead it aggregates the rows already present in FND_IMP_MENU_DEP_SUMMARY2. The defining query is:

The GROUP BY clause collapses the detail rows by SNAPSHOT_ID, BUG_NO, PATCH_ID, and APPLICATION_SHORT_NAME, so the view always reports one summarized record per unique combination of those four keys. The relationship to the base object is therefore one-to-many in the reverse direction: many FND_IMP_MENU_DEP_SUMMARY2 rows (each carrying a responsibility identifier and a path) map to a single summarized row in this view.

Key Columns

  • SNAPSHOT_ID — Identifier of the collection snapshot for which dependency data was captured. This is a grouping key that isolates one analysis run from another.
  • BUG_NO — The bug or patch tracking number associated with the analyzed dependency, used to correlate results with a specific fix or patch request.
  • APPLICATION_SHORT_NAME — The short name of the application whose menu structure is being summarized (for example, FND, GL, or AP), allowing per-application rollup.
  • RESP_CNT — The count of distinct RESPONSIBILITY_ID values within the group. This is the column most frequently searched for under the term "resp_cnt" and represents the number of distinct responsibilities impacted.
  • PATH_CNT — The total count of rows (paths) contributing to the group, giving the aggregate number of menu dependency paths for that snapshot/bug/patch/application combination.
  • PATCH_ID — The patch identifier under which the dependency was introduced or observed, used together with BUG_NO for patch-level analysis.

Common Use Cases and Queries

Typical usage centers on impact assessment during upgrades and patching. Administrators may want to know how many distinct responsibilities are affected by a given bug or patch, or compare responsibility and path counts across applications for a snapshot.

  • Count affected responsibilities for a specific bug:
    SELECT SNAPSHOT_ID, BUG_NO, APPLICATION_SHORT_NAME, RESP_CNT, PATH_CNT FROM FND_IMP_MENU_DEP_SUMMARY3_VL WHERE BUG_NO = :bug_no;
  • Aggregate impact by application for a snapshot:
    SELECT APPLICATION_SHORT_NAME, SUM(RESP_CNT) total_responsibilities, SUM(PATH_CNT) total_paths FROM FND_IMP_MENU_DEP_SUMMARY3_VL WHERE SNAPSHOT_ID = :snapshot_id GROUP BY APPLICATION_SHORT_NAME;
  • Identify the highest-impact patches by responsibility count:
    SELECT BUG_NO, PATCH_ID, SUM(RESP_CNT) resp_sum FROM FND_IMP_MENU_DEP_SUMMARY3_VL GROUP BY BUG_NO, PATCH_ID ORDER BY resp_sum DESC;

Because the view is read-only and derived, results should be refreshed by regenerating the underlying snapshot data in FND_IMP_MENU_DEP_SUMMARY2 before reuse.