AP-08: AP Supplier Health Diagnostic (Oracle Fusion)

Oracle Fusion Cloud supplier management is distributed across three separate functional areas — the Suppliers work area in Fusion Payables, the Trading Community Architecture (TCA) party model, and the Oracle Payments module. A supplier problem that presents in the AP Invoice Workbench as a payment block may have its root cause in the TCA party record, in the Payments business unit configuration, or in the supplier profile's business unit assignment. Diagnosing the correct layer requires knowing where each piece of supplier data lives in the Fusion data model.

The Fusion Supplier REST API (GET /payables/suppliers) provides access to supplier header data, sites, and bank accounts in a structured JSON response — but the API does not expose every field that the Fusion UI stores in the underlying HZ tables. Supplier holds, for example, are visible in the Manage Suppliers screen but require additional REST calls to the supplier profile endpoint to retrieve the hold type, hold date, and hold placer. The OTBI Supplier subject area provides population-level analysis — all suppliers on hold, all suppliers missing bank accounts, all 1099 suppliers with incomplete tax setup — that the standard Fusion Supplier reports do not produce.

The Fusion Cloud supplier duplicate problem is more complex than in EBS R12 because Fusion's data model enforces stricter uniqueness rules at the TCA party level, but the uniqueness enforcement can be bypassed when suppliers are created via FBDI import without proper pre-validation. A supplier created via FBDI with a name that is 95% similar to an existing supplier but with a different party ID will pass the import validation and create a duplicate that is invisible to the standard Fusion duplicate detection unless the OTBI Supplier subject area is queried with a name similarity filter.

AP-08 provides a structured Fusion supplier health diagnostic using the REST API supplier endpoints, the OTBI Supplier and Supplier Payments subject areas, and the Fusion Payments module configuration screens. It identifies vendor holds, missing bank accounts, incomplete 1099 setup, business unit assignment gaps, and duplicate supplier candidates — with the exact Fusion navigation path or REST API endpoint for each resolution.

════════════════════════════════════════════════════════════
  ORACLE FUSION — SUPPLIER HEALTH DIAGNOSTIC
════════════════════════════════════════════════════════════
  Supplier Number    : SUP-10892
  Supplier Name      : Pacific Rim Consulting LLC
  Business Unit      : US Primary BU
  Tool               : REST API + OTBI + Manage Suppliers UI
  Case Number        : FC-2026-0318
  Report Date        : 24-FEB-2026 09:30:11
════════════════════════════════════════════════════════════

[ STEP 1 — REST API SUPPLIER STATUS ]        STATUS: ✗ FAIL
────────────────────────────────────────────────────────────
  Endpoint           : GET /payables/suppliers/SUP-10892
  Supplier Status    : Active ✓
  Hold Flag          : Y — Hold Type: PAYMENT ✗
  Hold Date          : 15-JAN-2026

[ STEP 2 — BANK ACCOUNT CHECK ]              STATUS: ⚠ WARNING
────────────────────────────────────────────────────────────
  Endpoint           : GET /payables/suppliers/SUP-10892/payees
  Bank Accounts      : 1 found
  Account Status     : Inactive — prenote status: FAILED ⚠

[ STEP 3 — 1099 TAX SETUP ]                  STATUS: ✗ FAIL
────────────────────────────────────────────────────────────
  1099 Type          : MISC
  Federal Tax ID     : Missing ✗
  YTD Reportable     : $48,200.00

[ STEP 4 — OTBI DUPLICATE CHECK ]            STATUS: ⚠ WARNING
────────────────────────────────────────────────────────────
  ⚠ OTBI match: SUP-10445 'Pacific Rim Consulting' — 95% name similarity

════════════════════════════════════════════════════════════
  FUSION DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  3 conditions require resolution: hold, bank account, 1099 tax ID
  All fixes via Manage Suppliers UI or REST API PATCH
════════════════════════════════════════════════════════════

Diagnostic Steps

Fusion diagnostic using REST API /payables/suppliers endpoint, OTBI Supplier and Supplier Payments subject areas, and Manage Suppliers UI. Covers supplier status and hold flags, bank account existence and prenote status, 1099 tax setup completeness, business unit assignments, and duplicate detection.

Backup Created

Fusion Cloud does not permit direct database modification. FBDI supplier export is performed before any bulk supplier update or import retry to provide a point-in-time record of supplier data.

Guided Data Fix

