HCM-04: Worker Record Diagnostic (Oracle Fusion)

Oracle Fusion HCM worker record diagnostics use a fundamentally different data model than Oracle EBS HR. Where EBS stores employee data in date-effective relational tables (PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F), Fusion HCM uses an object-oriented model accessed through the REST API at /hcmRestApi/resources/workers and its child resources — assignments, contracts, salaries, and work relationships. The diagnostic approach uses the Fusion HCM REST API for individual worker detail, OTBI HCM subject areas for population-level analysis, and Manage Employment screens for interactive review.

Worker record integrity in Fusion is managed through the Work Relationship model. A worker can have multiple work relationships — for example, an employee relationship and a contingent worker relationship — and each relationship has its own set of assignments. When a worker's primary work relationship is terminated incorrectly or a work relationship is missing, downstream modules see the worker as inactive. Fusion payroll, absence management, and benefits all reference the primary work relationship to determine eligibility.

The most operationally impactful Fusion worker record issue is an incorrect termination. When a worker is terminated in error — either because the wrong person was selected, or because the termination date was set incorrectly — Oracle Fusion triggers a cascade of actions: payroll is end-dated, benefits enrollment is terminated, system access is revoked, and position becomes vacant. Reversing an incorrect termination requires reversing each of these actions in the correct sequence through Fusion's Reverse Termination function, and HCM-04 maps out the full reversal sequence and verifies each step completed correctly.

HCM-04 provides a structured Fusion worker record diagnostic using REST API GET /workers for complete worker profile, OTBI HCM Core subject area for assignment history analysis, Manage Employment for work relationship status, and the Fusion HCM Audit Report for change history review.

REST API Worker Profile

GET /workers — complete worker profile including work relationship status, assignment status, legal entity, payroll relationship, and contract details. The primary data source for individual worker diagnostics.

OTBI Assignment History

HCM Core subject area — full assignment history with status changes, effective dates, and entered-by detail. Identifies the specific change that caused the current issue and the user who made it.

Cascade Impact Assessment

Termination cascade actions confirmed: payroll exclusion, benefits end-date, access revocation. Maps the complete reversal sequence needed to restore the worker to their correct state across all downstream systems.

Fusion HCM Audit Report

Setup and Maintenance > Audit Reports — every HCM record change with user, timestamp, old value, and new value. The authoritative record of who made the change and when, used for both the KB article and any HR investigation.

════════════════════════════════════════════════════════════
  ORACLE FUSION — WORKER RECORD DIAGNOSTIC
════════════════════════════════════════════════════════════
  Worker Number      : WRK-10482
  Name               : J. Martinez
  Legal Entity       : US Incorporated
  Case Number        : FC-HCM-2026-0418
  Report Date        : 20-FEB-2026 10:30:22
════════════════════════════════════════════════════════════

[ STEP 1 — REST API WORKER STATUS ]         STATUS: ✗ ISSUE
────────────────────────────────────────────────────────────
  REST Endpoint      : GET /hcmRestApi/resources/workers/WRK-10482
  workerType         : Employee ✓
  workRelationship   : Status: Inactive — terminated 15-FEB-2026 ✗
  assignmentStatus   : Suspended ✗
  ✗ FAIL: Worker shows as terminated — payroll and access revoked

[ STEP 2 — OTBI ASSIGNMENT HISTORY ]        STATUS: ✗ INCORRECT TERMINATION
────────────────────────────────────────────────────────────
  Termination Date   : 15-FEB-2026
  Termination Reason : Resignation
  ✗ No resignation letter on file — termination entered in error
  HR Confirmation    : Manager confirms J.Martinez is still active ✗

[ STEP 3 — CASCADE IMPACT ]                 STATUS: ✗ ACTIONS TRIGGERED
────────────────────────────────────────────────────────────
  ✗ Payroll excluded from FEB-2026 run
  ✗ Benefits enrollment end-dated 15-FEB-2026
  ✗ Fusion account access revoked 15-FEB-2026

════════════════════════════════════════════════════════════
  FUSION DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  Worker terminated in error — Reverse Termination required
  FIX: Fusion Manage Employment > Reverse Termination — full sequence
════════════════════════════════════════════════════════════

Diagnostic Steps

Fusion worker record diagnostic using REST API GET /workers for full profile and work relationship status, OTBI HCM Core subject area for assignment history, Manage Employment for interactive work relationship review, and Fusion HCM Audit Report for the change history identifying who made the change and when.

Backup Created

Fusion Cloud does not permit direct database access. REST API GET response and OTBI assignment history export are saved before any corrective action as the pre-action state record for the KB article and audit trail.

Guided Data Fix

Reverse Termination via Manage Employment > Reverse Termination is the primary path for incorrect terminations. HCM-04 maps the complete reversal sequence — work relationship reinstatement, payroll re-inclusion, benefits re-enrollment, access restoration — and verifies each step.

KB Article Generated

