Script Library › HCM › HCM-03
HCM-03 Oracle Fusion Cloud HCM Guided Actions

Payroll Run Diagnostic (Oracle Fusion)

Fusion payroll diagnostics via OTBI, REST HCM API, and BIP — run action status, error counts, assignment action detail, ESS job history for Calculate Payroll and Prepayments.

Get Full Script → ← Back to Library
PlatformOracle Fusion Cloud
Input RequiredPayroll Flow Name or Legal Entity
Diagnostic ChecksOTBI + REST + BIP
Data SourcesOTBI / REST / BIP
Fix OptionsGuided UI Actions
The Problem

Why This Fails — and What It Costs

Oracle Fusion HCM Payroll processing diagnostics are performed through a structured set of Fusion tools rather than direct database queries. The Fusion Payroll Flow framework manages payroll processing as a series of tasks — Calculate Payroll, Calculate QuickPay, Verify Payroll Results, Calculate Prepayments, Archive Payroll Results, Transfer to Subledger Accounting. Each task runs as a Scheduled Process (ESS job) and produces a structured output that can be reviewed through the Payroll Flow Monitor, downloaded as a BIP report, or queried through OTBI Payroll subject areas.

The Fusion Payroll Flow Monitor is the primary diagnostic interface. It shows every task in the payroll flow with its status — Completed, Error, Corrective Action Required — and the employee count processed, completed, and in error at each stage. For tasks with errors, the Monitor links directly to the error detail log, which identifies the specific employee, the element, and the calculation error message. HCM-03 uses the Payroll Flow Monitor as the first diagnostic step, followed by the BIP Payroll Error Report for structured error analysis, and OTBI Payroll subject areas for population-level analysis.

Fusion Payroll element entry errors are diagnosed through the Manage Element Entries screen rather than direct PAY_ELEMENT_ENTRIES_F queries. The Fusion REST API provides the /payroll/elementEntries endpoint for programmatic access. When a payroll formula error occurs — because an element formula references a value input that has been changed or a fast formula has been incorrectly compiled — the Payroll Flow Monitor shows the error message and the Correct Payroll Results task allows the payroll team to correct element entries and reprocess the affected employees without rolling back the entire payroll run.

HCM-03 provides a structured Fusion Payroll diagnostic using the Payroll Flow Monitor for task-level status, BIP Payroll Error Report for employee-level error detail, OTBI Payroll Results subject area for population analysis, Manage Element Entries for element entry review, and the Payroll Costing Report for GL allocation completeness.

Diagnostic Coverage

What This Script Diagnoses

HCM-03 systematically investigates every major condition that can cause the issue this diagnostic targets. Below is the complete coverage breakdown.

Payroll Flow Monitor
Task-by-task status across the full payroll flow — Calculate Payroll, Calculate Prepayments, Archive, Transfer to SLA. Error count per task. Direct link to error detail log for each failing task.
BIP Payroll Error Report
Employee-level error detail — employee name, element, formula error message, and the specific input value or database item that caused the failure. The primary structured error source for formula diagnostics.
OTBI Payroll Results
Population-level payroll result analysis — costing exceptions (employees charged to suspense), retroactive elements, zero or negative net pay. Identifies systemic issues affecting multiple employees that may not surface as explicit errors.
Costing & GL Transfer
Payroll Costing Report for GL allocation completeness. Transfer to Subledger Accounting ESS status. SLA Create Accounting BIP Execution Report for accounting errors. Confirms payroll costs are fully journalized before period close.
Sample Diagnostic Output

Example Completed Worksheet

Completed diagnostic worksheet showing what the full diagnostic picture looks like after all steps have been worked through. Your worksheet will reflect your environment's specific data — the steps, tool sequence, and REST API calls to assemble it are documented in the Audit Trail section below.

HCM-03 — HCM-03 Fusion Diagnostic 
════════════════════════════════════════════════════════════
  ORACLE FUSION — PAYROLL RUN DIAGNOSTIC
════════════════════════════════════════════════════════════
  Payroll Flow       : US Monthly Payroll FEB-2026
  Legal Entity       : US Incorporated
  Flow Status        : In Progress — Corrective Action Required
  Case Number        : FC-HCM-2026-0310
  Report Date        : 22-FEB-2026 09:15:44
════════════════════════════════════════════════════════════

[ STEP 1 — PAYROLL FLOW MONITOR ]
────────────────────────────────────────────────────────────
  Calculate Payroll   : Completed with Errors — 3 of 842 in error ✗
  Calculate PrePaymts : Pending — waiting for errors to be resolved
  Transfer to SLA     : Pending

