Sales Documents held by inventory shortage or credit hold in S/4HANA Cloud, ranked by revenue at stake. The morning unblocking queue.
At a glance
The morning unblocking queue: Sales Documents held by inventory shortage, credit hold, or pricing block in S/4HANA Cloud, ranked by revenue at stake. Each row is revenue stuck behind a fixable problem. Combines SAP’s three native block types (delivery block, billing block, credit block from FSCM-CR) into one prioritised list so Finance and Operations can see the unblocking value at a glance.
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 Public Edition. Snapshot 03 May 26 at 8:45am. Headline: 64 Sales Documents blocked, $4,820,000 of revenue at stake. 22 are credit-blocked, 31 are inventory-blocked, 11 are pricing-blocked. Top 8 high-value blocked documents:
Investigation walkthrough:
- **The single biggest unblock is ACME Industries at 42K based on FD32 master record. Two paths: increase the credit limit (typically requires CFO sign-off), or take cash receipt against an existing open Billing Document to free up exposure. Either way, the value released exceeds the threshold by a large margin so it is the morning’s top priority.
- Inventory shortages cluster on three materials. MAT-A23 alone blocks four Sales Documents totalling $920K. Drilling into MD04 (stock-requirements list) shows the production order is 8 days behind. Reprioritising it via MRP could clear the entire cluster.
- Pricing blocks are usually fast. The two pricing-blocked documents are awaiting SD analyst review of a non-standard discount. 30-minute job; $500K released.
- Days-blocked is the secondary urgency signal. A document blocked >7 days is likely missed by the daily Operations huddle; the card surfaces this so it does not get older. The Zeta Industries document at 8 days is the oldest in this snapshot.
- Cumulative working-capital drag. 48K of margin and 2.1M of cash velocity per quarter.
- Run the morning unblocking huddle off this card. Finance handles credit blocks (VKM3, FD32). Supply Chain handles inventory blocks (MD04, CO09, MRP rerun). SD handles pricing blocks (VK11 / VK12).
- Track days-blocked as a SLA metric. Healthy is < 3 days average; > 5 days suggests the operational handoff between Finance and Supply Chain is broken.
- Set the alert threshold at the merchant’s true “high-value” point. Default 1bn-revenue distributor may run at $500K. Tunable per workspace.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in S/4HANA Cloud:Manage Sales Orders, Blocked Fiori app Sales Order Fulfilment Issues Fiori app Released Orders for Credit Limit transaction VKM3 (Finance) List of Sales Documents transaction VA05 with delivery-block / billing-block filtersDirect deep-link:
https://my{tenant}.s4hana.cloud.sap/sap/bc/ui2/flp#SalesOrder-monitorBlockedItems
Why our list may legitimately differ from VKM3 / VA05:
Cross-connector reconciliation:
This card has no commerce-platform counterpart, but ties to:
Known limitations / merchant FAQs
My SAP Functional Analyst says some blocks are “automatic” and not actionable. How does the card handle that? SAP credit blocks are split into manually-set blocks (a Finance user blocked the document) and automatic blocks (FSCM-CR’s Credit Management module set the block based on credit-limit checks). The card surfaces both because both are revenue at stake; the action differs (manual block needs the originating user’s review; automatic block needs limit increase or AR clearance), but the unblocking value is the same. Why is a Sales Document blocked even though my customer paid? Cash applied to the customer (transaction F-30 / FB05) updates the open-items balance, but FSCM-CR’s credit exposure recalculation runs on a schedule (typically nightly via background job). The block remains until exposure is recomputed, even though the underlying receivable is gone. Vortex IQ’s card uses the liveCMGST field, so it shows the block; once exposure recomputes, the card clears it.
What does “delivery block 02 inventory shortage” mean exactly?
The Sales Document line has no schedule-line confirmation because available-to-promise (ATP) check failed at the requested delivery date. The material is either out of stock, blocked by another reservation, or short on the inbound supply. T-code MD04 shows the stock-requirements list; CO09 shows the availability overview.
Can I unblock from the card with Ask Viq?
Limited. Vortex IQ can surface the action and deep-link to the Fiori app or transaction, but the actual block-release in SAP requires the user’s SAP Functional Analyst / Finance role and is performed natively (VKM3 for credit, VA02 for delivery / billing block clearance, with full audit trail). Some merchants build a custom Action API via SAP BTP that Ask Viq can invoke; that is opt-in and requires SAP authorisation work.
Does this card include free-of-charge orders that show as blocked?
FD (free-of-charge) document type is excluded by default since it has no revenue impact. Configurable via field map.
What is the difference between a delivery block and a billing block?
Delivery block (LIFSK) prevents the warehouse from picking and shipping. Billing block (FAKSK) allows shipping but prevents Billing Document creation, often used for “ship now, bill on milestone” projects. Both stall GL revenue.
Multi-Company-Code: do credit limits aggregate?
SAP’s Credit Management can run per Company Code or at the credit-control-area level (which can span Company Codes). The card respects the credit-control-area configuration; if a customer has a $1M shared limit across CC 1000 and CC 2000, the card shows the aggregate exposure consistently with FSCM-CR.
Does the card include sales documents blocked by SAP DRC (Document and Reporting Compliance) for e-invoicing rejections?
Not by default; those are integration errors rather than SAP-internal blocks. They land in the Commerce Orders Without S/4HANA Cloud Sales Document card or the integration error log. Future: a separate “DRC compliance hold” card is planned.