How to find the late purchase orders that matter in Oracle Fusion

What Oracle Fusion already gives you

In Oracle Fusion Cloud SCM, everything you need to judge a late purchase order already exists, spread across work areas built for different jobs:

• Purchase orders (Procurement > Purchase Orders): each schedule carries a *Requested Delivery Date* and, once the supplier commits, a *Promised Delivery Date*.
• Receipts (Receipts work area): what is expected and what has arrived against each schedule.
• Item quantities (Inventory Management): on-hand quantity by organization and subinventory.
• Material transactions (Inventory Management, completed transactions): every issue and receipt, which gives you a usage history.
• OTBI reports: the usual way to join purchasing and inventory data into one exportable list.

Each one answers part of the question. None of them ranks your late orders by the stock risk behind them. A past-due purchase order list sorted by date tells you who is late, not who to call first.

The method, step by step

1. List the open schedules past their delivery date

Build an OTBI analysis of open purchase order schedules with item, supplier, ordered and received quantities, requested and promised dates. Keep the schedules still open whose date is before today. Use the promised date when there is one and the requested date otherwise, and flag the schedules without a promise: their date is still your request.

2. Get stock and usage for each item

Take on-hand quantity per item and organization. For usage, sum issue transactions over a fixed window, for example the last 12 weeks, keeping the transaction types that mean consumption or shipment in your plant. Use the same window for every item.

3. Compare days of cover with the real arrival date

Days of cover = on-hand quantity / average daily usage. For each late schedule, take the date you now expect it, and check for another open schedule on the same item that arrives earlier. If cover runs out before any receipt, the line is a shortage risk.

4. Sort by days of cover, shortest first

Among the shortage risks, the item with the fewest days of cover goes to the top. That is your chase list for today. For each line, write down stock, usage, cover, the expected date and days late: when you call the supplier, you are discussing facts.

Illustrative example, not a customer result

Two schedules from the same analysis:

• Schedule A, aluminum extrusion: 8 days late. 2,400 on hand, usage of about 40 a day: 60 days of cover. Another schedule arrives next week.
• Schedule B, servo motor: 3 days late, no promised date. 24 on hand, usage of about 6 a day: 4 days of cover. No other open schedule.

Sorted by days late, schedule A comes first. Sorted by days of cover, schedule B does, and schedule B is the one that can stop production this week.

Where the manual method breaks

• It does not scale. Checking the forecast item by item works for ten late lines, not for two hundred every Monday.
• Usage needs care. New, seasonal or lumpy items make a 12-week average misleading. Flag them rather than trusting the number.
• Dates are only as good as their maintenance. If supplier updates are not entered, the line still carries the original date.
• Days of cover tells you when an item runs out, not which manufacturing order or customer order it affects. Linking the two still needs your planners and your bill of materials.

How WERISCO does it

WERISCO automates the data work behind these steps: it reads every open schedule, computes days of cover for each part and flags late or undated orders by severity, with the evidence on each line. For a first supply chain audit, it starts from two exports you can pull from Oracle Fusion today: on-hand quantity by item and open purchase order schedules. A direct Oracle Fusion connection through the Fusion REST API is built but not yet validated on a customer environment. It reads only; nothing is written back to Oracle, and your team decides what to chase.