[ STEP 2 — BIP PAYROLL ERROR REPORT ]       STATUS: ✗ ERRORS
────────────────────────────────────────────────────────────
  EMP-10481          : BONUS element — formula error: input value GRADE_STEP not found ✗
  EMP-10492          : OVERTIME element — rate formula error ✗
  EMP-10510          : BONUS element — same formula error as EMP-10481 ✗

[ STEP 3 — OTBI PAYROLL RESULTS ]           STATUS: ⚠ WARNING
────────────────────────────────────────────────────────────
  ⚠ 12 employees: costing defaulted to suspense — Payroll Costing Report shows gaps

[ STEP 4 — MANAGE ELEMENT ENTRIES ]
────────────────────────────────────────────────────────────
  BONUS element entry : GRADE_STEP input value — removed in FEB setup change
  Replacement input   : GRADE_BAND — defined 01-FEB-2026

════════════════════════════════════════════════════════════
  FUSION DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  3 employees in error — GRADE_STEP input removed without formula update
  FIX: Update formula via Fast Formulas, use Correct Payroll Results to reprocess
════════════════════════════════════════════════════════════
How the Diagnostic Works

The Four-Layer Architecture in HCM-03

1
Diagnostic Steps
Fusion Payroll diagnostic using Payroll Flow Monitor for task-level status, BIP Payroll Error Report for employee-level error identification, OTBI Payroll Results subject area for population analysis and costing exceptions, Manage Element Entries for element entry review, and the Payroll Costing Report for GL allocation completeness.
2
Backup Created
Fusion Cloud does not permit direct database access. Payroll Flow Monitor export and BIP Payroll Error Report are saved before any corrective action as the pre-action state record.
3
Guided Data Fix
Formula corrections via Payroll > Fast Formulas. Element entry corrections via Manage Element Entries. Affected employee reprocessing via Correct Payroll Results — no full payroll rollback required. Costing gaps corrected via Payroll Costing setup.
4
KB Article Generated
Complete KB article from Payroll Flow Monitor and BIP Payroll Error Report — flow name, error employees, formula issue, correction applied, reprocessing result.
Audit Trail

Documentation Before Every Action — HCM-03

Fusion Cloud does not permit direct database access. Every corrective action goes through a supported Oracle interface. Before any action is taken, the current state is exported and documented.

Pre-Action Documentation — HCM-03

Payroll Flow Monitor export — task status before any action
BIP: Payroll Error Report — employee-level errors saved
OTBI: Payroll Results — costing exception export

Exported before any UI action, ESS resubmission, or FBDI reimport. Provides a point-in-time record of the error state for the KB article and SR documentation if needed.

Pre-Action Verification

Fusion tenant accessibleConfirmed ✓
Payroll Flow Monitor retrievedStatus exported ✓
BIP Payroll Error Report runSaved ✓
OTBI Payroll Results export completedSaved ✓
Calculate Prepayments not yet runConfirmed ✓

Audit Trail Record

CASE_NUMBER<consultant case#>
DIAGNOSTIC_TOOL<OTBI / REST API / BIP / ESS>
ERROR_SNAPSHOT<exported before action>
ACTION_TAKEN<UI path / ESS program / FBDI>
RESULT_VERIFIEDYES ✓

No Direct DB Access — By Design

Oracle Fusion Cloud is a SaaS environment. There is no consultant-accessible Oracle schema, no SQL*Plus connection, and no CONS_BACKUP tablespace. All diagnostic and corrective activity goes through OTBI, REST APIs, BIP reports, ESS programs, and the Fusion UI — the same supported tools Oracle Support uses.

REST API Reference — Endpoints Used in This Diagnostic

All API calls use OAuth 2.0 authentication. The base URL is your Fusion Cloud instance URL. Replace {instanceName} with your tenant name. Obtain the OAuth token via the /oauth/token endpoint using client credentials.

GETPayroll Flow Status
/hcmRestApi/resources/11.13.18.05/payrollFlows/{FlowInstanceId}
Path Parameters
FlowInstanceId string — Fusion internal flow instance ID. Find from Payroll Flow Monitor or the collection GET filtered by payroll name and period.
Key Query Parameters
fields FlowInstanceId,FlowName,Status,StartDate,CompletionDate,LegalEntityName
Response Fields Read
Status — InProgress, Completed, CompletedWithErrors, Error
FlowName — the payroll flow definition name
CompletionDate — when the flow finished (null if still running)
LegalEntityName — legal entity the payroll run belongs to
GETPayroll Element Entries
/hcmRestApi/resources/11.13.18.05/payrollElementEntries
Key Query Parameters
q filter — PersonNumber={personNumber};PayrollName={payrollName};EffectiveStartDate>={periodStart}
fields ElementName,InputValueName,ScreenEntryValue,EffectiveStartDate,EffectiveEndDate,PersonNumber
Response Fields Read
ElementName — the payroll element, e.g. Annual Salary, Bonus, Overtime
InputValueName — the input value within the element, e.g. GRADE_STEP
ScreenEntryValue — the entered value — amount, rate, or flag
EffectiveStartDate, EffectiveEndDate — date range for the entry
Layer 4 Output

