Search Results hr_navigation_nodes_uk2




Overview
Explore in AI Chat

Overview

The HR_NAVIGATION_NODES table is a core repository within the Oracle E-Business Suite Human Resources (HRMS) module, specifically for the Oracle Navigator (Task Navigator) framework. Its primary role is to store the definitions for individual nodes that can be assembled into structured taskflows or navigation paths. These taskflows guide users through a sequence of forms or windows to complete specific business processes, such as hiring an employee or managing a performance review. The table is a seed data table, residing in the APPS_TS_SEED tablespace, indicating its definitions are part of the application's foundational metadata and are typically populated during installation or patching.

Key Information Stored

The table's structure is designed to uniquely identify and define each navigable node. The critical columns are:

  • NAV_NODE_ID (NUMBER): The system-generated primary key for the table. This is the unique identifier for every navigation node record, as enforced by the HR_NAVIGATION_NODES_PK index.
  • NAV_UNIT_ID (NUMBER): A foreign key column linking to the HR_NAVIGATION_UNITS table. This associates the node with its parent navigation unit or taskflow structure.
  • NAME (VARCHAR2(80)): The unique name of the node. Its uniqueness is enforced by the HR_NAVIGATION_NODES_UK2 index. This name typically identifies the functional purpose of the node.
  • CUSTOMIZED_RESTRICTION_ID (NUMBER(15)): This column is pivotal for personalization and customizations. It holds an identifier for any custom restriction (like a view-only mode or a context-specific filter) that should be applied when this specific instance of the node is invoked. This allows the same underlying window to appear in different taskflows with different behavioral rules.

Common Use Cases and Queries

This table is primarily referenced for configuration analysis, troubleshooting navigation issues, and auditing customizations. A common administrative query is to list all defined nodes within the system, often joined with related tables to get a fuller context. For instance, to see all nodes and their associated navigation unit names, one might execute:

SELECT n.NAV_NODE_ID, n.NAME AS NODE_NAME, n.CUSTOMIZED_RESTRICTION_ID, u.NAME AS UNIT_NAME
FROM HR.HR_NAVIGATION_NODES n,
     HR.HR_NAVIGATION_UNITS u
WHERE n.NAV_UNIT_ID = u.NAV_UNIT_ID
ORDER BY u.NAME, n.NAME;

Another key use case involves investigating why a specific form behaves differently in two separate taskflows. By querying for nodes with the same NAME but different CUSTOMIZED_RESTRICTION_ID values, one can identify where personalized logic is applied. Support personnel may also query this table directly using a known NAV_NODE_ID to retrieve its definition during issue diagnosis related to the Task Navigator.

Related Objects

The HR_NAVIGATION_NODES table sits at the center of the Navigator metadata model, with defined relationships to other key structures.

  • Parent Reference (Foreign Key): The table has a foreign key constraint (HR_NAVIGATION_NODES_FK1) on the NAV_UNIT_ID column, referencing the HR_NAVIGATION_UNITS table. This defines the hierarchical relationship where a Navigation Unit contains one or more Navigation Nodes.
  • Child Reference (Referenced by): The table is referenced by the HR_NAVIGATION_NODE_USAGES table via its NAV_NODE_ID column. This relationship documents how and where individual nodes are utilized within the broader construction of taskflows and navigation maps.

These relationships illustrate the data flow: a Navigation Unit (process) is composed of Navigation Nodes (steps), and those nodes are then placed into specific usages within the navigational UI.