All supplier fixes are applied through Fusion UI or REST API PATCH calls — Manage Suppliers, Manage Payments, Oracle E-Business Tax (replaced by Fusion Tax). AP-08 provides the exact navigation path and API endpoint for each resolution.

KB Article Generated

Complete KB article generated — Fusion supplier number, REST API diagnostic output, hold details, bank account status, 1099 setup findings, duplicate candidates. Upload directly to your knowledge base.

Pre-Action Documentation — AP-08

OTBI: Suppliers — Supplier Profile report export

REST API GET /procurementCommon/suppliers/{id} — response saved

REST API GET /procurementCommon/suppliers/{id}/sites — sites exported

FBDI: Supplier import template export before any corrections

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 GET confirmed for supplierResponse saved ✓

Pre-action OTBI export completedSaved ✓

No import 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.

GETSupplier Profile

/fscmRestApi/resources/11.13.18.05/suppliers/{SupplierId}

Path Parameters

SupplierId integer — Fusion internal supplier ID. Use supplier search endpoint to find it from supplier number.

Key Query Parameters

fields e.g. SupplierId,SupplierNumber,SupplierName,Status,TaxOrganizationType,FederalReportableFlag

Response Fields Read

Status — ACTIVE or INACTIVE

TaxOrganizationType — used for 1099 reporting classification

FederalReportableFlag — Y/N — whether supplier is 1099 reportable

TaxRegistrationNumber — Federal Tax ID

PaymentMethodsFlag — whether payment methods are configured

GETSupplier Sites

/fscmRestApi/resources/11.13.18.05/suppliers/{SupplierId}/sites

Path Parameters

SupplierId integer — Fusion internal supplier ID

Key Query Parameters

q filter expression — e.g. Status=ACTIVE to return only active sites

limit integer — default 25, increase if supplier has many sites

Response Fields Read

SupplierSiteId, SiteName, Status — ACTIVE or INACTIVE

PaymentHoldFlag — Y/N — payment hold at site level

InvoiceCurrencyCode — default invoice currency for the site

PurchasingSiteFlag, PaySiteFlag — whether site is used for PO/payment

GETSupplier Bank Accounts

/fscmRestApi/resources/11.13.18.05/suppliers/{SupplierId}/paymentDetails

Path Parameters

SupplierId integer — Fusion internal supplier ID

Response Fields Read

BankAccountNumber — masked bank account number

BankName, BankBranchName

PrimaryFlag — Y/N — whether this is the primary payment account

ActiveFlag — whether the bank account is active for payment

PrenoteStatus — prenote result: VERIFIED, REQUIRED, or NOT REQUIRED

KB-FC-0318-001 · Script: AP-08

Fusion Supplier Health — Payment Hold, Inactive Bank Account, Missing Federal Tax ID

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

Symptom

Supplier SUP-10892 Pacific Rim Consulting LLC has a PAYMENT hold blocking all invoice entry. Single bank account is inactive with a failed prenote. Federal Tax ID missing on 1099-MISC supplier with $48,200 YTD reportable payments.

Root Cause

Payment hold placed 15-JAN-2026 during payment dispute — not released after resolution. Bank account prenote failed when bank returned NACHA prenote rejection — account was inactivated but not corrected. Federal Tax ID was never entered at supplier creation.

Tables Affected

Fusion Supplier API response — supplierId: SUP-10892, holdFlag: Y, holdType: PAYMENT
Fusion Payees API response — payeeId: PAY-10892, bankAccountStatus: Inactive, prenoteStatus: FAILED

Fix Applied

Payment hold released via Manage Suppliers > Edit > Holds (authorized: AP Manager). Bank account reactivated and new prenote submitted via Manage Suppliers > Banking. Federal Tax ID entered via Manage Suppliers > Tax Organization.

Prevention

Fusion supplier creation workflow should require Federal Tax ID for 1099-MISC suppliers before the record can be saved. AP-08 Fusion supplier health check should run quarterly and before year-end 1099 processing.

