PO-07: Purchase Order Diagnostic (Oracle Fusion)

Oracle Fusion Cloud Purchase Order diagnostics operate through a different toolset than EBS R12. The Fusion REST API for procurement provides full access to PO header, line, schedule, and distribution data via the /procurement/purchaseOrders endpoint. OTBI Purchasing subject areas provide population-level analysis — all POs in a business unit with holds, all POs in a specific approval status, all POs with schedule changes pending acknowledgement. The Manage Orders screen provides the interactive view. None of these require direct database access, and all corrective actions go through Fusion's supported interfaces.

PO schedule acknowledgement failures are a Fusion-specific diagnostic area that does not exist in EBS R12 in the same form. When a Fusion PO schedule (equivalent to a shipment in EBS) is changed — delivery date, quantity, or ship-to location — Fusion can be configured to require supplier acknowledgement of the change before the schedule is considered confirmed. When the supplier has not acknowledged within the required window, the schedule remains in Change Pending status, and AP invoices matching against the unacknowledged schedule may receive a change-pending warning.

The Fusion procure-to-pay close process differs from EBS R12 in that Fusion does not have a separate Purchasing period-close program. The Fusion period close is managed entirely through the Close Monitor in General Accounting — the AP subledger close is the trigger for recognizing that the procure-to-pay cycle for the period is complete. PO accruals in Fusion are handled through the Create Accounting process for the Receipt Accounting application rather than the separate Period-End Accruals program in EBS.

PO-07 provides a structured Fusion PO diagnostic using REST API GET /procurement/purchaseOrders for PO status and hold detail, OTBI Purchasing Transactions subject area for population analysis, BIP PO Output report for complete PO detail, Manage Orders for hold release and amendment, and the Receipt Accounting Create Accounting ESS status for accrual completeness.

REST API PO Detail

GET /procurement/purchaseOrders — full PO header, line, schedule, and distribution data. Approval status, hold flags, schedule acknowledgement status, and change order state all in a single API call.

Schedule Acknowledgement

GET /purchaseOrders/{id}/schedules — acknowledgementRequired and acknowledgedDate fields. Identifies schedules in Change Pending status with the amendment date and supplier portal contact.

OTBI Hold Analysis

Purchasing Transactions subject area — population-level hold analysis across all POs. Identifies hold types, affected PO count, and total dollar amount on hold for the business unit.

Receipt Accounting Status

Create Accounting ESS status for the Receipt Accounting application. Confirms accrual accounting is complete for the period before the period close check is performed.

════════════════════════════════════════════════════════════
  ORACLE FUSION — PURCHASE ORDER DIAGNOSTIC
════════════════════════════════════════════════════════════
  PO Number          : PO-2026-009481
  Supplier           : Global Tech Distributors
  Business Unit      : US Operations BU
  Case Number        : FC-PO-2026-0248
  Report Date        : 23-FEB-2026 10:45:22
════════════════════════════════════════════════════════════

[ STEP 1 — REST API PO DETAIL ]             STATUS: ✗ ISSUE
────────────────────────────────────────────────────────────
  PO Status          : Open ✓
  Approval Status    : Approved ✓
  Schedule Status    : Change Pending — 8 days without acknowledgement ✗
  REST Endpoint      : GET /procurement/purchaseOrders/9481/schedules
  acknowledgementReqd: Y — supplier acknowledgement required
  acknowledgedDate   : null — not acknowledged ✗

[ STEP 2 — AP INVOICE STATUS ]              STATUS: ⚠ WARNING
────────────────────────────────────────────────────────────
  ⚠ 2 AP invoices referencing this PO schedule — change-pending warning
  Invoice AP-2026-00881: $42,100 — pending acknowledgement resolution

[ STEP 3 — OTBI ANALYSIS ]                  STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  No other PO-wide holds — single schedule acknowledgement issue ✓

[ STEP 4 — RECEIPT ACCOUNTING ]             STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  Receipt Accounting Create Accounting — complete for FEB-2026 ✓

════════════════════════════════════════════════════════════
  FUSION DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  Schedule change pending acknowledgement — 8 days
  FIX: Contact supplier for acknowledgement OR disable acknowledgement requirement
════════════════════════════════════════════════════════════

Pre-Action Documentation — PO-07

REST API: GET /procurement/purchaseOrders — pre-action export

OTBI: Purchasing Transactions — PO status export

BIP: PO Output Report — full PO detail saved

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 /procurement/purchaseOrders testedResponse saved ✓

OTBI Purchasing subject area availableVerified ✓

BIP PO Output Report run and savedSaved ✓

Pre-action PO state exportedSaved ✓

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.

