AR-07: AutoInvoice Diagnostic (Oracle Fusion)

Oracle Fusion Cloud AR AutoInvoice diagnostics operate in a fundamentally different tooling environment than EBS R12. In Fusion, the AutoInvoice import process runs as an Enterprise Scheduler Service (ESS) job — the Import AutoInvoice Fusion program — and errors are reported through a combination of the ESS job output, Oracle Business Intelligence Publisher reports for AutoInvoice exceptions, and OTBI queries against the Receivables Transactions subject area. There is no direct access to the interface tables through SQL; all error investigation goes through the supported reporting tools.

The Fusion AutoInvoice failure patterns are similar to EBS R12 — invalid transaction source, closed GL date, invalid customer or site, duplicate transaction reference — but the error messages appear in a structured BIP report output rather than in the RA_INTERFACE_ERRORS_ALL table. The BIP AutoInvoice Exceptions report shows the error type, the originating system reference, and the specific field that failed validation. Navigating to the correct screen in Fusion to correct an interface record requires knowing the path through the Manage Transactions screen, the AutoInvoice Corrections workflow, or the source system data correction workflow depending on the error type.

The most operationally significant Fusion AutoInvoice failure is the ESS job completion with errors — where the job status shows Succeeded with Warnings or Error, but the AR team may not notice the warning because the ESS job summary shows a high success count. AR-07 provides a systematic approach to reading the ESS job history output, identifying the specific records in error, and navigating the Fusion AR correction screens to resolve each error type.

AR-07 provides a structured Fusion AutoInvoice diagnostic framework using ESS job history analysis, BIP AutoInvoice Exceptions report interpretation, OTBI Receivables Transactions subject area queries for error population analysis, and the Fusion AR Manage Transactions and AutoInvoice Corrections screens for resolution navigation.

════════════════════════════════════════════════════════════
  ORACLE FUSION — AUTOINVOICE INTERFACE DIAGNOSTIC
════════════════════════════════════════════════════════════
  Batch Source       : OMS-FUSION-INVOICES
  ESS Job ID         : ESS-2026-04481
  Records Submitted  : 312 total
  Case Number        : FC-AR-2026-0142
  Report Date        : 22-FEB-2026 08:40:15
════════════════════════════════════════════════════════════

[ STEP 1 — ESS JOB STATUS ]                  STATUS: ⚠ WARNINGS
────────────────────────────────────────────────────────────
  ESS Job Status     : Succeeded with Warnings
  Imported           : 284 records ✓
  Rejected           : 28 records ✗

[ STEP 2 — BIP EXCEPTIONS REPORT ]
────────────────────────────────────────────────────────────
  Error Type 1       : INVALID_GL_DATE — 22 records (GL date 31-JAN-2026 — JAN closed)
  Error Type 2       : CUSTOMER_NOT_FOUND — 4 records (Cust Ref: CUST-EXT-8812)
  Error Type 3       : DUP_TRANSACTION_NUM — 2 records (already imported)

[ STEP 3 — OTBI ANALYSIS ]
────────────────────────────────────────────────────────────
  Subject Area       : Receivables Transactions — Exceptions
  22 GL date errors  : All reference batch source OMS-FUSION-INVOICES, created 31-JAN
  Fix                : AutoInvoice Corrections > Edit GL Date > set to 28-FEB-2026

[ STEP 4 — RESOLUTION NAVIGATION ]
────────────────────────────────────────────────────────────
  GL Date Fix        : Billing > AutoInvoice Corrections > update GL Date
  Customer Fix       : Create customer CUST-EXT-8812 via Manage Customers
  Duplicate Fix      : Delete duplicate interface records via AutoInvoice Corrections

════════════════════════════════════════════════════════════
  FUSION DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  28 records in 3 error categories — all resolvable via Fusion UI
════════════════════════════════════════════════════════════

Pre-Action Documentation — AR-07

ESS: Import AutoInvoice — job output log downloaded

BIP: AutoInvoice Exceptions report export

OTBI: Receivables Transactions — Exceptions subject area export

