An Oracle Fusion purchase order status query should identify the order and its procurement context before interpreting the status. A displayed PO number is a business reference. The API resource key identifies the specific order used for subsequent reads.
Begin with GET /fscmRestApi/resources/11.13.18.05/purchaseOrders?q=OrderNumber='DEMO-PO-1042'&limit=5. The number is synthetic. Oracle's purchase-order collection reference documents the queryable attributes. Encode the value through your client and inspect every matching result.
Verify the procurement business unit and supplier against the request. If several orders match the displayed number, refine the search using documented attributes. Do not treat a first-row selection as a successful identity check. Keep the confirmed business context beside the order key in your diagnostic output.
Read DocumentStatus and the other documented lifecycle fields from the resolved order. Interpret the returned values using the current service reference rather than comparing them with a status string copied from another integration. A document's lifecycle state does not by itself describe every line or delivery schedule.
This Oracle-documented SQL example reads a standard purchase order by synthetic order number and procurement business-unit ID. PO_HEADERS_ALL uses SEGMENT1 for the displayed number. Replace the number and business unit together.
SELECT po_header_id,
segment1 AS order_number,
type_lookup_code,
prc_bu_id,
vendor_id,
vendor_site_id,
document_status,
currency_code
FROM po_headers_all
WHERE segment1 = 'DEMO-PO-1042'
AND prc_bu_id = 300100000000001
AND type_lookup_code = 'STANDARD'
ORDER BY po_header_id;The scope includes the document type because different purchasing documents can share a number. PO_HEADER_ID is the table identifier; obtain the REST item key from the service response. Reporting access and REST visibility can differ.
Check the buyer and supplier information when investigating why the order appears unexpected. A supplier identifier and a supplier-site identifier describe different records. Continue with the supplier-site query if the issue concerns purchasing eligibility or business-unit setup.
Keep the returned self link for the item read. The purchase-order key can be a composite hash. Oracle explicitly directs clients to obtain it from the collection response. Constructing an item path from the displayed PO number bypasses that resolution and can produce a misleading missing-record error.
An apparently missing order can reflect account visibility or the distinction between a draft and the relevant purchase-order resource. Check the requested document stage and current account access before changing the filter broadly. A completed read with no matches is different from an authorization failure.
Fusion Toolkit can save a scoped REST read for inspection, and its purchasing operations can investigate a resolved order. Use the line and schedule guide for delivery and accounting detail. This workflow was reviewed on 8 November 2026.
You can use an LLM with the Fusion Toolkit AI Administrator skill and ask, "What is the current status of purchase order DEMO-PO-1042 in our procurement business unit?" It can retrieve supported Oracle records without requiring you to write the query. Include the business unit so the order is unambiguous.