Results for “menu_navigation”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.FND_IMP_MENU_DEP_SUMMARY2_VL is a reporting view in the Oracle E-Business Suite Applications (APPS) schema that summarizes menu navigation dependencies captured during patching and file-application activity. It is a critical component of Oracle's patch impact and dependency analysis framework, exposed primarily through the ETRM (E-Business Suite Technical Reference Manual) and the patch analysis utilities associated with AD (Applications DBA) and the online patching infrastructure.
The view's central purpose is to answer the question: which responsibilities and applications are affected when menu navigation dependencies exist between a patched object and its dependents? The "VL" suffix indicates a view that has undergone translation ("view language") processing, meaning responsibility names are joined against FND_RESPONSIBILITY_TL and filtered by userenv('LANG') so that only the session's current language rows are returned. The view joins patch snapshot and dependency metadata to responsibility, application, and user-assignment data, producing a flattened result set suitable for impact analysis reports and post-patch verification queries.
The filter r.dependency_type = 'MENU_NAVIGATION' is the defining characteristic of this view. It restricts output to dependencies classified as menu navigation links — that is, parent/child relationships where a patched object is reachable through a responsibility's menu structure. This directly addresses searches for "menu_navigation" in a patch or dependency context. Records where the dependency type is anything other than MENU_NAVIGATION are excluded.
Underlying Base Objects
The view is defined over the following documented base objects:
- FND_IMP_PSMASTER2 (synonym) — patch snapshot master records, supplying directory, filename, file type, patch ID, and bug number.
- FND_IMP_AFFECTEDFILES (synonym) — affected-file inventory per patch, unioned with PSMASTER2 to build the object path list.
- FND_IMP_DEPRELATIONS (synonym) — the dependency relations table, filtered on dependency_type = 'MENU_NAVIGATION'.
- FND_IMP_DEPOBJECTS (synonym) — dependency object registry, providing object_name, object_id, and attrib2 (menu ID) and attrib3 (description).
- FND_RESPONSIBILITY (synonym) — the responsibility definition, joined via
re.menu_id = o.attrib2. - FND_RESPONSIBILITY_TL (synonym) — translated responsibility names, language-filtered to the session locale.
- FND_APPLICATION (synonym) — application short name lookup.
- FND_USER_RESP_GROUPS (view) — active user-to-responsibility assignments, used to derive a user count.
- FND_DATE (package) — supporting date-handling logic referenced in dependency resolution.
The ansi-join structure produces an inline union of FMB/JSP source files (file_type 'fmb' or 'jsp') and affected files, both excluding rows where typeid = 'not applied'. This means the view reports only dependencies arising from patches that were actually applied to the instance.
Key Columns
- snapshot_id — identifier of the patch snapshot the row belongs to.
- bug_no — the originating bug or patch reference number.
- path — the object path (directory/filename), aliased from o.object_name.
- form_name — the filename of the affected form or JSP.
- user_cnt — subquery count of active (valid on SYSDATE) FND_USER_RESP_GROUPS assignments for the responsibility; a measure of blast radius.
- application_short_name — owning application of the responsibility.
- responsibility_name — the translated responsibility name for the session language.
- responsibility_id — the numeric responsibility identifier.
- description — free-text description from dependency object attrib3.
- patch_id — the patch that introduced the dependency.
Common Use Cases and Queries
The primary use case is identifying which responsibilities would be impacted by a menu navigation dependency before or after applying a patch. A representative query lists impacted responsibilities sorted by user count:
- SELECT responsibility_name, application_short_name, user_cnt, patch_id FROM apps.fnd_imp_menu_dep_summary2_vl ORDER BY user_cnt DESC;
- Filter to a single application: ... WHERE application_short_name = 'XXCUSTOM';
- Isolate a specific bug: ... WHERE bug_no = '12345678';
- Locate a specific form path: ... WHERE form_name LIKE 'XX%FMB';
- Aggregate impact count: SELECT patch_id, COUNT(DISTINCT responsibility_id) resp_count FROM apps.fnd_imp_menu_dep_summary2_vl GROUP BY patch_id;
Because user_cnt is computed against the current SYSDATE with active-date filtering, these queries reflect live assignment volumes at execution time, making the view suitable for change-impact assessments, upgrade dry-runs, and audit reports in both 12.1.1 and 12.2.2 environments.
-
FND_IMP_MENU_DEP_SUMMARY2_VL
APPS.FND_IMP_MENU_DEP_SUMMARY2_VL·↳ FND_APPLICATION·↳ FND_DATE·↳ FND_IMP_AFFECTEDFILES·Explore FND module →
-
FND_IMP_MENU_DEP_SUMMARY2_VL
APPS.FND_IMP_MENU_DEP_SUMMARY2_VL·↳ FND_APPLICATION·↳ FND_DATE·↳ FND_IMP_AFFECTEDFILES·Explore FND module →