Search Results from_nav_node_usage_id

Overview

The HR_NAVIGATION_PATHS table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HRMS) module, specifically under the PER product family. In the context of EBS 12.1.1 and 12.2.2, this table is fundamental to the Taskflow functionality, which guides users through structured, step-by-step processes for completing HR transactions. The table's primary role is to store the definition of navigation paths, which are the permissible transitions between individual steps (nodes) within a taskflow. It essentially maps the workflow of how a user can move from one task to another, ensuring a controlled and logical sequence of operations for complex HR processes such as hiring, promotions, or terminations.

Key Information Stored

The table stores metadata that defines the connections between navigation nodes. The primary columns, as indicated by the provided ETRM metadata, are the keys that establish these relationships. The NAV_PATH_ID column serves as the unique primary identifier for each path record. The two critical foreign key columns are FROM_NAV_NODE_USAGE_ID and TO_NAV_NODE_USAGE_ID. These columns store identifiers that link to the HR_NAV_NODE_USAGES table, defining the specific "from" and "to" nodes in the navigation sequence. The uniqueness constraint (UK1) on this pair of columns ensures that a direct path between any two given node usages is defined only once, preventing redundant or ambiguous navigation rules within the system.

Common Use Cases and Queries

This table is primarily accessed by the EBS application logic to render and enforce the navigation options presented to a user within a taskflow. From a technical or reporting perspective, common use cases include analyzing taskflow design, auditing process paths, and troubleshooting navigation issues. A typical query would join HR_NAVIGATION_PATHS to HR_NAV_NODE_USAGES and related tables like HR_NAVIGATION_NODES to translate IDs into meaningful business step names.

Sample Query Pattern:

• SELECT np.NAV_PATH_ID, from_node.NAME AS FROM_NODE, to_node.NAME AS TO_NODE
• FROM HR_NAVIGATION_PATHS np,
• HR_NAV_NODE_USAGES from_usage, HR_NAVIGATION_NODES from_node,
• HR_NAV_NODE_USAGES to_usage, HR_NAVIGATION_NODES to_node
• WHERE np.FROM_NAV_NODE_USAGE_ID = from_usage.NAV_NODE_USAGE_ID
• AND np.TO_NAV_NODE_USAGE_ID = to_usage.NAV_NODE_USAGE_ID
• AND from_usage.NAV_NODE_ID = from_node.NAV_NODE_ID
• AND to_usage.NAV_NODE_ID = to_node.NAV_NODE_ID;

Related Objects

The table has documented relationships with other key taskflow metadata tables, primarily through its foreign keys. The primary related object is the HR_NAV_NODE_USAGES table. Each record in HR_NAVIGATION_PATHS joins to this table twice:

• Join to HR_NAV_NODE_USAGES (From Node): HR_NAVIGATION_PATHS.FROM_NAV_NODE_USAGE_ID = HR_NAV_NODE_USAGES.NAV_NODE_USAGE_ID
• Join to HR_NAV_NODE_USAGES (To Node): HR_NAVIGATION_PATHS.TO_NAV_NODE_USAGE_ID = HR_NAV_NODE_USAGES.NAV_NODE_USAGE_ID

Furthermore, HR_NAV_NODE_USAGES itself references HR_NAVIGATION_NODES, which contains the definition of the actual task steps. Therefore, HR_NAVIGATION_PATHS sits at the center of the relational model that defines taskflow navigation, linking instances of node usage together to form a complete process map.