Results for “workflow_name”

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

Overview

HR_WORKFLOWS is a table owned by the HR schema within the PER (Human Resources) product module of Oracle E-Business Suite. It stores the taskflows defined and used within Oracle HRMS, providing the central registry that the HR navigation and taskflow framework relies on to identify, resolve, and launch configured workflows. In EBS 12.1.1 and 12.2.2, the table acts as the authoritative reference for workflow identity, tying together navigation units, navigation node usages, and assignment-level processing logs.

Based on the heuristic Data Vault classification mined from its foreign-key structure, HR_WORKFLOWS is hub-leaning. This suggests a modeling approach in which WORKFLOW_ID functions as the stable hub key, with surrounding descriptive attributes (such as name and legislation) treated as satellite context, and dependent tables such as HR_NAVIGATION_UNITS and HR_NAVIGATION_NODE_USAGES representing link-style relationships that associate taskflows with navigation structures.

Key Information Stored

The documented physical schema for ETRM 12.2.2 contains four columns, with the following being operationally significant:

• WORKFLOW_ID — the surrogate primary key, defined by the index HR_WORKFLOWS_PK. It uniquely identifies each taskflow record and is the column referenced by all dependent foreign keys in the system.
• WORKFLOW_NAME — the business-key candidate, enforced by the unique index HR_WORKFLOWS_UK2. This is the human-readable identifier for the taskflow and is the primary search target for users querying the table by workflow_name.
• LEGISLATION_CODE — identifies the legislative context under which the taskflow applies, allowing statutory or country-specific taskflows to be distinguished from global ones.
• ZD_EDITION_NAME — the editions-based redefinition column. It participates in both unique indexes (HR_WORKFLOWS_PK and HR_WORKFLOWS_UK2), meaning uniqueness of both WORKFLOW_ID and WORKFLOW_NAME is scoped by edition, supporting EBS 12.2 online patching and editioning semantics.

Common Use Cases and Queries

The most frequent reason to query HR_WORKFLOWS is to resolve a workflow_name returned by the application into its numeric WORKFLOW_ID, or conversely to translate a stored WORKFLOW_ID into a readable taskflow name for reporting. A typical lookup by business key takes the following form:

• SELECT workflow_id, workflow_name, legislation_code FROM hr.hr_workflows WHERE workflow_name = :p_name;
• SELECT w.workflow_name, u.unit_name FROM hr.hr_workflows w, hr.hr_navigation_units u WHERE u.default_workflow_id = w.workflow_id; — reports which navigation units default to a given taskflow.
• SELECT n.node_id, w.workflow_name FROM hr.hr_navigation_node_usages n, hr.hr_workflows w WHERE n.workflow_id = w.workflow_id; — audits which nodes invoke each taskflow.

Because EBS 12.2 uses editions-based redefinition, queries in a patched environment should account for ZD_EDITION_NAME to avoid returning both the pre-patch and post-patch edition of a workflow row.

Related Objects

HR_WORKFLOWS participates in a small but well-defined dependency graph. The most significant related objects, per the documented foreign keys, are:

• HR_NAVIGATION_NODE_USAGES — references HR_WORKFLOWS via WORKFLOW_ID, recording where each workflow is used within navigation nodes.
• HR_NAVIGATION_UNITS — references HR_WORKFLOWS via DEFAULT_WORKFLOW_ID, establishing the default taskflow for each navigation unit.
• PV_ASSIGNMENT_LOGS — references HR_WORKFLOWS via WORKFLOW_ID, linking workflow execution history to assignments.

Together these tables make HR_WORKFLOWS a hub through which HRMS navigation configuration and assignment processing converge, and its unique indexes on WORKFLOW_ID and WORKFLOW_NAME (both scoped by ZD_EDITION_NAME) provide the integrity guarantees that downstream consumers depend upon.