Table / View	Schema	Purpose in Diagnostic
REST: /suppliers	REST API	Supplier header active status and holds
REST: /supplierBankAccounts	REST API	Bank account completeness per supplier
OTBI: Procurement — Suppliers	OTBI	Site configuration and payment terms
BIP: Supplier Amendment Workflow	BIP	Amendment backlog in BPM Worklist

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
Supplier on payment hold — hold set in Fusion	Functional First	Remove hold via Manage Suppliers > Edit > Payment Details. AP-08 identifies the hold type (Invoice Hold, Payment Hold, or All Payments) and the navigation path to release.
Inactive bank account — prenote FAILED or inactive status	Functional First	Reactivate or replace the bank account via Manage Suppliers > Banking. AP-08 identifies the bank account ID and the prenote failure reason from the REST API response.
Missing Federal Tax ID — 1099 reporting gap	Functional First	Update Tax Organization Type and Tax ID via Manage Suppliers > Edit > Tax Details. AP-08 identifies the missing field and the 1099 reportable transaction total.
Missing Business Unit assignment	Functional First	Add the BU assignment via Manage Suppliers > Sites. AP-08 identifies which BUs have invoices without a matching supplier site assignment.
FBDI supplier import error — import failure	Functional First	Review the Load Suppliers Scheduled Process output. Correct the FBDI template and resubmit. AP-08 identifies the failing rows and the column-level error from the ESS output.
Duplicate supplier — same legal name or Tax ID	Functional First	Review potential duplicates via Manage Suppliers > Duplicate Identification. AP-08 identifies the candidate pairs from OTBI with invoice history on each. Merge via the Supplier Merge process.
Payment method rules missing	Functional First	Configure payment method rules via Manage Suppliers > Payment. AP-08 identifies the missing payment method assignment and the available methods for the supplier's BU.
Inactive supplier site with open invoices	Functional First	Reactivate the site via Manage Suppliers > Sites > Edit. AP-08 identifies open invoices referencing the inactive site via REST API GET /payables/invoices filtered by supplier and site.

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: Suppliers — Supplier Profile report export

Exported before any corrective action is taken

✓

REST API GET /procurementCommon/suppliers/{id} — response saved

Exported before any corrective action is taken

✓

REST API GET /procurementCommon/suppliers/{id}/sites — sites exported

Exported before any corrective action is taken

✓

FBDI: Supplier import template export before any corrections

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

════════════════════════════════════════════════════════════
  ORACLE FUSION — SUPPLIER HEALTH DIAGNOSTIC
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud (no direct DB access)
  Tools Available    : OTBI, REST API, Manage Suppliers UI, FBDI
  Pre-Action Export  : OTBI Supplier Profile report saved before any action
────────────────────────────────────────────────────────────
  Step 1 — OTBI      : Suppliers subject area — profile data retrieved ✓
  Step 2 — REST API  : GET /procurementCommon/suppliers/SUP-10892 ✓
  Step 3 — REST API  : GET /suppliers/SUP-10892/sites — site status retrieved ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — Supplier conditions identified
════════════════════════════════════════════════════════════
  Documentation      : KB article generated from REST API and OTBI output
  Fusion Audit Trail : Supplier changes logged in Fusion audit trail
  SR Reference       : N/A — resolved via Manage Suppliers 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-0318-001

Fusion Supplier Health — Payment Hold, Inactive Bank Account, Missing Federal Tax ID

Oracle Fusion Cloud · Accounts Payable

● RESOLVED

Symptom

Root Cause

Tables

Fusion Supplier API response — supplierId: SUP-10892, holdFlag: Y, holdType: PAYMENT
Fusion Payees API response — payeeId: PAY-10892, bankAccountStatus: Inactive, prenoteStatus: FAILED

Fix Applied

Prevention

Documentation Page	Title	Scenario
Accounts Payable Manager Job Role	Accounts Payable Manager Job Role	Supplier management privileges and REST access for Fusion
Types Of Holds	Types of Holds — Supplier Site Holds	Fusion supplier hold types and site-level hold configuration
Embedded Banking Services	Embedded Banking Services	Bank account setup and payment method configuration in Fusion

AP Supplier Health Diagnostic (Oracle Fusion)

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in AP-08

Documentation Before Every Action — AP-08

Pre-Action Documentation — AP-08

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

Most Common Issues Detected by AP-08

Supplier Inactive in Fusion

No Bank Account for EFT Supplier

Amendment Stuck in Approval

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-08

Documentation Before Every Action — AP-08

Pre-Action Documentation — AP-08

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

Most Common Issues Detected by AP-08

Supplier Inactive in Fusion

No Bank Account for EFT Supplier

Amendment Stuck in Approval

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

AP Invoice Validation (Fusion)

GL Period Close (Fusion)

Ready to Resolve This in Your Environment?