Auto-Generated Knowledge Base Article

This article is produced automatically at the end of every HCM-03 execution — written from actual run output. No manual documentation required.

KB-FC-HCM-0310-001 · Script: HCM-03
Fusion Payroll FEB-2026 — 3 Employees in Error: GRADE_STEP Input Value Removed
Module: HCM
Platform: Oracle Fusion Cloud
Status: RESOLVED
Symptom
US Monthly Payroll FEB-2026 flow shows Calculate Payroll completed with 3 errors. BIP Payroll Error Report identifies BONUS element formula error for EMP-10481, EMP-10492, EMP-10510 — input value GRADE_STEP not found. Calculate Prepayments pending.
Root Cause
Payroll setup change on 01-FEB-2026 removed the GRADE_STEP input value from the Grade element and replaced it with GRADE_BAND. The BONUS_CALC formula was not updated to reference the new input value name. 3 employees on the BONUS element affected.
Tables Affected
Payroll Flow Monitor: Calculate Payroll — Status: Completed with Errors, Error Count: 3
BIP Payroll Error Report: EMP-10481/10492/10510 — BONUS element, input value GRADE_STEP not found
Fix Applied
BONUS_CALC formula updated via Fast Formulas — GRADE_STEP reference replaced with GRADE_BAND. Correct Payroll Results submitted for 3 employees — all reprocessed successfully. Calculate Prepayments submitted and completed. Transfer to Subledger Accounting complete.
Prevention
Payroll setup change control: any input value rename or removal must include a Fast Formula impact check before the change is applied. Payroll parallel test run must complete without errors before live payroll submission.
Tags
Fusion HCMPayrollFlow MonitorFormula ErrorCorrect Payroll ResultsBIP Error ReportOracle Fusion Cloud
Common Issues

What This Script Finds

Formula

Input Value Not Found After Setup Change

Payroll setup change removed or renamed an input value that a Fast Formula still references. BIP Payroll Error Report shows the specific formula and input. Correction via Fast Formulas and Correct Payroll Results — no full run rollback needed.

Costing

Costing Defaulted to Suspense

No costing rule defined for an element-department combination. Payroll costs charged to the suspense account. Finance discovers at month-end reconciliation. HCM-03 identifies the gap from the OTBI Payroll Costing Report.

Payment

Calculate Prepayments Failure

Employee payment source invalid — bank account closed, payment method end-dated, or prenote not completed. HCM-03 identifies the employee and the payment source issue from the Flow Monitor error detail.

SLA

Transfer to Subledger Accounting Error

SLA Create Accounting error for payroll — typically an invalid account in the costing setup. HCM-03 identifies the account from the BIP Create Accounting Execution Report and the correction path.

Data Layer

Tables Examined

Data SourceTypePurpose
Payroll Flow MonitorFusion UITask-level status — errors, pending, complete
BIP: Payroll Error ReportBIPEmployee-level formula errors and element detail
OTBI: Payroll ResultsOTBIPopulation analysis — costing exceptions, zero pay
OTBI: Payroll Costing ReportOTBIGL allocation completeness — suspense account charges
REST API: /payroll/elementEntriesRESTElement entry detail for affected employees
ESS: Transfer to Subledger AccountingESSGL transfer status and error output
Decision Framework

How Every Resolution Decision Is Made

Every condition identified by the diagnostic maps to exactly one resolution path. In Fusion Cloud, all paths go through supported Oracle interfaces — UI, REST API, FBDI, or ESS. Direct database access does not exist in this environment.

1
First Option — Always
Can the Fusion UI resolve this?

Oracle's own Fusion screens, Scheduled Processes (ESS), and workflow tools are always the first resolution path. Manage Invoices, Manage Suppliers, Manage Accounting Periods, BPM Worklist, Scheduled Processes — the diagnostic identifies the exact navigation path and screen sequence for every condition that can be resolved this way. No third-party tools, no API calls, no risk beyond what Oracle's own UI carries.