FBDI: AutoInvoice import template exported before correction

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 history retrievedDownloaded ✓

BIP AutoInvoice Exceptions runReport saved ✓

OTBI exceptions export completedSaved ✓

No AutoInvoice job currently runningConfirmed ✓

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.

GETAutoInvoice Interface Errors

/fscmRestApi/resources/11.13.18.05/receivablesTrxImportErrors

Key Query Parameters

q filter — e.g. BatchName=YOUR_BATCH_NAME to scope to a specific import batch

limit integer — default 25, set to 500 for large batches

orderBy e.g. ErrorDate:desc to get most recent errors first

Response Fields Read

ErrorMessageName — Oracle error code, e.g. AR_INVALID_GL_DATE

ErrorMessageText — human-readable error description

BatchName — the AutoInvoice batch that produced the error

TransactionNumber — the source transaction reference

ColumnName — the specific column that failed validation

GETReceivables Transactions

/fscmRestApi/resources/11.13.18.05/receivablesInvoices/{TransactionId}

Path Parameters

TransactionId integer — Fusion internal transaction ID

Key Query Parameters

fields e.g. TransactionId,TransactionNumber,Status,AccountingStatus,CustomerId

Response Fields Read

Status — COMPLETE or INCOMPLETE

AccountingStatus — ACCOUNTED or NOT ACCOUNTED

TransactionDate, GlDate, DueDate

CustomerNumber, CustomerName, BillToSiteUseId

KB-FC-AR-0142-001 · Script: AR-07

Fusion AR AutoInvoice — 28 Records Rejected: Closed GL Date, Missing Customer, Duplicate Reference

Module: Accounts Receivable
Platform: Oracle Fusion Cloud
Status: RESOLVED

Symptom

ESS AutoInvoice job ESS-2026-04481 completed with Succeeded with Warnings. 28 of 312 records rejected. BIP Exceptions report shows 22 INVALID_GL_DATE, 4 CUSTOMER_NOT_FOUND, and 2 DUP_TRANSACTION_NUM errors.

Root Cause

GL date errors: OMS system used transaction date 31-JAN-2026 — JAN-2026 closed in Fusion AR on 03-FEB-2026. Customer errors: 4 records reference external customer CUST-EXT-8812 not yet created in Fusion. Duplicates: 2 records previously imported in the 20-JAN batch were resent.

Tables Affected

Fusion AutoInvoice Interface — origSystemBatchName: OMS-FUSION-INVOICES, glDate: 31-JAN-2026 (22 records)
ESS Job ID: ESS-2026-04481, status: Succeeded with Warnings

Fix Applied

GL dates corrected to 28-FEB-2026 via AutoInvoice Corrections screen. Customer CUST-EXT-8812 created via Manage Customers. 2 duplicate records deleted. AutoInvoice resubmitted — all 28 previously rejected records imported.

Prevention

OMS Fusion integration updated to query Fusion AR open periods API before populating GL date. Customer master pre-validation step added to OMS export workflow. AR-07 should run after each AutoInvoice batch to surface ESS warnings before they accumulate.

