SYS-05: ESS Job Health Diagnostic (Oracle Fusion)

Oracle Fusion Cloud Scheduled Processes (ESS — Enterprise Scheduler Service) are the backbone of every automated operation in Fusion — Create Accounting, Import Journals, AutoInvoice, Payroll Flow tasks, Transfer to GL, and hundreds of other batch processes all run through ESS. When an ESS job fails, it produces one of three status values: Error (the job engine itself failed — infrastructure issue), Completed with Errors (the job ran but individual records failed — data issue), or Warning (the job completed but with advisory messages that should be reviewed). The diagnostic approach is entirely different for each status.

The most common ESS job failure mode is Completed with Errors. This means the ESS infrastructure functioned correctly, the job started and finished, but some of the data records it processed had errors that prevented them from completing. The job output log contains the detailed error messages — typically an invalid account, a missing setup value, a date in a closed period, or a formula failure. For these failures, the diagnostic task is to read the output log, categorize the errors, identify the root cause in the underlying data or setup, and correct the source condition before resubmitting.

The Error status is fundamentally different and more serious. An ESS job with status Error means the job engine encountered an infrastructure-level problem — an out-of-memory condition, a database connection failure, a job definition error, or an unhandled exception in Oracle's own code. These failures cannot be resolved by correcting data and resubmitting — they require Oracle Support investigation. The distinction between Error and Completed with Errors is the most important triage decision in ESS diagnostics.

SYS-05 provides a structured ESS job health diagnostic using Manage Scheduled Processes for job status and output log access, OTBI System subject areas for population-level job failure analysis, and the ESS job request log for detailed error categorization. The diagnostic identifies whether a failure is data-driven (correctable) or infrastructure-driven (SR required) and provides the exact resubmission parameters for correctable failures.

Status Triage

The critical first step — distinguishing Completed with Errors (data issue, correctable) from Error (infrastructure issue, SR required). SYS-05 reads the job status and output log to make this determination before any other action.

Error Categorization

Output log analysis — error messages categorized by type (invalid account, closed period, missing setup, formula error). Record count per error type. Identifies the highest-impact error to address first.

Failure Pattern Analysis

OTBI Financials Job History — failure count and error type across multiple submission dates. Identifies recurring errors that indicate a systemic setup or data condition vs one-time failures.

Resubmission Readiness

Confirms no other ESS job is currently running for the same module. Validates that the source condition has been corrected. Provides the exact resubmission parameters for the corrected run.

════════════════════════════════════════════════════════════
  ORACLE FUSION — ESS JOB HEALTH DIAGNOSTIC
════════════════════════════════════════════════════════════
  Job Name           : Create Accounting
  Module             : Payables
  Submission Date    : 25-FEB-2026 02:00:11
  Case Number        : FC-SYS-2026-0512
  Report Date        : 25-FEB-2026 08:30:45
════════════════════════════════════════════════════════════

[ STEP 1 — JOB STATUS ]                    STATUS: ⚠ COMPLETED WITH ERRORS
────────────────────────────────────────────────────────────
  Job ID             : ESS-2026-048812
  Status             : Completed with Errors ⚠
  Records Processed  : 4,841
  Records in Error   : 3 ✗
  Output Log         : Available — downloaded for analysis

[ STEP 2 — ERROR CATEGORIZATION ]          STATUS: ✗ DATA ERRORS
────────────────────────────────────────────────────────────
  Error Type         : Invalid account combination — 3 invoices ✗
  Account            : 01-6200-7100-0000 — disabled 01-FEB-2026
  Invoices Affected  : INV-2026-00841, INV-2026-00842, INV-2026-00843
  Infrastructure     : Job engine healthy — no SR required ✓

[ STEP 3 — OTBI JOB HISTORY ]              STATUS: ⚠ PATTERN DETECTED
────────────────────────────────────────────────────────────
  ⚠ Same account error on 3 prior Create Accounting runs (JAN, FEB weeks 1-3)
  Root Cause         : Account disabled but invoices still coded to it

[ STEP 4 — RESUBMISSION READINESS ]        STATUS: ✓ READY
────────────────────────────────────────────────────────────
  Correct source account, then resubmit Create Accounting ✓
  No other ESS jobs currently running for Payables ✓

════════════════════════════════════════════════════════════
  FUSION DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  Completed with Errors — data issue, not infrastructure
  FIX: Re-enable account or remap 3 invoices, then resubmit
════════════════════════════════════════════════════════════

Diagnostic Steps

ESS job health diagnostic using Manage Scheduled Processes for job status and output log access, OTBI Financials Job History for failure pattern analysis across submission dates, and the ESS output log for error categorization — distinguishing data errors (Completed with Errors) from infrastructure errors (Error status).

Backup Created

Fusion Cloud does not permit direct database access. ESS job output log and OTBI job history are downloaded before any corrective action as the pre-action state record.

Guided Data Fix

