AP-07: AP Invoice Validation Diagnostic (Oracle Fusion)

Oracle Fusion Cloud AP Invoice Validation failures present differently from their EBS R12 equivalents — the underlying validation logic is similar, but the tooling for diagnosis is entirely different. In EBS R12, a consultant queries the database directly. In Fusion, the diagnostic approach uses Oracle Transactional Business Intelligence (OTBI) reports, the REST API invoices endpoint, Business Intelligence Publisher reports, and the Oracle Fusion Payables UI validation error screens. Each provides a different view of the same validation failure, and the practitioner needs all of them to build a complete picture.

The most common Fusion AP validation failure is a holds condition that is visible in the Manage Invoices screen but whose root cause is not visible without querying the OTBI Invoice Holds subject area or calling the REST API GET /payables/invoices/{invoiceId}/holds endpoint. The Fusion UI shows the hold name — for example, ACCOUNT INVALID — but does not show the specific distribution line, the code combination ID, or the effective date of the account disablement. Those details require an OTBI report or a Scheduled Process output from the Validate Payables Invoices process.

Fusion Cloud also introduces a category of validation issues that does not exist in EBS R12 — issues related to the Payables Integration (FBDI) import process. Invoices imported via the Import Payables Invoices FBDI template can fail at the import stage with errors in the AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables, before they ever reach the validation stage. These failures are reported in the FBDI import output log and the Import Payables Invoices Scheduled Process output, not in the Invoice Workbench or the holds tables.

AP-07 provides a structured diagnostic framework for Fusion AP Invoice Validation failures using the available Fusion tooling — OTBI report queries for holds population analysis, REST API call sequences for individual invoice hold detail, BIP report outputs for validation error summaries, and the FBDI interface table checks for import failures. It maps every hold type to its Fusion-specific resolution path and identifies which conditions can be resolved through the Fusion UI versus which require a Service Request.

OTBI Validation Error Summary

OTBI subject area: Payables Invoices. Invoice status, validation error category, operating unit, aging by error type. Validation error count by period and source.

ESS Job History — Import Payables

ESS job run history for Import Payables Invoices — status, start/end time, error count, log file reference. Identifies failed batches and their last run parameters.

REST API Invoice Status

REST endpoint: /fscmRestApi/resources/11.13.18.05/invoices. Invoice header status, validation status, approval status, hold count. Individual hold detail via REST.

BIP Interface Rejection Detail

BIP report: Payables Invoice Import Exceptions. Full rejection detail by rejection code, line number, and column. Cross-reference to setup tables for each rejection type.

Guided Resolution Navigation

Exact Fusion Cloud navigation paths for each validation error type — Payables > Invoices > Manage Invoices. Workflow task navigation in BPM Worklist. ESS resubmission guidance.

════════════════════════════════════════════════════════════
  ORACLE FUSION — AP INVOICE VALIDATION DIAGNOSTIC
════════════════════════════════════════════════════════════
  Invoice Number     : INV-2026-00445
  Business Unit      : US Primary BU
  Tool Used          : OTBI + REST API + Manage Invoices UI
  Case Number        : FC-2026-0291
  Report Date        : 23-FEB-2026 14:18:02
════════════════════════════════════════════════════════════

[ STEP 1 — MANAGE INVOICES UI ]              STATUS: ⚠ HOLDS
────────────────────────────────────────────────────────────
  Validation Status  : Needs Revalidation
  Holds Count        : 2
  Hold Names         : ACCOUNT INVALID, Quantity Ordered

[ STEP 2 — REST API HOLD DETAIL ]
────────────────────────────────────────────────────────────
  Endpoint           : GET /payables/invoices/445/holds
  Hold 1 Type        : ACCOUNT INVALID
  Hold 1 Line        : Distribution Line 2 — Code Combination: 01.500.7810.000
  Hold 1 Root Cause  : Account disabled in chart of accounts effective 01-JAN-2026
  Hold 2 Type        : Quantity Ordered
  Hold 2 Detail      : Billed: 100, Ordered: 85 — 15 unit overage

[ STEP 3 — RESOLUTION PATH ]
────────────────────────────────────────────────────────────
  Hold 1 Fix         : Manage Chart of Accounts: re-enable account or remap distribution
  Hold 2 Fix         : Amend PO or create quantity correction invoice

════════════════════════════════════════════════════════════
  FUSION DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  2 holds identified via REST API. Resolution paths documented.
  No direct database access — all fixes via Fusion UI or SR.
════════════════════════════════════════════════════════════

Pre-Action Documentation — AP-07

OTBI: Payables Invoices — Invoice Holds report export

REST API GET /payables/invoices/{id}/holds — response saved

BIP: Payables Invoice Import Exceptions report output

