Oracle Fusion HCM Workflow Tables Guide

Share

Oracle Fusion HCM Workflow Tables are an important topic for consultants who work with approvals, BPM workflows, and transaction processing in Oracle Fusion Cloud. In any Oracle Fusion HCM implementation, employee-related transactions such as promotions, transfers, salary changes, hiring, and terminations usually trigger approval workflows. These workflows are handled by the Oracle BPM engine behind the scenes, and the details are stored in several workflow tables in the Fusion database.

Understanding Oracle Fusion HCM Workflow Tables is extremely useful for technical consultants, report developers, and integration specialists who need to troubleshoot workflow issues, build BI reports, or analyze approval history.

For example, when an employee submits a promotion request, the system triggers an approval workflow that might go to the line manager, HR manager, and finance team. Each approval action and workflow stage is recorded in backend workflow tables. Technical consultants often query these tables to determine:

  • Who approved a transaction

  • When the approval happened

  • Current workflow status

  • Pending approvers

  • Historical workflow audit details

In this article, we will explore Oracle Fusion HCM Workflow Tables from an implementation perspective, including architecture, key tables, how they are used in reporting, and practical troubleshooting scenarios.


What are Oracle Fusion HCM Workflow Tables?

Oracle Fusion HCM Workflow Tables store information related to workflow execution, approval tasks, workflow history, and workflow states within the Fusion application.

These tables are primarily associated with the Oracle BPM Workflow Engine, which manages approval processes across Oracle Fusion applications including HCM, Financials, Procurement, and SCM.

When a workflow is triggered, the system performs the following steps:

  1. Creates a workflow instance

  2. Assigns approval tasks

  3. Sends notifications to approvers

  4. Tracks approval actions

  5. Updates workflow status

  6. Stores history and audit information

All these actions are recorded in backend workflow tables that can be accessed through BI Publisher reports, OTBI, or custom SQL queries.

These workflow tables are usually located in the SOA and BPM schemas, but Oracle exposes them through Fusion reporting tools.


Key Oracle Fusion HCM Workflow Tables

Below are some of the most commonly used workflow tables in Oracle Fusion HCM.

Table NameDescription
WFTASKStores workflow task information
WFTASKHISTORYStores workflow history records
WFASSIGNEEStores information about task assignees
WFROUTINGSLIPStores routing information for workflow tasks
WFCOMMENTSStores approval comments
WFTASKVERSIONStores version details of workflow tasks
WFATTACHMENTStores attachments related to workflow tasks

These tables allow consultants to retrieve detailed workflow data such as approval hierarchy, approvers, comments, and workflow states.


Understanding Workflow Architecture in Oracle Fusion

To understand workflow tables, it is important to understand how the Oracle BPM workflow engine operates.

The typical workflow lifecycle looks like this:

  1. User submits transaction

  2. Transaction triggers BPM workflow

  3. Workflow instance is created

  4. Approval tasks are assigned

  5. Approvers receive notifications

  6. Approvers approve or reject

  7. Workflow completes

The workflow engine maintains detailed audit records for each stage.

Example architecture:

 
User Transaction

Business Process Trigger

BPM Workflow Engine

Workflow Instance Created

Approval Tasks Generated

Approver Actions Recorded

Workflow Tables Updated
 

Each stage of this process updates multiple workflow tables.


Real-World Integration Use Cases

Understanding workflow tables becomes critical in several real-world Oracle Fusion implementations.

Use Case 1 — Workflow Approval Report

A customer wanted a report showing:

  • Employee transaction

  • Approver name

  • Approval date

  • Approval status

To build this report, consultants extracted data from:

  • WFTASK

  • WFASSIGNEE

  • WFTASKHISTORY

The report was developed using BI Publisher.


Use Case 2 — Troubleshooting Stuck Workflows

In some implementations, approval workflows get stuck due to configuration issues.

A technical consultant can query workflow tables to identify:

  • Current workflow state

  • Pending approver

  • Task status

Example SQL logic:

 
SELECT taskid,
tasknumber,
state,
assigneddate
FROM wftask
WHERE state = ‘ASSIGNED’
 

This helps identify pending approvals.


Use Case 3 — Audit Tracking for Compliance

Large enterprises require audit trails for approval transactions.

Workflow tables help auditors track:

  • Who approved the transaction

  • When approval happened

  • What comments were entered

Audit reports are commonly built using WFTASKHISTORY and WFCOMMENTS tables.


Workflow Architecture and Technical Flow

Below is the simplified workflow flow in Oracle Fusion.

Step 1 — Transaction Creation

Example:

Employee submits promotion request.

The transaction is stored in the HCM transaction tables.


Step 2 — Workflow Trigger

The transaction triggers a BPM workflow process.

Example workflow name:

 
HcmApprovalTask
 

Step 3 — Workflow Instance Creation

The system creates a workflow instance.

The instance ID is stored in workflow tables.


Step 4 — Task Assignment

Approval tasks are assigned to approvers.

This information is stored in:

  • WFASSIGNEE

  • WFTASK


Step 5 — Approval Action

Approvers can perform actions such as:

  • Approve

  • Reject

  • Request information

  • Reassign

These actions are stored in WFTASKHISTORY.


Important Workflow Tables Explained

1. WFTASK

The WFTASK table is the main workflow table that stores task-level information.

Key columns include:

ColumnDescription
TASKIDUnique identifier for workflow task
TASKNUMBERTask number
STATECurrent state of workflow
ASSIGNEDDATEDate task was assigned
UPDATEDDATELast update date

