Results for “hr_navigation_paths”

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

Overview

HR_NAVIGATION_PATHS is a Human Resources (PER) module table in the Oracle E-Business Suite, owned by the HR schema. Its documented purpose is to store taskflow navigation path details, meaning it records the directed relationships (edges) between navigation nodes presented to end users in the EBS self-service and professional user interfaces. Rather than defining the nodes themselves, this table captures how one node leads to another, providing the routing backbone for HR taskflow components.

The table resides in the HR schema and is classified as VALID in the ETRM documentation for both 12.1.1 and 12.2.2. From a heuristic Data Vault modeling perspective, the object is classified as standalone, meaning it does not exhibit strong hub, link, or satellite characteristics through foreign key relationships to other documented objects. In practice, it functions most closely as a link-style construct, associating two navigation node usages, but the absence of registered foreign keys means it should be treated as an independent entity for integration and lineage modeling purposes.

Key Information Stored

The documented physical schema for 12.2.2 contains seven columns, of which the following are most significant:

• NAV_PATH_ID — the surrogate primary key that uniquely identifies each navigation path row. It forms the basis of the HR_NAVIGATION_PATHS_PK constraint.
• FROM_NAV_NODE_USAGE_ID — identifies the source navigation node usage from which the path originates. Together with the source key, it forms part of the business-key unique index HR_NAVIGATION_PATHS_UK1.
• TO_NAV_NODE_USAGE_ID — identifies the destination navigation node usage reached through the path. This is the second component of the unique business key.
• NAV_BUTTON_REQUIRED — a flag indicating whether a navigation button is required to traverse this path, governing presentation behavior.
• SEQUENCE — the ordinal position used to order multiple paths that share a common source node.
• OVERRIDE_LABEL — an optional label that overrides the default caption presented for the navigation action.
• ZD_EDITION_NAME — the editioning column introduced in the 12.2 online patching architecture. It is part of both the primary key (NAV_PATH_ID, ZD_EDITION_NAME) and the unique index (FROM_NAV_NODE_USAGE_ID, TO_NAV_NODE_USAGE_ID, ZD_EDITION_NAME).

Notably, the primary key is composite when editioning is considered, and the unique business-key candidate is defined by the source/destination pair rather than by the surrogate identifier alone.

Common Use Cases and Queries

Typical use cases include auditing taskflow configurations, diagnosing unexpected navigation behavior in self-service pages, and producing migration or comparison reports between environments. A representative query retrieves ordered outgoing paths for a given source node:

• SELECT nav_path_id, from_nav_node_usage_id, to_nav_node_usage_id, sequence, nav_button_required, override_label FROM hr.hr_navigation_paths WHERE from_nav_node_usage_id = :node_id ORDER BY sequence;
• A uniqueness audit validates the business key: SELECT from_nav_node_usage_id, to_nav_node_usage_id, COUNT(*) FROM hr.hr_navigation_paths GROUP BY from_nav_node_usage_id, to_nav_node_usage_id HAVING COUNT(*) > 1;
• An edition-aware comparison across patching cycles groups by ZD_EDITION_NAME to identify paths introduced or removed by an upgrade.

Because the table is standalone, reporting joins must be constructed explicitly against node usage and taskflow metadata rather than relying on enforced referential integrity.

Related Objects

Although no formal foreign keys are registered in the documented metadata, the following objects are logically related through the navigation identifiers held in this table:

• HR_NAV_NODE_USAGES — the primary logical parent, joined on FROM_NAV_NODE_USAGE_ID and TO_NAV_NODE_USAGE_ID.
• HR_NAV_NODES — defines the underlying navigation nodes referenced by node usage rows.
• HR_TASKFLOWS — the taskflow definitions whose routing is expressed through these paths.
• HR_TASKFLOW_STEPS — steps that correspond to navigation targets within a taskflow.
• FND_FORM_FUNCTIONS — functions invoked when navigation paths trigger a form or page action.
• FND_MENUS / FND_MENU_ENTRIES — menu structures that may parallel or reference taskflow navigation.

These associations should be treated as logical dependencies, since the ETRM metadata records HR_NAVIGATION_PATHS as a standalone object without enforced foreign key constraints.