Commerce orders that never created a S/4HANA Cloud Sales Document. Each row is a revenue-leak investigation.
At a glance
Commerce orders (Shopify, BigCommerce, Adobe Commerce, SAP Commerce Cloud) that never created a corresponding S/4HANA Cloud Sales Document. Each row is a revenue-leak investigation: the customer paid, the commerce platform recorded the order, but SAP has no record. Untreated, these become permanent revenue gaps and audit findings.
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: 28 commerce orders unmapped, $214,000 of unbookable revenue at risk.
Investigation walkthrough:
- The dominant cluster: ACME-EU-12 with 3 orders totalling $108K. Single root cause: customer was created in the commerce platform but the corresponding SAP Business Partner (transaction BP, role FLCU01 customer) was never set up. The Functional Analyst creates the BP, the integration retries (manual or automatic depending on middleware), and all 3 orders flow through.
- GAMMA-WEST-LLC blocked by SAP DRC tax classification. The commerce platform sent a tax code that does not match the destination jurisdiction’s e-invoicing rules. SAP’s Document and Reporting Compliance module rejects the Sales Document creation. The Functional Analyst either fixes the tax code mapping in the commerce-platform integration or amends the order tax-classification before retry.
- DELTA-INTL: missing material in SAP master. A material on the order does not exist in SAP. Likely a new product was added on commerce platform without being created in SAP. Master-data team adds the material (transaction MM01), retries.
- EPSILON-MX: Company Code coverage gap. The order’s ship-to is Mexico but the integration was set up to flow into CC 1000 (US Inc) only. Either route MX orders to CC 3000 (MX SA) by configuration, or accept that MX-ship orders out of US Inc happen and configure cross-border tax handling.
- Shopify SP-92438: retry exhausted. Generic integration error, no clear cause. SAP Functional Analyst checks the integration logs (BTP Integration Suite). Often a transient timeout or rate-limit; manual retry usually clears.
- Daily during high-volume periods: SAP Functional Analyst clears the queue. Goal: zero rows by EOB.
- Master-data fixes (BP creation, MM01 material creation) clear most cases.
- DRC / e-invoicing rejections require integration-side tax mapping fixes.
- Repeat offenders (same customer / same material / same plant) suggest a configuration gap that needs structural fix, not just per-order patches.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in S/4HANA Cloud: S/4HANA Cloud has no native unmapped-orders view; this card is unique to Vortex IQ. Closest manual approach: the integration middleware’s error log (SAP Integration Suite, Cloud Platform Integration, MuleSoft, Boomi, etc) plus the commerce platform’s order export. For drill-down once a row is being investigated:Manage Business Partner transaction BP / Fiori app -> create or fix BP record Material Master transaction MM01 / MM02 / MM03 -> create or display material Display Sales Document transaction VA03 -> verify the Sales Document was created after retry DRC error log Fiori app -> for tax-classification rejectionsWhy our list may legitimately differ from the integration log:
Cross-connector reconciliation:
Known limitations / merchant FAQs
My integration retries automatically, why does this card still show unmapped orders? Auto-retries handle transient errors (network blips, rate limits). Master-data errors (missing BP, missing material, tax-classification rejections) require human intervention; auto-retry will exhaust without success. The card surfaces those. What happens if I never fix an unmapped order? It becomes a permanent revenue gap. The customer paid, the commerce platform shows the sale, but SAP has no record so the GL never books it. At year-end, this is an audit finding (cash on bank reconciliation that has no offsetting Sales Document) and likely a forced revenue adjustment. Can I auto-create the Business Partner from the commerce-side data? Some merchants do via SAP Cloud Platform Integration custom flows. It is opt-in and requires careful master-data governance (auto-creating BPs without proper credit limits and tax classifications creates downstream issues). What is the typical resolution time? Best-in-class merchants clear the queue within 4 hours. Most clear within 1 business day. Anything older than 5 days is a process gap. Multi-Company-Code: how does the card route an order to the right CC? The integration uses the order’s ship-to country / region to determine the destination CC. If routing logic is wrong (or absent), orders land in the wrong CC or fail entirely. SAP DRC e-invoicing rejections, are they fixable from the commerce platform? Usually yes. The commerce-platform tax classification needs to align with the destination jurisdiction’s e-invoicing rules. For UK MTD, German DSFinV-K, Indian e-invoicing IRP, Brazil NF-e, the rules differ; integration setup needs jurisdiction-aware tax mapping. T-codes / Fiori apps to clear cases?- BP: Business Partner (create / amend customer master).
- MM01 / MM02: Material Master (create / amend material).
- VA01: Create Sales Order (manual creation if integration cannot retry).
- BTP Integration Cockpit: Integration error log.