Example query:

 
SELECT tasknumber,
state,
assigneddate
FROM wftask
 

Common workflow states include:

  • ASSIGNED

  • COMPLETED

  • WITHDRAWN

  • REJECTED


2. WFTASKHISTORY

This table stores historical records of workflow actions.

Each approval step is recorded here.

Key columns include:

ColumnDescription
TASKIDWorkflow task ID
OUTCOMEApproval outcome
UPDATEDDATEApproval date
UPDATEDBYApprover

Example query:

 
SELECT outcome,
updatedby,
updateddate
FROM wftaskhistory
 

This table is commonly used in approval history reports.


3. WFASSIGNEE

This table stores the list of users assigned to workflow tasks.

Key columns include:

ColumnDescription
TASKIDWorkflow task ID
ASSIGNEEUser assigned
ASSIGNEETYPERole or user

Example use case:

Find current approver.


4. WFCOMMENTS

Stores comments entered by approvers during approval actions.

Example comment:

 
Approved based on budget availability
 

Example query:

 
SELECT commenttext
FROM wfcomments
 

5. WFATTACHMENT

Stores workflow attachments such as supporting documents submitted during approval.

Example:

  • Promotion justification document

  • Salary approval sheet


Prerequisites for Accessing Workflow Tables

Before accessing workflow tables, the following prerequisites should be available.

Required Access

  • BI Publisher access

  • OTBI reporting access

  • Database query access via data models

Required Knowledge

Consultants should understand:

  • Fusion BPM workflows

  • HCM transactions

  • SQL joins

  • BI Publisher report development


Step-by-Step Example — Building a Workflow Approval Report

Let’s walk through a typical reporting scenario.

Step 1 — Identify Workflow Tables

Common tables used:

  • WFTASK

  • WFASSIGNEE

  • WFTASKHISTORY


Step 2 — Create BI Publisher Data Model

Navigation:

 
Navigator → Tools → Reports and Analytics
 

Create a new Data Model.


Step 3 — Write SQL Query

Example SQL:

 
SELECT
WT.TASKNUMBER,
WT.STATE,
WA.ASSIGNEE,
WH.OUTCOME,
WH.UPDATEDDATE
FROM
WFTASK WT,
WFASSIGNEE WA,
WFTASKHISTORY WH
WHERE
WT.TASKID = WA.TASKID
AND WT.TASKID = WH.TASKID
 

Step 4 — Create Report Layout

Use BI Publisher layout options such as:

  • Table format

  • Approval history view

  • Approver timeline


Step 5 — Test the Report

Run the report with sample workflow transactions.

Expected output:

Task NumberApproverStatusApproval Date
123456John ManagerApproved12-Mar-2026

Testing Workflow Data

When testing workflow-related reports, consultants should validate the following:

Test Scenario

Employee submits promotion request.

Steps:

  1. Submit transaction

  2. Manager receives approval

  3. Manager approves

Check workflow tables.

Expected validation:

  • Workflow task created

  • Approver recorded

  • Approval outcome updated


Common Errors and Troubleshooting

Issue 1 — Workflow Stuck in Assigned State

Cause:

Approver has not taken action.

Solution:

Check WFTASK.STATE.


Issue 2 — Missing Approval History

Cause:

Incorrect join between tables.

Solution:

Join using TASKID.


Issue 3 — Incorrect Approver Display

Cause:

Incorrect column mapping.

Solution:

Check WFASSIGNEE.ASSIGNEE column.


Best Practices for Working with Workflow Tables

Experienced Oracle consultants typically follow these practices.

1. Use BI Publisher Instead of Direct SQL Access

Direct database queries are not recommended in production environments.


2. Join Tables Carefully

Workflow tables contain large volumes of data.

Always filter using:

  • TASKNUMBER

  • CREATIONDATE


3. Avoid Full Table Queries

Example:

Bad practice:

 
SELECT * FROM WFTASK
 

Instead use filters.


4. Use Workflow Analytics

Fusion provides built-in workflow analytics dashboards.

These should be used where possible.


5. Understand Workflow Lifecycle

Consultants should understand:

  • Workflow initiation

  • Approval routing

  • Task completion

This knowledge helps in troubleshooting issues faster.


Summary

Oracle Fusion HCM Workflow Tables play a critical role in managing and tracking approval processes across the application. They store detailed information about workflow tasks, approvers, approval history, comments, and attachments.

For technical consultants, understanding these tables is extremely valuable when building reports, troubleshooting workflows, and analyzing approval transactions.

The most important workflow tables include:

  • WFTASK

  • WFTASKHISTORY

  • WFASSIGNEE

  • WFCOMMENTS

  • WFATTACHMENT

By understanding the structure and relationships between these tables, consultants can efficiently develop workflow reports, analyze approval flows, and resolve workflow issues during Oracle Fusion implementations.

For additional reference and detailed workflow documentation, Oracle provides official documentation here:

https://docs.oracle.com/en/cloud/saas/index.html


FAQs

1. What are Oracle Fusion HCM Workflow Tables used for?

Oracle Fusion HCM Workflow Tables store information about workflow approvals, tasks, approvers, and approval history generated during HCM transactions.


2. Which table stores workflow approval history?

The WFTASKHISTORY table stores detailed workflow approval history including approver actions and approval outcomes.


3. Can workflow tables be used in BI Publisher reports?

Yes. Workflow tables such as WFTASK, WFASSIGNEE, and WFTASKHISTORY are commonly used in BI Publisher reports to build approval tracking and workflow audit reports.


Share

Leave a Reply

Your email address will not be published. Required fields are marked *