GETPurchase Order Header

/fscmRestApi/resources/11.13.18.05/purchaseOrders/{POHeaderId}

Path Parameters

POHeaderId integer — Fusion internal PO header ID

Key Query Parameters

fields POHeaderId,OrderNumber,Status,ApprovalStatus,SupplierName,TotalAmount,CurrencyCode

Response Fields Read

Status — Open, Closed, Cancelled, Finally Closed

ApprovalStatus — current approval workflow state

TotalAmount — PO total in document currency

SupplierName, SupplierSiteCode

GETPO Schedule (Acknowledgement Status)

/fscmRestApi/resources/11.13.18.05/purchaseOrders/{POHeaderId}/lines/{LineId}/schedules

Path Parameters

POHeaderId integer — Fusion internal PO header ID

LineId integer — Fusion internal PO line ID

Key Query Parameters

fields ScheduleId,ShipToOrganizationCode,QuantityOrdered,NeedByDate,AcknowledgmentStatus,AcknowledgedDate

Response Fields Read

AcknowledgmentStatus — REQUIRED, ACKNOWLEDGED, NOT REQUIRED

AcknowledgedDate — date supplier acknowledged (null if not yet acknowledged)

NeedByDate — required delivery date

QuantityOrdered, QuantityReceived, QuantityBilled

GETPO Distributions

/fscmRestApi/resources/11.13.18.05/purchaseOrders/{POHeaderId}/lines/{LineId}/schedules/{ScheduleId}/distributions

Path Parameters

POHeaderId integer

LineId integer

ScheduleId integer

Key Query Parameters

fields DistributionId,ChargeAccountCombination,ChargeAccountId,QuantityOrdered,Amount

Response Fields Read

ChargeAccountCombination — account segments string for validation

ChargeAccountId — internal CCID — cross-reference against active COA accounts

QuantityOrdered, Amount — distribution quantity and value

KB-FC-PO-0248-001 · Script: PO-07

Fusion PO-2026-009481 Schedule Change Pending Acknowledgement — 8 Days

Module: Procurement
Platform: Oracle Fusion Cloud
Status: RESOLVED

Symptom

PO-2026-009481 schedule shows Change Pending status for 8 days. Supplier acknowledgement required but not received. 2 AP invoices referencing the schedule flagged with change-pending warning.

Root Cause

PO schedule delivery date was amended by the buyer on 15-FEB-2026. The acknowledgement requirement was configured for this supplier. The supplier portal notification was sent but the supplier contact did not log in to acknowledge. No escalation configured for unacknowledged changes.

Tables Affected

REST API: GET /procurement/purchaseOrders/9481/schedules — acknowledgementRequired: Y, acknowledgedDate: null, changeOrderStatus: Change Pending
OTBI: Purchasing Transactions — scheduleStatus: Change Pending (8 days)

Fix Applied

Buyer contacted supplier directly — supplier acknowledged the schedule change via the Fusion Supplier Portal. acknowledgedDate updated to 23-FEB-2026 via supplier portal login. AP invoices cleared the change-pending warning on revalidation. Escalation rule added: 3-day unacknowledged change triggers buyer email alert.

Prevention

Acknowledgement escalation rule added for all supplier change orders: 3 business days without acknowledgement triggers buyer notification. PO-07 unacknowledged change report should run weekly for all active POs.

Schedule Change Pending Acknowledgement

A Fusion-specific condition. PO schedule change not acknowledged by supplier within the required window. AP invoices matching the schedule may carry a change-pending warning. PO-07 identifies the schedule, the change, and the supplier portal contact.

Account

Invalid Distribution Account

PO distribution references an inactive account in the Fusion Chart of Accounts. Blocks receipt accounting and AP invoice matching. PO-07 identifies the invalid account from the REST API distribution response and the correction path.

Receipt

Receipt Accounting Create Accounting Error

Receipt Accounting Create Accounting ESS job completed with errors. Accrual journals not generated for the period. PO-07 identifies the error from the BIP Execution Report and the account correction needed.

Import

FBDI PO Import Failure

Bulk PO import via FBDI rejected some records. ESS Import PO job completed with warnings. PO-07 identifies the failing rows and the column-level error from the ESS job output log.

