Search Results hr_navigation_context_rule_uk1




Overview
Explore in AI Chat

Overview

The HR_NAVIGATION_CONTEXT_RULES table is a core data security and navigation control object within the Oracle E-Business Suite Human Resources (HRMS) module. Its primary function is to enforce conditional navigation rules between different HRMS forms and functions. The table defines the specific business logic conditions that must be satisfied for a user to successfully navigate from one HR "unit" (such as a person record) to another (such as an assignment). If the defined condition fails at the moment of navigation, the system prevents the action and displays an appropriate error message. This mechanism is essential for maintaining data integrity and ensuring users follow valid business process flows, such as preventing navigation to an assignment form for a person who is not an employee.

Key Information Stored

The table stores a concise set of columns that define each navigation rule. The NAV_CONTEXT_RULE_ID is a system-generated unique identifier serving as the primary key. The GLOBAL_USAGE_ID is a foreign key that links the rule to a specific navigation pathway defined in the HR_NAV_UNIT_GLOBAL_USAGES table. The rule's logic is defined by two key columns: EVALUATION_TYPE_CODE specifies the type of condition check (e.g., 'Not Null', 'Equals'), and VALUE holds the acceptable value against which the condition is evaluated. For example, a rule might specify an evaluation type of "Equals" with a value of "EMP" to ensure the person's type is Employee.

Common Use Cases and Queries

The primary use case is troubleshooting navigation failures within HRMS forms or analyzing the security model for customizations. Administrators or developers may query this table to understand why a specific menu path is disabled or generates an error. A common query involves joining with related navigation tables to see all rules for a given functional path.

SELECT ncr.NAV_CONTEXT_RULE_ID,
       ncr.GLOBAL_USAGE_ID,
       ncr.EVALUATION_TYPE_CODE,
       ncr.VALUE,
       hnu.UNIT_ID
FROM   hr.HR_NAVIGATION_CONTEXT_RULES ncr,
       hr.HR_NAV_UNIT_GLOBAL_USAGES hnu
WHERE  ncr.GLOBAL_USAGE_ID = hnu.GLOBAL_USAGE_ID
AND    hnu.UNIT_ID = <desired_unit_id>;

Another critical pattern is validating the existence of the primary key constraint, which was the user's initial search term. This can be checked via data dictionary views like USER_CONSTRAINTS.

Related Objects

  • HR_NAV_UNIT_GLOBAL_USAGES: This is the primary parent table, as indicated by the foreign key relationship on GLOBAL_USAGE_ID. It defines the global navigation usages to which the context rules are applied.
  • HR_NAVIGATION_CONTEXT_RULE_PK: The primary key index on NAV_CONTEXT_RULE_ID, which enforces uniqueness for the table's main identifier.
  • HR_NAVIGATION_CONTEXT_RULE_UK1: A unique key index on the combination of GLOBAL_USAGE_ID, EVALUATION_TYPE_CODE, and VALUE, preventing duplicate rule definitions for the same navigation usage.