ESS: Import Payables Invoices — job output log downloaded

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 ✓

OTBI subject area availableVerified ✓

REST API connectivity testedConfirmed ✓

Pre-action OTBI export completedSaved ✓

ESS job not 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.

GETInvoice Holds

/fscmRestApi/resources/11.13.18.05/invoices/{invoiceId}/holds

Path Parameters

invoiceId integer — Fusion internal invoice ID (not the invoice number). Obtain from the invoice header GET or from OTBI.

Key Query Parameters

limit integer — records per page, default 25, max 500

onlyData boolean — omit HAL metadata from response, set true for cleaner output

Response Fields Read

holdName — Oracle hold code, e.g. ACCOUNT INVALID, QUANTITY ORDERED

holdDate — date the hold was applied

holdReason — free-text reason populated by the hold source

releasedFlag — Y/N — whether the hold has been released

releasedReason — reason for release (populated when releasedFlag = Y)

lineNumber — AP invoice line the hold applies to (line-level holds)

GETInvoice Header

/fscmRestApi/resources/11.13.18.05/invoices/{invoiceId}

Path Parameters

invoiceId integer — Fusion internal invoice ID

Key Query Parameters

fields comma-separated list — restrict response to specific fields, e.g. InvoiceId,InvoiceNumber,ValidationStatus,AccountingStatus

Response Fields Read

InvoiceNumber — supplier-facing invoice number

ValidationStatus — VALIDATED, NEEDS REVALIDATION, INVALID

AccountingStatus — ACCOUNTED, PARTIALLY ACCOUNTED, NOT ACCOUNTED

InvoiceAmount, PaymentStatus, SupplierNumber

GETInvoice Distributions

/fscmRestApi/resources/11.13.18.05/invoices/{invoiceId}/lines/{lineNumber}/distributions

Path Parameters

invoiceId integer — Fusion internal invoice ID

lineNumber integer — invoice line number (1-based)

Response Fields Read

AccountingDate — GL date for the distribution

DistributionCombination — the account code combination string

AccountCodingStatus — VALID or INVALID — whether the account is active

Amount — distribution amount

KB-FC-0291-001 · Script: AP-07

Fusion AP Invoice Holds — ACCOUNT INVALID and Quantity Ordered Holds via REST API Diagnostic

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

Symptom

Oracle Fusion invoice INV-2026-00445 in Needs Revalidation status. Two holds visible in Manage Invoices screen — ACCOUNT INVALID and Quantity Ordered. Invoice blocked from payment.

Root Cause

ACCOUNT INVALID hold: distribution line 2 references account 01.500.7810.000 which was disabled in the chart of accounts effective 01-JAN-2026. Identified via REST API GET /payables/invoices/445/holds. Quantity Ordered hold: 100 units billed against an 85-unit PO — confirmed via OTBI Invoice Matching subject area.

Tables Affected

Fusion AP Invoice Holds (REST API) — invoiceId: 445, holdId: 881, holdType: ACCOUNT INVALID
Fusion AP Invoice Distributions — distributionId: 2, codeCombination: 01.500.7810.000

Fix Applied

ACCOUNT INVALID: Account re-enabled in Manage Chart of Accounts by GL Controller. Invoice revalidated — hold released. Quantity Ordered: PO amended to 100 units by Buyer. Invoice revalidated — approved.

Prevention

Before disabling accounts in Fusion Chart of Accounts, run OTBI report: Payables Invoice Distributions with account filter to identify open distributions referencing target accounts across all business units.

Import Payables Invoices ESS Failure

ESS job completed with errors — common causes: invalid supplier, inactive account combination, closed period. AP-07 identifies the error category and ESS log navigation.

Holds

Fusion Invoice on Hold

Invoice stuck with approval or validation holds. AP-07 navigates to the Manage Holds page, identifies hold type, and provides the release workflow navigation path.

Setup

Account Combination Invalid in Fusion

Distribution account combination is invalid for the chart of accounts. AP-07 provides OTBI query for all invalid combinations and the Account Combinations maintenance path.

Integration

Inbound Invoice Integration Failures

Invoices from external systems failing at the interface layer. AP-07 provides BIP rejection detail and the resubmit or manual correction path.