Table / View	Schema	Purpose in Diagnostic
OTBI: Receivables Transactions	OTBI	Import batch errors and statuses
ESS Job History	ESS	Import AutoInvoice run history
BIP: AutoInvoice Exceptions	BIP	Line-level rejection detail

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
INVALID_GL_DATE — GL date in closed Fusion AR period	Functional First	Correct via Billing > AutoInvoice Corrections > Edit GL Date. AR-07 identifies the correct open period from the Fusion AR period status.
CUSTOMER_NOT_FOUND — customer reference not in Fusion	Functional First	Create the customer via Manage Customers or verify the customer number mapping in the source system. AR-07 identifies the external reference and searches for near-match candidates.
DUP_TRANSACTION_NUM — already imported in prior batch	Functional First	Delete the duplicate interface record via AutoInvoice Corrections. AR-07 identifies the original imported transaction and confirms the duplicate was not a legitimate amendment.
INVALID_TRANSACTION_SOURCE — batch source not in Fusion	Functional First	Define the transaction source via Billing > Setup > Transaction Sources. AR-07 identifies the source name in the interface record and the Fusion setup navigation.
ESS job completes with Error — full batch rejected	Functional First	Review the full ESS job output log. AR-07 identifies the first critical error and the correction path. Common causes: profile option misconfiguration, missing receivables activity setup.
Invalid bill-to site in Fusion customer master	Functional First	Verify the bill-to site address and status via Manage Customers > Sites. AR-07 identifies the customer and the site use that failed validation.
Tax failure in Fusion Tax engine	Functional First	Fusion tax errors corrected via Manage Tax Rates or by updating the transaction tax classification. AR-07 identifies the error from the BIP Exceptions report tax error column.
Recurring import failures — same source, multiple batches	Oracle Support SR	Persistent failures across batches from the same source indicate a source system integration defect or a Fusion code issue. AR-07 documents the pattern 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: Import AutoInvoice — job output log downloaded

Exported before any corrective action is taken

✓

BIP: AutoInvoice Exceptions report export

Exported before any corrective action is taken

✓

OTBI: Receivables Transactions — Exceptions subject area export

Exported before any corrective action is taken

✓

FBDI: AutoInvoice import template exported before correction

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

AR-07 — Fusion Diagnostic Framework

════════════════════════════════════════════════════════════
  ORACLE FUSION — AR AUTOINVOICE DIAGNOSTIC
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud (no direct DB access)
  Tools Available    : ESS Job History, BIP Exceptions, OTBI, AutoInvoice Corrections
  Pre-Action Export  : FBDI file exported before any corrections
────────────────────────────────────────────────────────────
  Step 1 — ESS       : Import AutoInvoice job history retrieved — 28 rejected ✓
  Step 2 — BIP       : AutoInvoice Exceptions report — 3 error types identified ✓
  Step 3 — OTBI      : Receivables Transactions exceptions queried ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — All 28 errors categorized, resolution paths identified
════════════════════════════════════════════════════════════
  Documentation      : KB article generated from BIP and ESS output
  Fusion Audit Trail : AutoInvoice Corrections changes logged in Fusion audit trail
  SR Reference       : N/A — all errors resolved via Fusion UI
════════════════════════════════════════════════════════════

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-AR-0142-001

Fusion AR AutoInvoice — 28 Records Rejected: Closed GL Date, Missing Customer, Duplicate Reference

Oracle Fusion Cloud · Accounts Receivable

● RESOLVED

Symptom

Root Cause

Tables

Fusion AutoInvoice Interface — origSystemBatchName: OMS-FUSION-INVOICES, glDate: 31-JAN-2026 (22 records)
ESS Job ID: ESS-2026-04481, status: Succeeded with Warnings

Fix Applied

Prevention

Documentation Page	Title	Scenario
Manage Accounts Receivable Balances	Manage Accounts Receivable Balances	Fusion AutoInvoice error categories and resolution paths
Oracle Fusion General Ledger	Using Analytics and Reports for Financials	Reconciliation reporting after AutoInvoice ESS job corrections

AutoInvoice Diagnostic (Oracle Fusion)

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in AR-07

Documentation Before Every Action — AR-07

Pre-Action Documentation — AR-07

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

Most Common Issues Detected by AR-07

Import AutoInvoice ESS Failure

Invalid Customer or Site in Fusion

Closed Period GL Date

Tables & Views 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 AR-07

Documentation Before Every Action — AR-07

Pre-Action Documentation — AR-07

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

Most Common Issues Detected by AR-07

Import AutoInvoice ESS Failure

Invalid Customer or Site in Fusion

Closed Period GL Date

Tables & Views Examined

How Every Resolution Decision Is Made

Nothing Acts Without a Documented State

Every Execution Produces a Record

Oracle Documentation References

Related Diagnostic Scripts

AR Period Close (Fusion)

AP Invoice Validation (Fusion)

GL Period Close (Fusion)

Ready to Resolve This in Your Environment?