Results for “hr_navigation_node_usages_uk1”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
HR.HR_NAVIGATION_NODE_USAGES is a seed-data intersection table in the Oracle E-Business Suite Human Resources (HR) schema. It resides in the APPS_TS_SEED tablespace, reflecting its role as a delivered, upgradeable reference construct rather than transactional data. Physically, the object records which navigation nodes are consumed by which workflows and, critically, identifies the entry point of a taskflow. As documented by ETRM, it is the intersection table between HR_WORKFLOWS, HR_NAVIGATION_NODES, and HR_NAVIGATION_PATHS, meaning it resolves the many-to-many relationships among workflows and the navigation nodes that make up a taskflow, while also participating in the parent/child path relationships defined in HR_NAVIGATION_PATHS.
From a heuristic Data Vault modeling perspective (mined from its foreign key structure), this table classifies as a link. It carries two foreign keys — WORKFLOW_ID and NAV_NODE_ID — and its unique business key spans exactly those two columns, which is the classic signature of a link entity connecting two hubs. The surrogate primary key NAV_NODE_USAGE_ID anchors the physical row, while the unique constraint enforces the business rule that a given navigation node may appear at most once per workflow.
Key Information Stored
The table is narrow, and its meaning is concentrated in a small set of columns:
- NAV_NODE_USAGE_ID — System-generated surrogate primary key (HR_NAVIGATION_NODE_USAGES_PK). It uniquely identifies each usage row and is referenced by HR_NAVIGATION_PATHS via the FROM_NAV_NODE_USAGE_ID and TO_NAV_NODE_USAGE_ID columns.
- WORKFLOW_ID — Foreign key to HR_WORKFLOWS. Identifies the workflow (taskflow) context in which the node is used. Part of the business-key candidate.
- NAV_NODE_ID — Foreign key to HR_NAVIGATION_NODES. Identifies the navigation node consumed within the workflow. Part of the business-key candidate.
- TOP_NODE — VARCHAR2(30). Flags the top node, i.e., the single entry point, of the taskflow. The documentation explicitly states that a taskflow can have only one entry point, so this column disambiguates the starting node from all others.
- ZD_EDITION_NAME — Editioning column present in the 12.2.2 physical schema. It participates in both the primary key and the unique index, supporting the Edition-Based Redefinition (EBR) model introduced with 12.2.
The business-key candidates are documented across two unique indexes. In 12.2.2 these are HR_NAVIGATION_NODE_USAGES_PK (NAV_NODE_USAGE_ID, ZD_EDITION_NAME) and HR_NAVIGATION_NODE_USAGES_UK1 (WORKFLOW_ID, NAV_NODE_ID, ZD_EDITION_NAME) — the object referenced in the user's search. The user's search term aligns directly with this UK1 unique key, whose purpose is to prevent duplicate node-to-workflow associations within an edition.
Common Use Cases and Queries
Because HR_NAVIGATION_NODE_USAGES is seed data, direct DML is unusual; it is normally queried to understand or troubleshoot taskflow configuration delivered by the HR self-service and navigation framework.
- Identifying taskflow entry points for a given workflow:
SELECT n.NAV_NODE_ID, n.NAV_NODE_NAME
FROM HR.HR_NAVIGATION_NODE_USAGES u
JOIN HR.HR_NAVIGATION_NODES n ON n.NAV_NODE_ID = u.NAV_NODE_ID
WHERE u.WORKFLOW_ID = :p_workflow_id
AND u.TOP_NODE IS NOT NULL;
- Resolving the navigation graph by joining to HR_NAVIGATION_PATHS on FROM_NAV_NODE_USAGE_ID and TO_NAV_NODE_USAGE_ID, which reconstructs the directed edges between usages and thus the full taskflow path.
- Validating seed integrity — detecting orphaned usages or, conversely, nodes defined without a workflow association.
- Upgrade impact analysis — reviewing which nodes each workflow consumes before patching or re-seeding the HR navigation model.
- Edition-aware reporting — filtering on ZD_EDITION_NAME is required in 12.2 to avoid double-counting nodes across editions.
Related Objects
- HR.HR_WORKFLOWS — joined on WORKFLOW_ID; the workflow/taskflow definition.
- HR.HR_NAVIGATION_NODES — joined on NAV_NODE_ID; provides node names and attributes.
- HR.HR_NAVIGATION_PATHS — references this table twice, through FROM_NAV_NODE_USAGE_ID and TO_NAV_NODE_USAGE_ID, defining allowed transitions between node usages.
- APPS.HR_NAVIGATION_NODE_USAGES and PUBLIC.HR_NAVIGATION_NODE_USAGES — dependent synonyms/grants exposing the table to the APPS and PUBLIC schemas.
- HR_NAVIGATION_NODE_USAGES_FK2 — the non-unique index on NAV_NODE_ID that supports lookups by node.
-
Intersection table between HR_WORKFLOWS, HR_NAVIGATION_NODES and HR_NAVIGATION_PATHS.
-
Intersection table between HR_WORKFLOWS, HR_NAVIGATION_NODES and HR_NAVIGATION_PATHS.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person