Complete KB article from REST API response and Fusion HCM Audit Report — worker number, termination details, cascade actions triggered, reversal sequence performed, post-reversal state verified.

Pre-Action Documentation — HCM-04

REST API: GET /workers/WRK-10482 — full worker profile saved

OTBI: HCM Core — assignment history export before action

Fusion HCM Audit Report — change history for the worker

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 ✓

REST API GET /workers/WRK-10482 response savedExported ✓

OTBI HCM assignment history export completedSaved ✓

Fusion HCM Audit Report downloadedSaved ✓

Manager confirmation of active status obtainedConfirmed ✓

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.

GETWorker Profile

/hcmRestApi/resources/11.13.18.05/workers/{PersonId}

Path Parameters

PersonId integer — Fusion internal person ID. Find from PersonNumber (worker number) via the collection GET with q=PersonNumber={workerNumber}.

Key Query Parameters

expand workRelationships,assignments — expand child collections inline

fields PersonId,PersonNumber,DisplayName,workRelationships.WorkerType,workRelationships.ActiveFlag,workRelationships.TerminationDate

Response Fields Read

workRelationships.ActiveFlag — Y/N — whether the work relationship is active

workRelationships.WorkerType — Employee, Contingent Worker

workRelationships.TerminationDate — set if worker has been terminated

workRelationships.TerminationReason — reason code for the termination

assignments.AssignmentStatus — Active Assignment, Suspended, Inactive

assignments.ManagerPersonId — the line manager's person ID

GETWorker Assignment History

/hcmRestApi/resources/11.13.18.05/workers/{PersonId}/child/assignments

Path Parameters

PersonId integer — Fusion internal person ID

Key Query Parameters

fields AssignmentId,AssignmentStatus,EffectiveStartDate,EffectiveEndDate,DepartmentName,JobName,GradeName,LocationName,ManagerPersonId

orderBy EffectiveStartDate:desc — most recent assignment first

Response Fields Read

AssignmentStatus — Active, Inactive, Suspended

EffectiveStartDate, EffectiveEndDate — date range for each assignment version

DepartmentName, JobName, GradeName, LocationName — role context

ManagerPersonId — cross-reference against workers endpoint to confirm manager active status

KB-FC-HCM-0418-001 · Script: HCM-04

Fusion Worker WRK-10482 Terminated in Error — Reverse Termination Required

Module: HCM
Platform: Oracle Fusion Cloud
Status: RESOLVED

Symptom

J.Martinez (WRK-10482) shows as terminated in Oracle Fusion HCM as of 15-FEB-2026 with reason Resignation. Manager confirms J.Martinez is still active. Payroll excluded from FEB run, benefits end-dated, Fusion access revoked. Reverse Termination required.

Root Cause

HR user selected the wrong employee when entering a resignation — J.Martinez was selected instead of J.Martinez-Lopez (two employees with similar names in the same department). Error discovered on 20-FEB-2026 when J.Martinez reported inability to log in.

Tables Affected

REST API: GET /workers/WRK-10482 — workRelationshipStatus: Inactive, terminationDate: 15-FEB-2026
OTBI: HCM Core — terminationReason: Resignation, enteredBy: HR_USER_CHEN, enteredDate: 15-FEB-2026 09:14

Fix Applied

Reverse Termination executed via Manage Employment for WRK-10482. Work relationship reinstated effective 15-FEB-2026. J.Martinez re-included in FEB-2026 payroll via Correct Payroll Results. Benefits re-enrollment submitted. Fusion account access restored.

Prevention

Employee search for termination actions should require both name AND employee number confirmation before proceeding. HR policy updated: terminations require manager email confirmation before entry.

Worker Terminated in Error

Wrong worker selected for termination, or termination date incorrect. Cascade actions triggered immediately — payroll excluded, benefits end-dated, access revoked. HCM-04 maps the full Reverse Termination sequence and verifies each cascade action is correctly reversed.

Relationship

Work Relationship Missing or Inactive

Primary work relationship terminated or missing — worker shows as inactive to payroll, benefits, and downstream modules. HCM-04 identifies the missing relationship and the correct start date for re-establishment.

Supervisor

Incorrect Line Manager Assignment

Worker assigned to the wrong supervisor in Fusion — affects approval hierarchy routing, organization chart, and manager self-service visibility. HCM-04 identifies the current and correct supervisor from the REST API and org chart.

Import

FBDI Worker Import Failure

Bulk worker data import via FBDI rejected records. Missing required fields, invalid legal entity, or date format errors. HCM-04 identifies the failing rows from the ESS job output log.

