Search Results from_nav_unit_id

Overview

The HR_INCOMPATIBILITY_RULES table is a core data structure within the Oracle E-Business Suite (EBS) Human Resources (HRMS) module, specifically under the PER product family. Its primary function is to enforce business logic governing user navigation by defining incompatible relationships between navigation units. In the context of Oracle EBS 12.1.1 and 12.2.2, navigation units are logical groupings of forms, functions, or menus. This table acts as a repository for rules that prevent a user from accessing one navigation unit if they have already accessed another, thereby controlling workflow and ensuring data integrity or security protocols are maintained during a user session.

Key Information Stored

The table's structure is designed to define a pairwise relationship between navigation units. The primary data elements are the identifiers for the two units involved in the rule. As defined by the primary key constraint HR_INCOMPATIBILITY_RULES_UK, the table's essential columns are FROM_NAV_UNIT_ID and TO_NAV_UNIT_ID. Both columns store foreign key references to the HR_NAVIGATION_UNITS table. A record in this table signifies that the navigation unit identified by FROM_NAV_UNIT_ID is incompatible with the navigation unit identified by TO_NAV_UNIT_ID. The relationship may be interpreted bidirectionally by application logic, meaning the rule could prevent navigation from Unit A to Unit B and also from Unit B to Unit A.

Common Use Cases and Queries

This table is integral to the dynamic menu and function security within Oracle HRMS. A primary use case is preventing conflicting transactions within a single session, such as blocking access to a "Terminate Employee" form if the user is currently in a "Promote Employee" process for the same person. System administrators may query this table to audit or manage navigation rules. Common SQL patterns include identifying all incompatibilities for a specific navigation unit or verifying if a rule exists between two units before allowing a navigation event.

• To find all navigation units incompatible with a specific unit (e.g., ID 100):
  SELECT to_nav_unit_id FROM hr_incompatibility_rules WHERE from_nav_unit_id = 100;
• To check for a specific incompatibility rule:
  SELECT 'Rule Exists' FROM hr_incompatibility_rules WHERE (from_nav_unit_id = 100 AND to_nav_unit_id = 200) OR (from_nav_unit_id = 200 AND to_nav_unit_id = 100);

Related Objects

The HR_INCOMPATIBILITY_RULES table has a direct and exclusive dependency on the HR_NAVIGATION_UNITS table, which stores the master definition of all navigable components. As documented in the provided metadata, the following foreign key relationships exist, ensuring referential integrity:

• HR_INCOMPATIBILITY_RULES.FROM_NAV_UNIT_ID references HR_NAVIGATION_UNITS (Foreign Key).
• HR_INCOMPATIBILITY_RULES.TO_NAV_UNIT_ID references HR_NAVIGATION_UNITS (Foreign Key).

These relationships mean that every FROM_NAV_UNIT_ID and TO_NAV_UNIT_ID value must have a corresponding, valid entry in the HR_NAVIGATION_UNITS table. This design centralizes the definition of navigation units, allowing the incompatibility rules table to function as a pure relationship table between them.