For Completed with Errors: correct the source data or setup condition, then resubmit. SYS-05 provides the exact resubmission parameters. For Error status: document the job ID, request ID, and output log for the Oracle Support SR — never attempt data corrections when the job engine itself has failed.

KB Article Generated

Complete KB article from ESS log and OTBI history — job name, failure type, error categorization, root cause, corrective action, resubmission result.

Pre-Action Documentation — SYS-05

ESS job output log — downloaded before any action

OTBI: Financials Job History — error pattern export

Manage Scheduled Processes — job detail screenshot

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 ✓

ESS job output log downloadedSaved ✓

OTBI job history export completedSaved ✓

Job status confirmed Completed with Errors (not Error)Verified ✓

No ESS job currently running for this moduleConfirmed ✓

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.

GETESS Scheduled Process (Job Status)

/fscmRestApi/resources/11.13.18.05/erpintegrations/jobs/{JobId}

Path Parameters

JobId integer — ESS request ID. Visible in Manage Scheduled Processes output column or in the job output log filename.

Key Query Parameters

fields JobId,JobName,Status,StartTime,EndTime,SubmittedBy,Parameters

Response Fields Read

Status — SUCCEEDED, COMPLETED_WITH_ERRORS, ERROR, RUNNING, WAIT

StartTime, EndTime — job duration calculation

SubmittedBy — who submitted the job

Parameters — the parameter values used for this submission

NOTE: The ERP Integrations REST API requires the ERP_INTEGRATION_SPECIALIST role or equivalent. Standard AP/GL roles may not have access to this endpoint — verify before attempting.

POSTESS Job Submission (Resubmit)

/fscmRestApi/resources/11.13.18.05/erpintegrations/jobs

Response Fields Read

Body required: { "JobPackageName": "oracle/apps/ess/...", "JobDefinitionName": "JobName", "ESSParameters": "param1,param2,..." }

Response: JobId — the new ESS request ID for monitoring

Use GET /erpintegrations/jobs/{JobId} to poll status after submission

NOTE: POST to this endpoint triggers an actual ESS job submission. Test parameter values in Manage Scheduled Processes first before using the API for submission.

KB-FC-SYS-0512-001 · Script: SYS-05

ESS Create Accounting (Payables) Completed with Errors — Invalid Account 01-6200-7100-0000

Module: System
Platform: Oracle Fusion Cloud
Status: RESOLVED

Symptom

Create Accounting ESS job ESS-2026-048812 (Payables, FEB-2026) completed with 3 errors. Output log identifies invalid account combination 01-6200-7100-0000 on invoices INV-2026-00841/842/843. Same error pattern on 3 prior runs. Infrastructure healthy — data issue.

Root Cause

Account 01-6200-7100-0000 was disabled on 01-FEB-2026 as part of a COA restructuring. Three invoices coded to this account before the restructure were not updated. The account was disabled in Manage Chart of Accounts without checking for open AP invoices still referencing it.

Tables Affected

ESS Output Log: ESS-2026-048812 — AccountingError: Invalid account combination 01-6200-7100-0000 (INV-2026-00841, 00842, 00843)
OTBI: Financials Job History — same error on 4 consecutive Create Accounting submissions

Fix Applied

Account 01-6200-7100-0000 re-enabled temporarily via Manage Chart of Accounts. Three invoice distributions updated to use replacement account 01-6200-7200-0000 via Manage Invoices. Create Accounting resubmitted — completed with 0 errors. Account 01-6200-7100-0000 re-disabled after correction.

Prevention

COA restructuring checklist updated: before disabling any account, run OTBI query for open AP invoices, PO distributions, and journal lines referencing the account. SYS-05 recurring error check — any ESS job failing 3+ consecutive runs triggers an alert to the system admin.

Completed with Errors — Invalid Account

The most common Create Accounting failure. Account disabled or end-dated after the source transactions were coded to it. SYS-05 identifies the account, the affected records, and whether to re-enable the account or remap the transactions.

Infrastructure

Error Status — SR Required

ESS job status Error means the job engine itself failed — not a data issue. Data corrections will not help. SYS-05 documents the job ID, request ID, and output log for Oracle Support and confirms no data action should be taken.

Pattern

Recurring Failure — Same Error Multiple Runs

The same error appearing across 3+ consecutive runs indicates a systemic setup or data condition that is not being addressed between resubmissions. SYS-05 identifies the root cause from OTBI job history pattern analysis.

Schedule

Scheduled Job Not Running

An ESS job with an active schedule that has not submitted at the expected time. Schedule definition may be inactive, paused, or the prior run may still be in progress. SYS-05 identifies the schedule status and the last successful submission.