Data Source	Type	Purpose
REST API: /hcmRestApi/resources/workers	REST	Complete worker profile — relationships, assignments, contracts
OTBI: HCM Core	OTBI	Assignment history — status changes, effective dates, entered-by
Fusion HCM Audit Report	Fusion UI	Change history — user, timestamp, old/new values
Manage Employment	Fusion UI	Interactive work relationship and assignment management
BIP: Worker Data Report	BIP	Complete worker data for documentation

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.

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

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

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

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
Worker terminated in error — Reverse Termination required	Functional First	Execute Reverse Termination via Manage Employment > Actions > Reverse Termination. HCM-04 maps the full reversal sequence and verifies each cascade action (payroll, benefits, access) is correctly reversed.
Work relationship missing — worker shows as inactive	Functional First	Add the work relationship via Manage Employment > Add Work Relationship. HCM-04 identifies the missing relationship type and the correct start date from the OTBI assignment history.
Assignment status incorrect — Suspended or Inactive in error	Functional First	Correct the assignment status via Manage Employment > Edit Assignment. HCM-04 identifies the current status and the correct status from the worker's current work context.
Supervisor assignment incorrect in Fusion	Functional First	Update the line manager via Manage Employment > Edit Assignment. HCM-04 identifies the current supervisor from the REST API response and confirms the correct supervisor from the org chart.
Worker not included in payroll after record correction	Functional First	Use Correct Payroll Results or a QuickPay calculation to include the corrected worker in the current period. HCM-04 identifies the payroll flow and the submission parameters.
Benefits not re-enrolled after reversal	Functional First	Submit benefits re-enrollment via Benefits > Enrollment. HCM-04 identifies which benefit plans were end-dated and the re-enrollment path for each.
FBDI worker import error — bulk import failure	Functional First	Review the Load Worker Data ESS output. Correct the FBDI template and resubmit. HCM-04 identifies the failing rows and column-level error from the ESS log.
Work relationship data corruption — unresolvable via UI	Oracle Support SR	If the work relationship is in an inconsistent state not correctable through Reverse Termination or Manage Employment, HCM-04 documents the worker ID and data state 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

✓

REST API: GET /workers/WRK-10482 — full worker profile saved

Exported before any corrective action is taken

✓

OTBI: HCM Core — assignment history export before action

Exported before any corrective action is taken

✓

Fusion HCM Audit Report — change history for the worker

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-04 — Fusion Diagnostic Framework

════════════════════════════════════════════════════════════
  ORACLE FUSION — WORKER RECORD DIAGNOSTIC STEPS
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud HCM
  Tools              : REST API, OTBI HCM Core, Manage Employment, Audit Report
  Pre-Action Export  : REST API worker profile and OTBI history saved
────────────────────────────────────────────────────────────
  Step 1 — REST API  : GET /workers/WRK-10482 — termination confirmed in data ✓
  Step 2 — OTBI      : HCM Core assignment history — termination 15-FEB identified ✓
  Step 3 — Audit Rpt : Fusion HCM Audit Report — entered by HR user at 09:14 ✓
  Step 4 — Cascade   : Payroll exclusion, benefits end-date, access revoke confirmed ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — Reverse Termination sequence mapped
════════════════════════════════════════════════════════════
  Documentation      : KB article from REST API and audit report output
  Fusion Audit Trail : Reverse Termination logged in HCM audit trail
  SR Reference       : N/A — resolved via Manage Employment > Reverse Termination
════════════════════════════════════════════════════════════

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-0418-001

Fusion Worker WRK-10482 Terminated in Error — Reverse Termination Required

Oracle Fusion Cloud · HCM

● RESOLVED

Symptom

Root Cause

Tables

REST API: GET /workers/WRK-10482 — workRelationshipStatus: Inactive, terminationDate: 15-FEB-2026
OTBI: HCM Core — terminationReason: Resignation, enteredBy: HR_USER_CHEN, enteredDate: 15-FEB-2026 09:14

Fix Applied

Prevention

Employee search for termination actions should require both name AND employee number confirmation before proceeding. HR policy updated: terminations require manager email confirmation before entry.

Documentation Page	Title	Scenario
Accounts Payable Manager Job Role	Accounts Payable Manager Job Role	Fusion HCM worker data and financial system integration
Implement General Ledger	Getting Started with Financials Implementation	Business unit and legal entity setup for Fusion HCM workers

Worker Record Diagnostic (Oracle Fusion)

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in HCM-04

Documentation Before Every Action — HCM-04

Pre-Action Documentation — HCM-04

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

Worker Terminated in Error

Work Relationship Missing or Inactive

Incorrect Line Manager Assignment

FBDI Worker Import Failure

Tables Examined

How Every Resolution Decision Is Made

Nothing Acts Without a Documented State

Every Execution Produces a Record

Oracle Documentation References

Ready to Resolve This in Your Environment?

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in HCM-04

Documentation Before Every Action — HCM-04

Pre-Action Documentation — HCM-04

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

Worker Terminated in Error

Work Relationship Missing or Inactive

Incorrect Line Manager Assignment

FBDI Worker Import Failure

Tables Examined

How Every Resolution Decision Is Made

Nothing Acts Without a Documented State

Every Execution Produces a Record

Oracle Documentation References

Related Diagnostic Scripts

Payroll Run Diagnostic (Fusion)

Absence Management (Fusion)

Ready to Resolve This in Your Environment?