Table / View	Schema	Purpose in Diagnostic
OTBI: Payables Invoices	OTBI	Invoice status, validation errors, holds
REST: /invoices	REST API	Invoice header and hold detail
BIP: Invoice Import Exceptions	BIP	Interface rejection detail by code
ESS Job History	ESS	Import Payables Invoices run history

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
ACCOUNT INVALID hold — account disabled in Fusion COA	Functional First	Re-enable account via Manage Chart of Accounts, or remap the invoice distribution to an active account via Manage Invoices > Edit Distribution. All changes through Fusion UI — no direct DB access.
Quantity Ordered hold — billed quantity exceeds PO	Functional First	Buyer amends PO via Manage Purchase Orders, or AP creates a quantity correction invoice. Fusion automatically releases the hold on revalidation when the PO is amended.
FBDI import failure — invoice rejected at interface stage	Functional First	Review the Import Payables Invoices Scheduled Process output for the specific error code. Correct the FBDI template data and resubmit. AP-07 identifies the failing rows and the column-level error.
Tax validation failure — Fusion tax engine error	Functional First	Tax errors in Fusion AP are resolved via Manage Tax Rates or by correcting the invoice tax classification. AP-07 identifies the specific tax error code from the validation output.
Approval workflow hold — invoice pending approval	Functional First	Manage Invoice Approval workflow via the Worklist or the invoice approval history screen. AP-07 identifies the current approver and the workflow stage from the REST API holds response.
Closed period GL date — Fusion period status blocking	Functional First	Update the invoice accounting date to a date in an open period via Manage Invoices > Edit. AP-07 identifies the next open Fusion AP period.
Subledger accounting error — Create Accounting fails	Functional First	Correct the source condition (invalid account, missing setup) via the appropriate Fusion setup screen, then resubmit Create Accounting ESS. AP-07 identifies the error from the BIP Execution Report.
Recurring holds after correct setup	Oracle Support SR	Persistent holds after confirmed correct setup indicate a Fusion code defect. AP-07 documents the hold type, frequency, and setup configuration 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

✓

OTBI: Payables Invoices — Invoice Holds report export

Exported before any corrective action is taken

✓

REST API GET /payables/invoices/{id}/holds — response saved

Exported before any corrective action is taken

✓

BIP: Payables Invoice Import Exceptions report output

Exported before any corrective action is taken

✓

ESS: Import Payables Invoices — job output log downloaded

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

AP-07 — Fusion Diagnostic Framework

════════════════════════════════════════════════════════════
  ORACLE FUSION — AP INVOICE VALIDATION DIAGNOSTIC
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud (no direct DB access)
  Tools Available    : OTBI, REST API, BIP, Manage Invoices UI
  Pre-Action Export  : OTBI Invoice Holds report saved before any action
────────────────────────────────────────────────────────────
  Step 1 — OTBI      : Payables Invoices Holds subject area — holds retrieved ✓
  Step 2 — REST API  : GET /payables/invoices/445/holds — 2 holds returned ✓
  Step 3 — BIP       : Import Exceptions report — interface errors categorized ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — Resolution paths identified for all holds
════════════════════════════════════════════════════════════
  Documentation      : KB article generated from REST API and OTBI output
  Fusion Audit Trail : Setup and Maintenance > Audit Reports records all UI changes
  SR Reference       : N/A — both holds 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-0291-001

Fusion AP Invoice Holds — ACCOUNT INVALID and Quantity Ordered Holds via REST API Diagnostic

Oracle Fusion Cloud · Accounts Payable

● RESOLVED

Symptom

Oracle Fusion invoice INV-2026-00445 in Needs Revalidation status. Two holds visible in Manage Invoices screen — ACCOUNT INVALID and Quantity Ordered. Invoice blocked from payment.

Root Cause

Tables

Fusion AP Invoice Holds (REST API) — invoiceId: 445, holdId: 881, holdType: ACCOUNT INVALID
Fusion AP Invoice Distributions — distributionId: 2, codeCombination: 01.500.7810.000

Fix Applied

Prevention

Documentation Page	Title	Scenario
Types Of Holds	Types of Holds — Fusion Payables	Fusion hold types and validation error categories
Invoice Holds And Releases	Implementing Payables: Invoice Holds and Releases	Hold configuration and holds resolution workflow setup
Using Payables Invoice To Pay	Using Payables Invoice to Pay — Fusion Cloud	Import Payables Invoices ESS job failure analysis

AP Invoice Validation Diagnostic (Oracle Fusion)

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in AP-07

Documentation Before Every Action — AP-07

Pre-Action Documentation — AP-07

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

Most Common Issues Detected by AP-07

Import Payables Invoices ESS Failure

Fusion Invoice on Hold

Account Combination Invalid in Fusion

Inbound Invoice Integration Failures

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 AP-07

Documentation Before Every Action — AP-07

Pre-Action Documentation — AP-07

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

Most Common Issues Detected by AP-07

Import Payables Invoices ESS Failure

Fusion Invoice on Hold

Account Combination Invalid in Fusion

Inbound Invoice Integration Failures

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

Supplier Health (Fusion)

GL Period Close (Fusion)

GL Journal Import (Fusion)

Ready to Resolve This in Your Environment?