> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # OOS with Open Sales Order Demand, Oracle ERP Cloud > Items with open Sales Order demand but zero on-hand. The morning purchasing queue, ranked by Sales Order value. How to read it, why it matters, and how to ... **Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Items with open Sales Order demand but zero on-hand. The morning purchasing queue, ranked by Sales Order value. ## At a glance > SKUs with open Sales Order demand but zero on-hand inventory. Each row is a SKU with the SO dollars at risk plus the open SO count. The morning purchasing queue, ranked by SO value descending. The mirror of [Dead Stock with Active Ad Spend](/nerve-centre/kpi-cards/oracle-erp/dead-stock-with-active-ad-spend): under-stocked + has demand vs over-stocked + over-promoted. | | | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `SKU WHERE oracle.on_hand = 0 AND open_so_demand_units > 0`. SO Demand Units sums shipped-quantity-pending across all open Sales Orders for the SKU. | | **Currency** | SO Value at risk in reporting ledger. | | **Channels / sources** | All Order Management SOs across all Business Units. | | **Time window** | Real-time snapshot. | | **Alert trigger** | `any high-value SO blocked` (default \$25K threshold). | | **Roles** | owner, operations | ## Calculation Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A US Fortune 500 industrial-supply distributor on Oracle ERP Cloud. Snapshot 14 Apr 26. **Top 8 OOS-with-SO-demand cases:** | SKU | Description | Open SO units | Open SO value | On hand | Lead time | PO status | | ---------------- | ----------------------- | ------------- | ------------- | ------- | --------- | --------------------- | | BEAR-2080-RB | Roller bearing 80mm | 1,420 | \$284,000 | 0 | 21 days | PO placed 02 Apr 26 | | FILT-ECON-LRG | Industrial econ filter | 840 | \$168,000 | 0 | 14 days | None | | HOSE-HYD-1IN | Hydraulic hose 1" | 612 | \$122,400 | 0 | 28 days | PO arriving 18 Apr 26 | | PUMP-CENT-2KW | Centrifugal pump 2kW | 28 | \$98,400 | 0 | 45 days | None (long-lead) | | FAST-BOLT-M12-A4 | M12 stainless bolt | 8,400 | \$48,800 | 0 | 7 days | PO placed 11 Apr 26 | | SEAL-VITON-50MM | Viton seal 50mm | 1,200 | \$42,000 | 0 | 14 days | None | | GASK-CFG-100 | Compressed-fibre gasket | 2,400 | \$32,400 | 0 | 10 days | PO placed 09 Apr 26 | | VALV-BALL-DN50 | DN50 ball valve | 84 | \$28,400 | 0 | 21 days | None | **Total revenue at risk: \$824,400 across 16 SKUs (top 8 shown).** Five things to notice: 1. **\$284K of revenue is blocked on roller bearings.** A PO was placed 02 Apr 26 with 21-day lead time, so arrival ETA is \~23 Apr 26. Customer SOs are dated 04 Apr to 12 Apr; if delivery commitments are firm at order date + 14 days, there is risk on the older SOs. 2. **FILT-ECON-LRG and SEAL-VITON-50MM have NO PO placed.** This is the actionable signal. Purchasing missed the demand or the system did not trigger a reorder. Drill into the [Low Stock Alerts](/nerve-centre/kpi-cards/oracle-erp/low-stock-alerts) card to confirm reorder logic. 3. **PUMP-CENT-2KW has a 45-day lead time and no PO.** This is the highest-risk row: \$98K of demand and over a month of sourcing time. Customer service likely needs to communicate revised delivery dates. 4. **The cross-platform angle:** Cross-reference [Inventory Sync Drift](/nerve-centre/kpi-cards/oracle-erp/inventory-sync-drift). If commerce platform was showing these SKUs as in-stock when Oracle had zero, the customer order experience just took a hit, and you may have new orders coming in for items that cannot ship. 5. **Action playbook:** Place expedite POs on the no-PO rows immediately. Communicate revised dates to customers on long-lead items. For high-volume items, review the Min/Max planning rules in Oracle Inventory Cloud to ensure auto-reorder triggers are tight enough. ## Sibling cards merchants should reference together | Card | Why pair it with OOS with Open SO Demand | | ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | | [Sales Orders Blocked on Inventory or Credit](/nerve-centre/kpi-cards/oracle-erp/sales-orders-blocked-on-inventory-or-credit) | Inventory Hold subset is the SO-side view of this card. | | [Low Stock Alerts](/nerve-centre/kpi-cards/oracle-erp/low-stock-alerts) | Forward-looking shortage list. | | [Inventory Sync Drift](/nerve-centre/kpi-cards/oracle-erp/inventory-sync-drift) | Whether commerce was showing stock that Oracle says zero. | | [Dead Stock with Active Ad Spend](/nerve-centre/kpi-cards/oracle-erp/dead-stock-with-active-ad-spend) | The mirror leak: this is under-stocked + has demand; that is over-stocked + over-promoted. | | [Open Sales Order Value](/nerve-centre/kpi-cards/oracle-erp/oerp-open-so-value) | Pool from which these blocked SOs are drawn. | ## Reconciling against the vendor's own dashboard **Where to look in Oracle ERP Cloud:** > **Inventory → Reports → Stock Out Items with Demand** > **Order Management → Manage Orders** filtered to inventory-hold reasons > **OTBI → custom analysis joining Inventory Real Time + Order Management Real Time** **Why our list may legitimately differ:** | Reason | Direction | Why | | -------------------------- | --------- | --------------------------------------------------------------------------------------- | | **In-transit treatment** | Either | Card excludes in-transit. If you count in-transit as "available", the OOS list shrinks. | | **Subinventory exclusion** | Either | Quarantine / Damage subinventories excluded by default. | **Cross-connector reconciliation:** | Card | Direction | Notes | | --------------------------------------- | ----------- | -------------------------------------------------------------------------- | | Commerce-platform OOS / low-stock cards | Approximate | Commerce sees its own catalog availability; Oracle is the source of truth. | ## Known limitations / merchant FAQs **Why is this a hero / kill-shot card?** Because it surfaces the exact dollar value of revenue that is blocked due to inventory shortage, with PO status visible. Most ERPs surface the OOS view OR the open-SO view but not the intersection. The intersection is what Operations needs. **Why include in-transit or back-order considerations?** Configurable. Default: in-transit excluded (safer for commitment). If your merchant's sales process commits delivery against in-transit, the field map can include. **Multi-warehouse, can a SKU be OOS in one warehouse and in stock in another?** Yes. The card flags by inventory-org level. A SKU with stock in Warehouse A but zero in Warehouse B (where the SO is sourced) appears here. Drill-down shows per-warehouse. **Can Vortex IQ trigger expedite POs?** Surfaces the candidates; PO placement is a Procurement decision. Ask Viq can route to Procurement with the row context. **Differences vs SAP / NetSuite?** Same logic. Vortex IQ supports all three. *** ### Tracked live in Vortex IQ Nerve Centre *OOS with Open Sales Order Demand* is one of hundreds of KPI pulses Vortex IQ tracks across Oracle ERP Cloud and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.