Introduction
How many times have you received questions like these?
- 👤 Who is this transaction currently with?
- ✅ Who already approved it?
- 📅 When was it assigned to each approver?
- ⏳ How many days did each approver take?
- 🔍 Can we see the complete approval history in one report?
Checking one or two transactions individually may be manageable. But when HR Operations, support teams, or auditors need to review hundreds of transactions, going through them one by one quickly becomes difficult.
That is exactly why I built this Oracle Fusion HCM Approval Audit Report.
The report brings together employee details, transaction information, the current or last approver, and the approval trail in a single output.
And yes, I am also sharing the BI Catalog file so you can use it as a starting point in your own Oracle Fusion environment. 🎁
📊 See the Complete Approval Trail in One Report
Instead of simply knowing whether a transaction is Pending, Approved, or Rejected, this report gives you deeper visibility into the approval journey.
The report provides information such as:
- Person Number
- Full Name
- Grade
- Business Unit
- Process Name
- Transaction Status
- Current/Last Approver
- Submitted By
- Submitted Date
- Completed Date
- Approver at each step
- Approval Action
- Assigned Date
- Action Date
- Action Days
For each approval step, the report can display:
Approver → Action → Assigned Date → Action Date → Action Days
The sample report shared in this blog has been designed with 10 approval-step columns as an example. This does not mean Oracle Fusion approvals are limited to 10 levels.
The actual number of approval steps can vary depending on each organisation’s approval rules and business requirements. Some transactions may have only a few approvers, while more complex approval flows may contain additional steps.
The report design can be extended or reduced accordingly.
🔍 See Who Approved, When They Approved and How Long They Took
This is where the report becomes especially useful.
For every approval step, you can see:
Approver → Action → Assigned Date → Action Date → Action Days
For example:
| Approval Step | Approver | Action | Assigned Date | Action Date | Days |
|---|---|---|---|---|---|
| Level 1 | Line Manager | Approved | 01-Sep | 02-Sep | 1 |
| Level 2 | Department Head | Approved | 02-Sep | 04-Sep | 2 |
| Level 3 | HR Manager | Assigned | 04-Sep |
Within seconds, you can understand who already completed the approval, what action was taken, when the task was assigned, how long each step took, and who the current or last approver is.
This makes the report useful not only for identifying pending transactions, but also for understanding completed approval history.
💡 Where Can This Report Help?
🔹 Find Stuck Approvals
When someone says:
“My transaction is stuck somewhere.”
the report gives you a quick way to review the approval activity and identify who currently has the transaction.
🔹 Approval Ageing
See how many calendar days each approval step took.
This can help identify transactions that are taking longer than expected.
🔹 Approval Bottleneck Analysis
If certain approval steps repeatedly take longer, the report provides the data needed to investigate where delays are happening.
🔹 Audit Support
The report brings together key approval information such as who submitted the transaction, who received the approval, what action was taken, when it was assigned, when the approver acted, and when the transaction was completed.
🔹 HR Operations Monitoring
Instead of checking transactions individually, HR Operations teams can periodically run the report and review approval activity across multiple transactions.
🎯 Simple Parameters, Powerful Output
The report uses only three main parameters:
| Parameter | Purpose |
|---|---|
| Process Name | Select the required HCM process |
| From Date | Transaction submitted from date |
| To Date | Transaction submitted to date |
Select the required process and date range, run the report, and review the approval details.
🧩 What Is Happening Behind the Report?
I wanted to keep the report technically useful without turning this blog into a SQL tutorial.
At a high level, the BI Publisher Data Model combines three key areas.
1️⃣ HCM Transaction Information
The report retrieves information such as:
- Process Name
- Transaction Status
- Submitted By
- Submitted Date
- Completed Date
2️⃣ Employee Information
The transaction is mapped back to the employee to retrieve information such as:
- Person Number
- Full Name
- Grade
- Business Unit
3️⃣ Workflow Approval Information
Workflow information is used to derive:
- Current/Last Approver
- Previous approvers
- Approval actions
- Assigned dates
- Action dates
- Approval ageing
All this information is consolidated into a single BI Publisher output.
🔄 One Report for HCM Approval Processes
One of the key advantages of this report is that it is not designed for only one HCM module or one approval process.
The report is designed as a common reporting solution across Oracle Fusion HCM approval processes.
Using the Process Name parameter, users can select the required HCM process and review its transaction and approval details from the same report.
This provides a common approach for analysing HCM approvals instead of creating separate reports for every individual process.
Whether the transaction originates from Core HR, Absence, Recruiting, Document of Records, or another HCM area, the objective remains the same:
One report to analyse HCM approval activity.
Depending on the underlying transaction object and configuration used in your environment, some processes may require additional mapping or adjustment in the Data Model.
⚙️ Important Notes Before You Use the Report
Every Oracle Fusion implementation is different, so some environment-specific adjustments may still be required.
A few important points to keep in mind:
Employee Information: The report retrieves the employee’s current assignment-related information.
Action Days: The calculation represents calendar days, not working days.
Approval Steps: The shared sample template contains 10 approval-step columns. These can be increased or reduced depending on your approval structure.
HCM Processes: The report is designed as a common HCM approval reporting solution, but specific transaction objects may require additional mapping depending on the process.
Security: Report results depend on the reporting and data access available in your environment.
I recommend initially testing the report with a small date range and validating a few known transactions before using it for wider reporting.
🖥️ Does This Replace Transaction Console?
No.
Transaction Console remains important when you need to investigate or troubleshoot an individual transaction.
The Approval Audit Report serves a different purpose.
| Transaction Console | Approval Audit Report |
|---|---|
| Review individual transactions | Analyse multiple transactions together |
| Troubleshoot specific workflow issues | Review approval history |
| Investigate transaction details | Analyse approval ageing |
| Perform administrative actions | Reporting and audit visibility |
The two complement each other.
❤️ Before You Download, One Small Request
I am sharing this report because approval reporting can take considerable time to develop, test, and validate.
If this report helps you or saves you some development effort, I have one small request:
🔄 Please reshare this blog on LinkedIn.
There may be another Oracle consultant searching for exactly the same solution.
Your reshare helps FusionPathFinder reach more members of the Oracle community and encourages me to continue sharing reusable reports, solutions, and practical Oracle Fusion content.
There is no mandatory verification or complicated process.
If you find the report useful, simply support it by sharing the blog with your network. 😊
📥 Download the Oracle Fusion HCM Approval Audit Report
Ready to try it?
🎁 Download the BI Catalog File
Use the shared catalog as a starting point, review the Data Model based on your environment, and validate the results before using it for business reporting.
I strongly recommend testing it in a non-production environment first.
🚀 Final Thoughts
A simple question such as:
“Who is this transaction currently with?”
can quickly lead to several more questions.
Who already approved it?
What action did they take?
When was it assigned?
How long did each approver take?
Who submitted it?
When was it completed?
Instead of checking all of this transaction by transaction, the Oracle Fusion HCM Approval Audit Report brings the information together in one place.
Submitted → Routed → Approved → Current/Last Approver → Completed
I hope this report saves you development time and provides a useful starting point for your own Oracle Fusion approval reporting requirements.
If you enhance the report further or extend the logic for additional scenarios, I would love to hear what you added!
Leave a Reply