Data Source	Type	Purpose
Manage Scheduled Processes	Fusion UI	Job status, output log, request ID, submission detail
ESS Job Output Log	Log File	Record-level error messages — the primary error source
OTBI: Financials Job History	OTBI	Job failure patterns across submission dates
BIP: Job Execution Report	BIP	Structured error summary for specific job types

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
Completed with Errors — data errors in output log	Functional First	Read the output log via Manage Scheduled Processes > Output. SYS-05 categorizes the errors by type and identifies the source data or setup condition to correct before resubmitting.
Same error recurring across multiple runs	Functional First	OTBI job history pattern confirms the root cause is systemic — a setup or data condition that persists across runs. SYS-05 identifies the common error from the pattern and the upstream source to fix.
Job status Error — infrastructure failure	Oracle Support SR	ESS job status Error (not Completed with Errors) indicates a job engine issue. SYS-05 documents the job ID, request ID, and full output log for the Oracle Support SR. Do not attempt data corrections.
Invalid account in Create Accounting	Functional First	Re-enable or remap the account via Manage Chart of Accounts or the source transaction. SYS-05 identifies the specific account and the invoices, journals, or receipts referencing it from the output log.
Job runs but produces no output — zero records processed	Functional First	Review the job parameters — legal entity, ledger, date range, process category. A zero-record run typically indicates a parameter mismatch. SYS-05 identifies the correct parameter set from prior successful submissions.
ESS job queue backlog — long wait times	Functional First	Review the ESS job queue via Manage Scheduled Processes > Search. SYS-05 identifies jobs with unusually long queue times and whether a prior long-running job is blocking the queue.
Scheduled job not running on schedule	Functional First	Review the schedule definition via Manage Scheduled Processes > Schedule. SYS-05 confirms whether the schedule is active and whether the last scheduled submission ran at the expected time.
ESS infrastructure degraded — multiple jobs failing	Oracle Support SR	When multiple unrelated ESS jobs across modules all show Error status simultaneously, the ESS infrastructure itself is degraded. SYS-05 documents the pattern and affected job list 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

✓

ESS job output log — downloaded before any action

Exported before any corrective action is taken

✓

OTBI: Financials Job History — error pattern export

Exported before any corrective action is taken

✓

Manage Scheduled Processes — job detail screenshot

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

SYS-05 — Fusion Diagnostic Framework

════════════════════════════════════════════════════════════
  ORACLE FUSION — ESS JOB HEALTH DIAGNOSTIC STEPS
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud
  Tools              : Manage Scheduled Processes, OTBI, ESS Output Log
  Pre-Action Export  : ESS output log and OTBI history saved before action
────────────────────────────────────────────────────────────
  Step 1 — Job Status    : ESS-2026-048812 — Completed with Errors, 3 records ✓
  Step 2 — Output Log    : Invalid account 01-6200-7100-0000 — disabled 01-FEB ✓
  Step 3 — OTBI History  : Pattern confirmed — same error 4 consecutive runs ✓
  Step 4 — Triage        : Data error (not infrastructure) — no SR required ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — Account correction and resubmission path identified
════════════════════════════════════════════════════════════
  Documentation      : KB article from ESS log and OTBI output
  Fusion Audit Trail : Account and invoice changes logged in Fusion audit trail
  SR Reference       : N/A — data error resolved via Manage Chart of Accounts
════════════════════════════════════════════════════════════

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-SYS-0512-001

ESS Create Accounting (Payables) Completed with Errors — Invalid Account 01-6200-7100-0000

Oracle Fusion Cloud · System

● RESOLVED

Symptom

Root Cause

Tables

ESS Output Log: ESS-2026-048812 — AccountingError: Invalid account combination 01-6200-7100-0000 (INV-2026-00841, 00842, 00843)
OTBI: Financials Job History — same error on 4 consecutive Create Accounting submissions

Fix Applied

Prevention

Documentation Page	Title	Scenario
Using Payables Invoice To Pay	Using Payables Invoice to Pay — Fusion	ESS job submission and monitoring for Fusion Payables
Period Close	Period Close — Close Monitor	ESS job completion dependencies for Fusion period close
Oracle Fusion General Ledger	Using Analytics and Reports for Financials	Scheduled process analytics for ESS job health trending

ESS Job Health Diagnostic (Oracle Fusion)

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in SYS-05

Documentation Before Every Action — SYS-05

Pre-Action Documentation — SYS-05

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

Completed with Errors — Invalid Account

Error Status — SR Required

Recurring Failure — Same Error Multiple Runs

Scheduled Job Not Running

Data Sources

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 SYS-05

Documentation Before Every Action — SYS-05

Pre-Action Documentation — SYS-05

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

Completed with Errors — Invalid Account

Error Status — SR Required

Recurring Failure — Same Error Multiple Runs

Scheduled Job Not Running

Data Sources

How Every Resolution Decision Is Made

Nothing Acts Without a Documented State

Every Execution Produces a Record

Oracle Documentation References

Related Diagnostic Scripts

Integration Monitor (Fusion)

Security & Role (EBS)

GL Period Close (Fusion)

Ready to Resolve This in Your Environment?