Search Results hr_navigation_units




Overview
Explore in AI Chat

Overview

The HR_NAVIGATION_UNITS table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically in versions 12.1.1 and 12.2.2. It serves as a repository for defining discrete navigation options within a taskflow. In essence, this table stores metadata that describes potential steps or units of work a user can navigate to during a business process, such as entering a new hire or updating an employee's details. Its primary role is to support the structured navigation and workflow logic of HR forms, enabling the system to manage complex, multi-step transactions by defining the available paths and their relationships.

Key Information Stored

The table's structure centers on identifying a navigation unit and linking it to the application interface and associated workflow logic. The primary key is the unique NAV_UNIT_ID. A unique key constraint on FORM_NAME and BLOCK_NAME directly ties each navigation unit to a specific form and block within the Oracle Forms interface, ensuring a precise mapping to a user-accessible screen component. A critical foreign key column is DEFAULT_WORKFLOW_ID, which references the HR_WORKFLOWS table. This column links the navigation unit to a default workflow process that may be invoked, defining the sequence of steps or approvals associated with that specific task. Other columns, not fully detailed in the excerpt but implied by the table's purpose, would typically store descriptive information, sequencing data, and status indicators for each navigation unit.

Common Use Cases and Queries

This table is primarily used for administrative configuration, troubleshooting, and reporting on HR taskflow navigation. A common use case involves analyzing the available navigation paths for a specific form to understand process dependencies. Developers or functional consultants may query the table to identify all navigation units associated with a particular workflow or to verify the configuration linking a form block to its default process. A typical diagnostic query would join HR_NAVIGATION_UNITS with HR_WORKFLOWS to list navigation points and their associated workflows.

SELECT hnu.nav_unit_id, hnu.form_name, hnu.block_name, hw.workflow_name
FROM hr_navigation_units hnu,
     hr_workflows hw
WHERE hnu.default_workflow_id = hw.workflow_id
AND hnu.form_name = 'PERWSFGI';

Another key use case is governed by the HR_INCOMPATIBILITY_RULES table, which uses this table to define rules preventing conflicting concurrent tasks (e.g., a promotion and a termination cannot be processed simultaneously for the same person).

Related Objects

The HR_NAVIGATION_UNITS table is central to the HR taskflow infrastructure, with documented relationships to several key tables:

  • HR_WORKFLOWS: Linked via HR_NAVIGATION_UNITS.DEFAULT_WORKFLOW_ID. Defines the default workflow process for the navigation unit.
  • HR_INCOMPATIBILITY_RULES: Linked twice: via FROM_NAV_UNIT_ID and TO_NAV_UNIT_ID. Stores rules that prevent two navigation units from being active concurrently.
  • HR_NAVIGATION_NODES: Linked via HR_NAVIGATION_NODES.NAV_UNIT_ID. Likely stores the individual nodes or steps within the broader navigation unit's path.
  • HR_NAV_UNIT_GLOBAL_USAGES: Linked via HR_NAV_UNIT_GLOBAL_USAGES.NAV_UNIT_ID. Governs the global availability or context usage of the navigation unit.

These relationships illustrate that HR_NAVIGATION_UNITS acts as a hub, connecting the definition of a taskflow step (the unit) to its rules, components, and execution workflow.