Results for “user_cnt”

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

Overview

FND_IMP_MENU_DEP2 is an Oracle Application Object Library (FND) table owned by the APPLSYS schema. It is a repository for menu dependency information captured during import and patching operations, associating menu structure metadata with a snapshot identifier, a bug or patch reference, and the application, responsibility, and root menu context in which the menu is used. The table records the resolved path, form name, and user count associated with each captured menu entry, allowing support and patching diagnostics to trace how a given menu configuration was derived at the time a snapshot was taken.

The table is documented with ten physical columns in the ETRM 12.2.2 schema and is present with VALID status in both 12.1.1 and 12.2.2 environments. Its name follows the FND_IMP convention used for staging and capture tables associated with the menu import and diagnostics utilities. The heuristic Data Vault classification mined from the foreign key structure is standalone, meaning the table contains no dependency-driven hub, link, or satellite pattern; it should be modeled as an independent staging or capture entity rather than as part of a normalized Data Vault construct.

Key Information Stored

The documented column set consists of ten attributes, of which the following are the most operationally significant.

• SNAPSHOT_ID — Identifier of the snapshot under which the menu dependency rows were captured. This is the principal grouping key and is also the column involved in the documented foreign key reference to AHL_SNAPSHOTS.
• APP_ID — Application identifier for the application context in which the menu dependency was recorded. A documented foreign key reference from this column points to IGS_UC_APPLICANTS.
• RESP_ID — Responsibility identifier, qualifying the menu context to a specific responsibility.
• ROOT_MENU_ID — Identifier of the root menu from which the reported dependency path originates.
• PATH — The resolved menu path, providing the navigation hierarchy traversed to reach the entry in question.
• FORM_NAME — The form invoked at the end of the recorded path, allowing the functional target of the menu entry to be identified.
• USER_CNT — Count of users associated with the captured menu entry, supporting impact analysis.
• DESCRIPTION — Descriptive text for the captured menu dependency record.
• BUG_NO and PATCH_ID — References to the bug and patch under investigation, tying the snapshot rows to a specific remediation or release event.

No single-column surrogate primary key is documented for this table. SNAPSHOT_ID functions as the primary grouping attribute, with meaningful uniqueness likely expressed as a composite of SNAPSHOT_ID with APP_ID, RESP_ID, ROOT_MENU_ID, and PATH. Because the metadata documents no unique index explicitly, these business-key candidates should be validated against the live data dictionary before being treated as authoritative.

Common Use Cases and Queries

The table is primarily used for diagnosing menu-related problems encountered during patching or support investigation. Typical scenarios include determining which users are affected by a broken or changed menu path, identifying every form reachable from a given root menu within a responsibility, and correlating menu observations with a specific bug number or patch identifier.

A representative query lists the highest-impact dependencies for a snapshot:

• SELECT snapshot_id, app_id, resp_id, root_menu_id, path, form_name, user_cnt FROM applsys.fnd_imp_menu_dep2 WHERE snapshot_id = :p_snapshot ORDER BY user_cnt DESC;
• SELECT bug_no, patch_id, form_name, COUNT(*) FROM applsys.fnd_imp_menu_dep2 GROUP BY bug_no, patch_id, form_name;

Reporting use cases include patch impact summaries showing the aggregate user population reachable through affected forms, and responsibility-level menu footprint reports. Because the table is a capture artifact rather than a transactional entity, queries are normally scoped by SNAPSHOT_ID or PATCH_ID, and historical rows should be treated as point-in-time evidence.

Related Objects

The documented foreign key relationships connect this table to the following objects.

• AHL_SNAPSHOTS — joined on SNAPSHOT_ID, providing the snapshot context for each captured row.
• IGS_UC_APPLICANTS — the documented FK target for APP_ID as recorded in the mined relationship data.
• FND_RESPONSIBILITY — natural reference point for RESP_ID, supplying the responsibility definition for the menu context.
• FND_MENUS — natural reference point for ROOT_MENU_ID.
• FND_APPLICATION — natural reference point for the application identified by APP_ID.
• FND_FORM — lookup for the form named in FORM_NAME.

The documented foreign key targets should be treated as the authoritative relationships; the additional FND reference points above are conventional joins based on the column names recorded in the ETRM schema. No public API is documented against this table, and it should generally be accessed read-only for diagnostics and impact analysis.