Results for “workflow_id”

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

Overview

HR_NAVIGATION_NODE_USAGES is an Oracle E-Business Suite table owned by the HR schema and registered under the PER (Human Resources) product family. It functions as an intersection table that associates HR_WORKFLOWS, HR_NAVIGATION_NODES, and HR_NAVIGATION_PATHS, resolving the many-to-many relationship between navigation nodes and the workflows in which they participate. The table is classified as VALID in the ETRM 12.2.2 data dictionary and contains five documented columns.

From a dimensional modeling perspective, the mined foreign-key structure suggests a Data Vault classification of link. This is a heuristic recommendation rather than a definitive designation: the table carries no descriptive attributes of its own beyond structural identifiers, and its primary function is to record the association between two hub-like entities (workflows and navigation nodes). A designer mapping EBS HR self-service navigation to a Data Vault model would typically treat HR_NAVIGATION_NODE_USAGES as a link table connecting HR_WORKFLOWS and HR_NAVIGATION_NODES.

Key Information Stored

The table stores the relationship records that govern which navigation nodes appear within a given workflow, and at what position within the node hierarchy. The most important columns are:

• NAV_NODE_USAGE_ID — the surrogate primary key, sourced from the HR_NAVIGATION_NODE_USAGES_PK index. It uniquely identifies each usage record.
• WORKFLOW_ID — foreign key to HR_WORKFLOWS, identifying the workflow context in which the node is used. Part of the business-key candidate HR_NAVIGATION_NODE_USAGES_UK1.
• NAV_NODE_ID — foreign key to HR_NAVIGATION_NODES, identifying the specific navigation node being referenced. Also part of UK1.
• TOP_NODE — a flag or reference indicating whether the associated node serves as the top (root) node of the workflow navigation structure.
• ZD_EDITION_NAME — the editioning column introduced by the EBS 12.2 online patching architecture. It is included in both the primary key and the unique business key, making it essential to any query that must resolve the correct edition of the row.

The distinction between the surrogate key and the business key is significant. NAV_NODE_USAGE_ID provides row-level uniqueness, while the combination of WORKFLOW_ID, NAV_NODE_ID, and ZD_EDITION_NAME (HR_NAVIGATION_NODE_USAGES_UK1) enforces the business rule that a given node may appear at most once per workflow within an edition.

Common Use Cases and Queries

The primary use case is resolving which navigation nodes belong to a workflow, and how the node hierarchy is composed. A typical join pattern is:

• Join HR_NAVIGATION_NODE_USAGES to HR_NAVIGATION_NODES on NAV_NODE_ID = NODE_ID to retrieve node labels, functions, and form targets.
• Join to HR_WORKFLOWS on WORKFLOW_ID = WORKFLOW_ID to retrieve the workflow name or owner.
• Filter on ZD_EDITION_NAME to constrain results to the active edition when reporting against a 12.2.2 environment.

Representative SQL:

SELECT u.NAV_NODE_USAGE_ID, w.WORKFLOW_ID, n.NODE_ID, n.NODE_NAME, u.TOP_NODE
FROM HR.HR_NAVIGATION_NODE_USAGES u,
     HR.HR_WORKFLOWS w,
     HR.HR_NAVIGATION_NODES n
WHERE u.WORKFLOW_ID = w.WORKFLOW_ID
  AND u.NAV_NODE_ID = n.NODE_ID
  AND u.ZD_EDITION_NAME = 'ORA$BASE';

Common reporting scenarios include auditing workflow composition for HR self-service responsibilities, verifying that a newly registered function is reachable through an expected navigation path, and diagnosing missing menu entries after a patch or configuration change. On 12.1.1, the ZD_EDITION_NAME predicate is not applicable and should be omitted.

Related Objects

The following objects are most directly relevant based on the documented foreign keys and the intersection-table role:

• HR_WORKFLOWS — referenced via WORKFLOW_ID; defines the workflow that owns the node usage.
• HR_NAVIGATION_NODES — referenced via NAV_NODE_ID; defines the node record itself.
• HR_NAVIGATION_PATHS — the third member of the documented intersection relationship; describes the navigable path traversing node usages.
• HR_NAVIGATION_NODE_USAGES_PK — unique index enforcing row uniqueness on NAV_NODE_USAGE_ID and ZD_EDITION_NAME.
• HR_NAVIGATION_NODE_USAGES_UK1 — unique index enforcing the business key on WORKFLOW_ID, NAV_NODE_ID, and ZD_EDITION_NAME.

These objects collectively support the HR self-service navigation framework, and any query against HR_NAVIGATION_NODE_USAGES will almost invariably require joins to HR_WORKFLOWS and HR_NAVIGATION_NODES to produce meaningful business output.