Open Sales Document Value, SAP

Card class: Card

Live value of all open Sales Documents not yet invoiced in S/4HANA Cloud. The forward revenue book.

​

At a glance

The real-time value of all open Sales Documents in S/4HANA Cloud that are past Sales Document creation but not yet fully billed. The forward revenue book: what is queued to become GL revenue once goods issue and the next billing-due-list run complete. Sums VBAP.NETWR (item net value) across documents in Awaiting goods issue, Partially delivered, Awaiting billing, and Partially billed statuses.

​

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 manufacturer running SAP S/4HANA Cloud Public Edition with three Company Codes (US, MX, CA) and an integrated supply-chain footprint (production-orders, MRP). Snapshot 03 May 26. Five things to notice:

1. **The biggest bucket is Awaiting goods issue ($14.8M).** Most enterprise SAP shops with manufacturing run a configure-to-order or make-to-order pattern. Sales Documents sit in this status until production posts goods receipt, then move to ready-to-ship. The$14.8M is normal for a $280M annual run-rate (about 19 days of forward demand).
2. Awaiting billing ($5.18M) is the immediate billing-due-list candidate. These documents have goods issue posted (warehouse has shipped) but no Billing Document yet. The next VF04 billing-due-list run (typically scheduled weekly via background job) will sweep them into Billing Documents, posting revenue to GL. If the run is late, this bucket grows; if it is on cadence, it stays around 4 to 6 days of run-rate.
3. Pair this card with Sales Documents Blocked on Inventory or Credit. That card filters to the subset blocked by inventory shortage (no schedule line confirmation) or credit hold (FSCM-CR block). For this merchant: $2.18M of the$14.8M Awaiting goods issue is on inventory hold, $640K of which is high-value B2B accounts. Those are the unblocking priorities.
4. Compare to last week’s snapshot. A growing Open Sales Document Value at constant revenue means the order-to-cash pipeline is lengthening (operational drag, billing delays, or supply-chain holds). A shrinking value at constant revenue means the pipeline is healthier or the inbound funnel is slowing. Vortex IQ tracks this as a 7D trend implicitly.
5. Forward-revenue read. With Net-30 terms and an average 14-day delivery-to-billing lag, $5.18M of Awaiting billing converts to Billed (and so to GL revenue) within ~2 weeks. That is the run-rate Finance can take to the bank lender as committed forward revenue.

​

Sibling cards merchants should reference together

​

Reconciling against the vendor’s own dashboard

Where to look in S/4HANA Cloud:

Manage Sales Documents Fiori app (F1873) filtered to status Open Sales Order Fulfilment Issues Fiori app for the blocked subset List of Sales Documents transaction VA05 in SAP GUI for power-user roll-ups Embedded Analytics: CDS view I_SalesDocumentItem filtered to OverallSDProcessStatus = 'A' (Not Yet Processed) or 'B' (Partially Processed)

Direct deep-link: https://my{tenant}.s4hana.cloud.sap/sap/bc/ui2/flp#SalesDocument-manage Why our number may legitimately differ from VA05 / Manage Sales Documents: Cross-connector reconciliation: This card is the SAP-side forward-revenue view; it has no direct commerce-platform counterpart but ties to:

​

Known limitations / merchant FAQs

Why is this number different from the open-order figure my SAP Functional Analyst pulled from VA05? Three usual culprits: document type filter (VA05 may include quotes / returns); status filter (VA05 lets you pick delivery status or billing status independently); currency translation (VA05 in document currency vs this card in Group Currency). Re-run VA05 with this card’s filter scope and the numbers reconcile. Should this number grow or shrink over time? Stable as a fraction of revenue is healthy (typically 12 to 25 days of forward demand for B2B distributors, 5 to 10 days for DTC). Growing at constant revenue means pipeline is clogging. Shrinking at constant revenue means demand is softening or operations are accelerating. Does this include scheduling agreements and contracts? Yes if there are open call-offs or releases against them. Long-term contracts (CQ / WK1) without open call-offs are not in this card; they are forward backlog, not active pipeline. Scheduling agreements (LP / LZ) with open schedule lines count. B2B vs DTC mix, how should it look? DTC documents typically clear within 1 to 3 days (rapid goods issue + same-day or next-day billing). B2B documents on Net-30 terms with delivery-to-billing-due-list lag of 7 to 14 days will dominate the pipeline value. Does this match my SAP Analytics Cloud “Open Sales Orders” KPI tile? SAC’s standard KPI uses the same I_SalesDocumentItem CDS view base. Differences usually trace to filter scope (SAC tiles default to user’s authorisation scope; the card respects the dashboard CC filter explicitly) or to refresh cadence (SAC typically refreshes every 24 hours; this card every 15 minutes). Returns Sales Documents (RE), included? No. RE documents create negative revenue once they bill (Credit Memo); they are not “forward revenue” in the same sense. They are tracked separately on Returns Count and Credit Memo Value. T-codes for drilling in? VA05 (list of Sales Documents), VA03 (display single document), VL10A / VL10B (delivery due list, to see what is shippable), VF04 (billing due list, to see what is billable).

---

​

Tracked live in Vortex IQ Nerve Centre

Open Sales Document Value 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 or book a demo to see this metric running on your own data.