Results for “user_cnt”

24 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The FND_IMP_MENU_DEP_SUMMARY2_VL view is a reporting object owned by the APPS schema within the FND (Application Object Library) product module. It is a member of the FND_IMP_* family of objects, which are used by Oracle E-Business Suite patch and patching-analysis tooling (notably the Patch Information / "IMP" snapshot utilities) to report on dependency relationships captured during patch application. Specifically, this view summarizes MENU_NAVIGATION dependencies that exist between a patched file (FMB or JSP form/menu artifact) and the responsibilities that navigate to it, along with the number of active users assigned to each affected responsibility.

Its role is diagnostic and administrative rather than transactional. During a patch impact analysis, customers and DBAs can use the view to determine which responsibilities, applications, and end users are potentially affected by a change to a given form or JSP navigation path. The view exposes a stable, denormalized result set that joins patch snapshot metadata with responsibility, application, and user-assignment data, making it convenient for both ad-hoc queries and integration into downstream impact reports.

Underlying Base Objects

The view is defined as a join over several documented base objects, mostly accessed through APPS synonyms:

Key Columns

  • SNAPSHOT_ID — identifier for the patch snapshot from which the dependency was captured.
  • BUG_NO — the bug or patch tracking number associated with the affected file.
  • PATH — the directory/filename path of the changed form or JSP artifact.
  • FORM_NAME — the bare filename of the patched artifact.
  • USER_CNT — the count of active users assigned to the responsibility (the column of interest in the search for "user_cnt"). "Active" is evaluated against SYSDATE between START_DATE and END_DATE on FND_USER_RESP_GROUPS.
  • APPLICATION_SHORT_NAME — the short name of the owning application.
  • RESPONSIBILITY_NAME / RESPONSIBILITY_ID — the responsibility affected by the menu navigation dependency.
  • DESCRIPTION — the object description sourced from FND_IMP_DEPOBJECTS.ATTRIB3.
  • PATCH_ID — the patch identifier applied to the snapshot.

Common Use Cases and Queries

A typical use case is estimating patch impact by exposure — i.e., how many users touch each affected responsibility. For example:

SELECT FORM_NAME, RESPONSIBILITY_NAME, USER_CNT
FROM APPS.FND_IMP_MENU_DEP_SUMMARY2_VL
WHERE USER_CNT > 0
ORDER BY USER_CNT DESC;

Another scenario isolates high-impact responsibilities for a specific snapshot or bug:

SELECT SNAPSHOT_ID, BUG_NO, FORM_NAME, RESPONSIBILITY_NAME, USER_CNT
FROM APPS.FND_IMP_MENU_DEP_SUMMARY2_VL
WHERE SNAPSHOT_ID = :snapshot_id;

Because the view joins TL tables and evaluates SYSDATE within the USER_CNT subquery, results are language- and time-sensitive and should be queried in the same session language used for reporting.