✓ Functional First
2
When the UI Path Is Insufficient
Can a REST API PATCH or FBDI reimport resolve this?

For bulk corrections or conditions not surfaced in the standard UI, Oracle Fusion's public REST APIs and FBDI import templates are the supported programmatic path. A REST API PATCH call to correct an invoice distribution account, an FBDI resubmission with corrected records after an import failure, or a Mass Update via the REST API — these are supported, documented, and reversible through normal Oracle mechanisms. The current state is exported before any API call is made.

→The API endpoint is an Oracle-published, versioned REST resource
→The FBDI template matches the current Fusion release version
→The pre-action state is exported (OTBI report / GET response) before the PATCH or import runs
→The result is verified via a follow-up GET or OTBI query before the case is closed
⚡ API / FBDI
3
Hard Stops — No Exceptions
Does this require Oracle Support?

Certain conditions in Fusion Cloud cannot be resolved through any customer-accessible interface. The diagnostic flags these and generates the Service Request documentation:

✗ESS job infrastructure failures — job status Error (not Completed with Warnings) indicating an engine-level issue not caused by data
✗Subledger accounting engine errors — Create Accounting failures where the error is in the Oracle accounting engine, not in the source transaction data
✗Recurring failures after correct setup — a condition that returns after a confirmed correct resolution indicates a code defect, submitted as an SR with a reproducible test case
✗Fusion data corruption — records in an inconsistent internal state not reachable through any published API or UI action
⚠ Oracle Support
4
For All Actions Taken
Export → Act → Verify → Document

Before any UI action, ESS resubmission, REST API call, or FBDI reimport — the current error state is exported via OTBI report, BIP report output, or REST API GET response. After the action, a verification step confirms the expected outcome. The complete sequence — tool used, pre-action state, action taken, result verified — is written into the KB article as the primary record of what was done and why.

📋 Documented
Condition Identified Resolution Path Notes
Formula error — input value not found after setup change Functional First Update the formula via Payroll > Fast Formulas. HCM-03 identifies the failing formula from the BIP Payroll Error Report and the correct input value from the current element setup.
Affected employees need reprocessing Functional First Use Correct Payroll Results to reprocess affected employees without rolling back the full run. HCM-03 identifies the employees and the task parameters for the Correct Payroll Results submission.
Costing defaulted to suspense — hierarchy gap Functional First Define the costing rule via Payroll > Payroll Costing for the element-department combination. HCM-03 identifies the gap from the Payroll Costing Report in OTBI.
Calculate Prepayments failing — payment source invalid Functional First Correct the payment source (bank account or check writer) via Manage Personal Payment Methods. HCM-03 identifies the employee and the invalid payment source from the Flow Monitor error detail.
Transfer to Subledger Accounting errors Functional First Correct the account via Manage Chart of Accounts, then resubmit Transfer to Subledger Accounting. HCM-03 identifies the error from the SLA Create Accounting BIP Execution Report.
Payroll flow task stuck in Pending Functional First Identify the blocking prior task in the Flow Monitor. Resubmit or rollback the blocking task via the Flow Monitor Actions menu. HCM-03 identifies the task dependency chain.
Element entry missing for employee Functional First Add the element entry via Manage Element Entries. HCM-03 identifies the missing element from the payroll results comparison — employees with the element in prior periods but not the current period.
Payroll flow task in Error status — engine failure Oracle Support SR ESS task status Error (not Completed with Errors) indicates an engine-level issue. HCM-03 documents the task ID and error log for the Oracle Support SR.
Safeguards

Nothing Acts Without a Documented State

Fusion Cloud's SaaS architecture eliminates direct database access — which means every action is a supported Oracle API call, UI operation, or ESS submission. Before any action runs, the current error state is captured. After any action, the result is verified.

Pre-Action Documentation — All Completed First
✓
Payroll Flow Monitor export — task status before any action
Exported before any corrective action is taken
✓
BIP: Payroll Error Report — employee-level errors saved
Exported before any corrective action is taken
✓
OTBI: Payroll Results — costing exception export
Exported before any corrective action is taken
✓
Post-action verification
Follow-up OTBI query or REST GET confirms the expected state before the case is closed
Fusion Audit Trail — What Replaces CONS_BACKUP

In EBS R12, a CONS_BACKUP table provides the rollback point. In Fusion Cloud, the equivalent audit trail is built from three sources that together give a complete before-and-after record:

