Search Results fnd_imp_menu_dep_summary2




Overview
Explore in AI Chat

Overview

FND_IMP_MENU_DEP_SUMMARY2 is an Oracle E-Business Suite table owned by the APPLSYS schema within the FND (Application Object Library) product. Its name indicates that it belongs to the menu dependency import and analysis infrastructure used by Oracle's internal tooling to enumerate the dependency footprint of menus, responsibilities, and forms across an EBS environment. The table carries a status of VALID in the ETRM repository, confirming it is a supported, documented physical object in both EBS 12.1.1 and 12.2.2.

The table records the results of automated scans that capture, per bug or patch reference, which navigation paths, forms, responsibilities, and applications are exercised by a given menu structure, along with a count of how many users were observed touching each path. This makes the object a diagnostic and impact-analysis artifact rather than a transactional runtime table. In terms of Data Vault modeling heuristics mined from its foreign-key structure, the table is classified as standalone, meaning it does not participate in the hub-and-link topology typical of normalized operational data. A standalone classification suggests it can be modeled as an independent satellite or staging-style table keyed on its own snapshot identifier.

Key Information Stored

The table contains ten documented columns. The most significant are:

  • SNAPSHOT_ID — the primary identifier for an individual scan or capture run. It is also the sole documented foreign key, referencing AHL_SNAPSHOTS, which places each row in the context of a specific environment or point-in-time snapshot.
  • BUG_NO — the bug or defect reference under investigation, linking summary rows to the change record that motivated the capture.
  • PATCH_ID — the patch context associated with the scan, allowing dependency summaries to be correlated to a specific patch delivery.
  • PATH — the navigation path (menu hierarchy traversal) exercised by the captured data.
  • FORM_NAME — the Oracle Forms module reached via the path.
  • APPLICATION_SHORT_NAME — the short name of the owning application, enabling cross-application reporting.
  • RESPONSIBILITY_NAME and RESPONSIBILITY_ID — the responsibility under which the path was executed. RESPONSIBILITY_ID is the natural identifier, while RESPONSIBILITY_NAME provides denormalized, human-readable context.
  • USER_CNT — a numeric measure of how many users followed the associated path, useful for prioritising high-impact dependency analysis.
  • DESCRIPTION — free-text detail describing the captured dependency entry.

The surrogate primary key is SNAPSHOT_ID together with the scan-specific discriminators; business-key candidates for uniqueness typically involve the combination of SNAPSHOT_ID, BUG_NO, PATCH_ID, RESPONSIBILITY_ID, and FORM_NAME.

Common Use Cases and Queries

Typical use cases include patch impact analysis, responsibility menu dependency mapping, and identifying widely used forms before retiring or modifying them. A representative query joins the summary to its snapshot parent:

  • SELECT s.snapshot_id, s.bug_no, s.patch_id, s.responsibility_name, s.form_name, s.user_cnt FROM fnd_imp_menu_dep_summary2 s WHERE s.snapshot_id = :snapshot_id ORDER BY s.user_cnt DESC;
  • SELECT s.form_name, s.application_short_name, SUM(s.user_cnt) total_users FROM fnd_imp_menu_dep_summary2 s GROUP BY s.form_name, s.application_short_name ORDER BY total_users DESC;
  • SELECT s.* FROM fnd_imp_menu_dep_summary2 s, ahl_snapshots a WHERE s.snapshot_id = a.snapshot_id AND s.bug_no = :bug_no;

These patterns support reporting on form reach, responsibility coverage, and patch-level dependency comparisons across snapshots.

Related Objects

  • AHL_SNAPSHOTS — referenced by SNAPSHOT_ID; provides the parent snapshot context for every summary row.
  • FND_RESPONSIBILITY — supplies the authoritative definition behind RESPONSIBILITY_ID and RESPONSIBILITY_NAME.
  • FND_APPLICATION — resolves APPLICATION_SHORT_NAME to the owning application record.
  • FND_FORM — the registered form definition corresponding to FORM_NAME.
  • FND_MENUS / FND_MENU_ENTRIES — the menu structures whose paths are summarized here.
  • AD_PATCH_RUN_BUGS / AD_BUGS — patch and bug metadata that contextualises BUG_NO and PATCH_ID.

Together these objects allow the summary table to be resolved into application, responsibility, menu, and patch dimensions for analysis and reporting.