> ## 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 Document Demand, SAP > Items with open Sales Document demand but zero on-hand. The morning purchasing queue, ranked by Sales Document value. How to read it, why it matters, and h... **Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Items with open Sales Document demand but zero on-hand. The morning purchasing queue, ranked by Sales Document value. ## At a glance > Materials with open Sales Document demand (confirmed customer orders waiting to ship) but zero or insufficient on-hand stock. The morning purchasing queue, ranked by Sales Document value at risk. The reverse of dead-stock: this is "we have customers but no inventory". Joins SAP's open Sales Document book to the live stock position. | | | | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | For each material with open Sales Documents (`VBAP` lines with un-fulfilled schedule lines), check `MARC.LABST` (on-hand) at the relevant plant. If on-hand \< total open demand, flag the material with: open demand units, on-hand units, shortfall units, total open Sales Document value at risk, top customers waiting. | | **Tax treatment** | Net of tax. | | **Shipping** | Included if Sales Document net value includes freight. | | **Discounts** | Already deducted. | | **Refunds** | n/a (forward-looking). | | **Cancelled / voided orders** | Excluded (rejected lines). | | **Currency** | Group Currency for consolidated views. | | **Plant scope** | Per material per plant. Multi-plant materials shown per plant; cross-plant transfers visible separately. | | **Time window** | `RT` | | **Alert trigger** | `any high-value SO blocked` (threshold default \$50K open value at risk). | | **Roles** | owner, operations | ## Calculation Calculated automatically from your SAP 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 enterprise B2B distributor on S/4HANA Cloud. Snapshot 03 May 26. **Headline:** 22 materials with open Sales Document demand exceeding on-hand stock. \$1,840,000 of Sales Document value at risk. **Top 7 OOS-with-demand cases:** | Material | Plant | Open demand units | On-hand units | Shortfall | Open SO value | Top waiting customer | Action | | -------- | ----- | ----------------- | ------------- | --------- | ------------- | -------------------- | ------------------------------------- | | MAT-A23 | 1010 | 280 | 0 | 280 | \$640,000 | ACME Industries | Expedite production order | | MAT-B41 | 1010 | 120 | 0 | 120 | \$284,000 | Beta Distribution | Cross-ship from plant 1020 (60 units) | | MAT-C18 | 1020 | 480 | 142 | 338 | \$216,000 | Gamma Wholesale | PO with supplier | | MAT-D62 | 1010 | 84 | 0 | 84 | \$148,000 | Delta Manufacturing | Production order priority | | MAT-E55 | 1010 | 240 | 80 | 160 | \$128,000 | Epsilon Trading | Cross-ship + PO | | MAT-F09 | 2010 | 32 | 0 | 32 | \$84,000 | Zeta Industries | Inbound shipment due 06 May | | MAT-G82 | 1010 | 480 | 220 | 260 | \$98,000 | Eta Logistics | PO + production rerun | **Investigation walkthrough:** 1. **MAT-A23 at \$640K is the priority.** ACME Industries has a Sales Document for 280 units that cannot ship; the on-hand is zero. T-code MD04 (stock-requirements list) shows the next production order arrives in 8 days. If ACME has an SLA on delivery date, this is at risk of cancellation and possibly contractual penalties. Immediate action: expedite the production order. 2. **MAT-B41 has cross-ship potential.** Plant 1010 shows 0 on-hand but plant 1020 has 60 units (visible via [Inventory Sync Drift](/nerve-centre/kpi-cards/sap/inventory-sync-drift) or MD04). Half the demand can ship from 1020 today; rest from production. Cross-ship costs $4K but recovers $284K of revenue. 3. **MAT-C18: 480 demanded, 142 on-hand.** Partial shipment is option; full shipment requires a procurement PO. Procurement lead time on this supplier is 14 days. Customer Gamma Wholesale needs to be informed; if they accept partial shipment + back-order, no problem. If they need full shipment, risk of cancellation. 4. **The pattern is the action.** Materials with high-value open demand and zero stock require immediate expedite action. Materials with partial coverage benefit from cross-ship. Materials with adequate inbound supply just need patience. 5. **Cross-platform context:** these are materials where the merchant has actual customer demand, in contrast to [Dead Stock with Active Ad Spend](/nerve-centre/kpi-cards/sap/dead-stock-with-active-ad-spend) where the merchant has stock but no demand. Both signals together tell the merchant where to reallocate working capital. **Action playbook:** * **Daily** in tight-supply periods: Operations runs the morning unblocking off this card. * **Cross-ship from sister plant** if available; recovers revenue at marginal cost. * **Expedite production orders** for materials with internal supply. * **Issue purchase orders** for materials with external supply. * **Customer communication** for materials at risk of missing SLA. ## Sibling cards merchants should reference together | Card | Why pair it with OOS with Open Sales Document Demand | | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | | [Low Stock Alerts](/nerve-centre/kpi-cards/sap/low-stock-alerts) | The trigger condition for OOS materials. | | [Sales Documents Blocked on Inventory or Credit](/nerve-centre/kpi-cards/sap/sales-documents-blocked-on-inventory-or-credit) | Materials here directly cause inventory blocks there. | | [Open Sales Document Value](/nerve-centre/kpi-cards/sap/sap-open-so-value) | The pipeline this card filters. | | [Inventory Sync Drift](/nerve-centre/kpi-cards/sap/inventory-sync-drift) | Drift can hide OOS conditions; reconcile both. | | [Dead Stock with Active Ad Spend](/nerve-centre/kpi-cards/sap/dead-stock-with-active-ad-spend) | The mirror leak: too much stock + no demand vs too little stock + demand. | ## Reconciling against the vendor's own dashboard **Where to look in S/4HANA Cloud:** > **Stock / Requirements List** transaction MD04 (per-material view of demand vs supply) > **Sales Order Fulfilment Issues** Fiori app > **Material Availability** Fiori app > **Embedded Analytics**: CDS view `I_SalesOrderItemSupplyAndDemand` Direct deep-link: `https://my{tenant}.s4hana.cloud.sap/sap/bc/ui2/flp#SalesOrderFulfilment-monitor` **Why our list may legitimately differ from MD04 / Sales Order Fulfilment Issues:** | Reason | Direction | Why | | ------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------- | | **ATP vs gross on-hand** | Either | Card uses gross on-hand by default. MD04 uses ATP (subtracting earlier-promised demand). Toggle in field map. | | **Plant scope** | Either | Card respects dashboard CC scope. | | **Inbound supply window** | Either | MD04 considers planned inbound (production orders, POs). Card by default uses current on-hand only. Configurable. | | **Stock type** | Either | Card excludes consignment / blocked / restricted. | **Cross-connector reconciliation:** | Source | Role | | --------------------------------------------------- | --------------------------------------------------------------------------------------- | | S/4HANA Cloud Sales Documents `I_SalesDocumentItem` | Demand source | | S/4HANA Cloud Stock `I_MaterialStock` | On-hand source | | Commerce platforms | Indirectly via [Inventory Sync Drift](/nerve-centre/kpi-cards/sap/inventory-sync-drift) | ## Known limitations / merchant FAQs **Why is this card different from MD04?** MD04 is per-material; this card is multi-material ranked by SO value at risk. Use MD04 to drill into a single material from this card's row. **Production orders / inbound shipments, do they count?** Configurable. By default, card shows current on-hand only (the worst-case view). Toggle to include confirmed inbound supply if Operations wants the optimistic view. **Customer SLAs, does the card show them?** If your SAP setup uses date-of-confirmation as a Sales Document field, the card surfaces it. Customers with imminent confirmed dates rank higher in the priority list. **B2B vs DTC, behaviour difference?** DTC orders typically have shorter customer-tolerance windows; OOS for DTC means cancellation. B2B with Net-30 terms typically have multi-day flex; OOS often resolves with customer communication and partial-shipment acceptance. **Cross-plant sourcing, does the card surface options?** Yes if you have multi-plant inventory visibility. The card highlights when shortfall in plant A could be covered by stock in plant B. **Multi-Company-Code: cross-CC stock transfer?** Visible but flagged separately because cross-CC transfer is a financial transaction (intercompany invoice in some scenarios), not just a logical move. **T-codes for action?** MD04 (stock-requirements list), CO09 (availability overview), VL10A (delivery due list), MB1B (stock transfer to other plant), ME21N (create PO), CO02 (change production order). *** ### Tracked live in Vortex IQ Nerve Centre *OOS with Open Sales Document Demand* is one of hundreds of KPI pulses Vortex IQ tracks across SAP 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.