Data Source	Type	Purpose
REST API: /procurement/purchaseOrders	REST	PO header, line, schedule, distribution detail
REST API: /purchaseOrders/{id}/schedules	REST	Schedule acknowledgement status
OTBI: Purchasing Transactions	OTBI	Population-level hold and status analysis
BIP: PO Output Report	BIP	Complete PO detail for documentation
ESS: Receipt Accounting Create Accounting	ESS	Accrual accounting completeness for period

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
Schedule change pending acknowledgement — supplier not responded	Functional First	Contact supplier to acknowledge via Fusion Supplier Portal, or waive acknowledgement via Manage Orders > Schedule > Actions. PO-07 identifies the schedule, change date, and supplier portal contact.
PO distribution account invalid — Fusion COA	Functional First	Correct the account via Manage Orders > Edit > Distributions, or via Manage Chart of Accounts for the account setup. PO-07 identifies the invalid account from the REST API distribution response.
AP invoice on PO_CLOSED hold — schedule closed early	Functional First	Reopen the PO schedule via Manage Orders > Schedules. PO-07 identifies the closed schedule and the unmatched AP invoices referencing it from OTBI.
Receipt Accounting Create Accounting errors	Functional First	Correct the source condition (invalid account) via Manage Chart of Accounts, then resubmit Create Accounting ESS for Receipt Accounting. PO-07 identifies the error from the BIP Execution Report.
PO in Change Order — amendment not approved	Functional First	Approve or reject the change order via Manage Orders > Change History. PO-07 identifies the pending change order from the REST API changeOrderStatus field.
FBDI PO import failure — bulk import error	Functional First	Review the Load Interface File for Import ESS output. Correct the FBDI template and resubmit. PO-07 identifies the failing rows and column-level error from the ESS job output.
AP invoice quantity hold — Fusion three-way match failure	Functional First	Correct the receipt quantity via Manage Receipts or amend the PO schedule quantity via Manage Orders. PO-07 identifies the PO, receipt, and invoice quantities from OTBI and REST API.
PO in Fusion approval loop — recurring approval failure	Oracle Support SR	Persistent approval routing failure after AMX rule correction indicates a Fusion BPM engine issue. PO-07 documents the task history and AMX rule 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

✓

REST API: GET /procurement/purchaseOrders — pre-action export

Exported before any corrective action is taken

✓

OTBI: Purchasing Transactions — PO status export

Exported before any corrective action is taken

✓

BIP: PO Output Report — full PO detail saved

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

PO-07 — Fusion Diagnostic Framework

════════════════════════════════════════════════════════════
  ORACLE FUSION — PO DIAGNOSTIC
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud (no direct DB access)
  Tools Available    : REST API, OTBI, BIP PO Output, Manage Orders
  Pre-Action Export  : REST API PO state saved before any action
────────────────────────────────────────────────────────────
  Step 1 — REST API  : GET /procurement/purchaseOrders/9481 — status retrieved ✓
  Step 2 — REST API  : GET /purchaseOrders/9481/schedules — change pending identified ✓
  Step 3 — OTBI      : Purchasing Transactions — no other holds on this PO ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — Schedule acknowledgement issue identified
════════════════════════════════════════════════════════════
  Documentation      : KB article generated from REST API and OTBI output
  Fusion Audit Trail : PO changes logged in Fusion procurement audit trail
  SR Reference       : N/A — resolved via Manage Orders or acknowledgement setup
════════════════════════════════════════════════════════════

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-PO-0248-001

Fusion PO-2026-009481 Schedule Change Pending Acknowledgement — 8 Days

Oracle Fusion Cloud · Procurement

● RESOLVED

Symptom

PO-2026-009481 schedule shows Change Pending status for 8 days. Supplier acknowledgement required but not received. 2 AP invoices referencing the schedule flagged with change-pending warning.

Root Cause

Tables

REST API: GET /procurement/purchaseOrders/9481/schedules — acknowledgementRequired: Y, acknowledgedDate: null, changeOrderStatus: Change Pending
OTBI: Purchasing Transactions — scheduleStatus: Change Pending (8 days)

Fix Applied

Prevention

Documentation Page	Title	Scenario
Invoice Holds And Releases	Implementing Payables — Fusion Payment Setup	Fusion PO to AP invoice matching and validation reference
Payables	Tables and Views for Financials	Fusion POZ_PO_HEADERS_ALL structure for PO validation

Purchase Order Diagnostic (Oracle Fusion)

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in PO-07

Documentation Before Every Action — PO-07

Pre-Action Documentation — PO-07

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

Schedule Change Pending Acknowledgement

Invalid Distribution Account

Receipt Accounting Create Accounting Error

FBDI PO 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 PO-07

Documentation Before Every Action — PO-07

Pre-Action Documentation — PO-07

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

Schedule Change Pending Acknowledgement

Invalid Distribution Account

Receipt Accounting Create Accounting Error

FBDI PO 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

PO Approval Workflow (Fusion)

AP Invoice Validation (Fusion)

GL Period Close (Fusion)

Ready to Resolve This in Your Environment?