BEFORE STATE
OTBI report export or REST API GET response saved as the pre-action snapshot
ACTION RECORD
Fusion audit trail (Setup and Maintenance > Audit Reports) captures every UI and API change with user, timestamp, old value, and new value
AFTER STATE
Post-action OTBI query or REST GET confirms the fix — this output becomes the KB article verification artifact
HCM-03 — Fusion Diagnostic Framework 
════════════════════════════════════════════════════════════
  ORACLE FUSION — PAYROLL DIAGNOSTIC STEPS
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud HCM
  Tools              : Payroll Flow Monitor, BIP Error Report, OTBI, Manage Elements
  Pre-Action Export  : Flow Monitor status and BIP Error Report saved
────────────────────────────────────────────────────────────
  Step 1 — Flow Monitor : Calculate Payroll — 3 errors identified, task detail retrieved ✓
  Step 2 — BIP Report   : Payroll Error Report — 3 employees, GRADE_STEP input error ✓
  Step 3 — OTBI         : Payroll Results — 12 costing defaults to suspense identified ✓
  Step 4 — Element Setup: GRADE_STEP removed, GRADE_BAND replacement confirmed ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — Formula correction and Correct Payroll Results path identified
════════════════════════════════════════════════════════════
  Documentation      : KB article from Flow Monitor and BIP output
  Fusion Audit Trail : Fast Formula changes logged in Fusion audit trail
  SR Reference       : N/A — resolved via Fast Formulas and Correct Payroll Results
════════════════════════════════════════════════════════════
Knowledge Base

Every Execution Produces a Record

The knowledge base article is generated automatically from the script's execution output. No manual documentation required. It becomes the institutional record — for the team, for auditors, and for every future engagement in the same environment.

Zero Manual Effort
Every field — environment, tables, before/after values, backup reference, root cause, prevention — is generated from actual execution output. Nothing is written by hand.
Patterns Surface Over Time
The first engagement produces findings. The third produces patterns. Recurring conditions that are invisible as individual incidents become obvious as knowledge base trends.
Survives Staff Turnover
The knowledge base is an institutional record of the Oracle environment. A new manager, a new DBA, or an external auditor can read exactly what happened, what was done, and what prevents recurrence.
KB-FC-HCM-0310-001
Fusion Payroll FEB-2026 — 3 Employees in Error: GRADE_STEP Input Value Removed
Oracle Fusion Cloud · HCM
● RESOLVED
Symptom
US Monthly Payroll FEB-2026 flow shows Calculate Payroll completed with 3 errors. BIP Payroll Error Report identifies BONUS element formula error for EMP-10481, EMP-10492, EMP-10510 — input value GRADE_STEP not found. Calculate Prepayments pending.
Root Cause
Payroll setup change on 01-FEB-2026 removed the GRADE_STEP input value from the Grade element and replaced it with GRADE_BAND. The BONUS_CALC formula was not updated to reference the new input value name. 3 employees on the BONUS element affected.
Tables
Payroll Flow Monitor: Calculate Payroll — Status: Completed with Errors, Error Count: 3
BIP Payroll Error Report: EMP-10481/10492/10510 — BONUS element, input value GRADE_STEP not found
Fix Applied
BONUS_CALC formula updated via Fast Formulas — GRADE_STEP reference replaced with GRADE_BAND. Correct Payroll Results submitted for 3 employees — all reprocessed successfully. Calculate Prepayments submitted and completed. Transfer to Subledger Accounting complete.
Prevention
Payroll setup change control: any input value rename or removal must include a Fast Formula impact check before the change is applied. Payroll parallel test run must complete without errors before live payroll submission.
Tags
Fusion HCMPayrollFlow MonitorFormula ErrorCorrect Payroll ResultsBIP Error ReportOracle Fusion Cloud
Oracle References

Oracle Documentation References

References the Oracle public documentation for this diagnostic area. These links open directly on docs.oracle.com.

Documentation PageTitleScenario
Period ClosePeriod Close — Close MonitorFusion payroll transfer to GL and close monitor status
Oracle Fusion General LedgerUsing Analytics and Reports for FinancialsPayroll to GL reconciliation for Fusion Cloud
Continue Your Diagnosis

Related Diagnostic Scripts

HCM-04

Worker Record Diagnostic (Fusion)

View the full diagnostic for this related script.

 AP-07

AP Invoice Validation (Fusion)

View the full diagnostic for this related script.

Engage William A. Green

Ready to Resolve This in Your Environment?

HCM-03 is one of 65 diagnostic scripts covering every major Oracle EBS and Fusion module. William A. Green Consulting runs the script in your environment, applies guided data fixes, and builds the knowledge base that prevents the same issues from recurring.

Schedule a Discovery Call → ← View All 65 Scripts

See this script run autonomously — Oracle AI Platform →