Skip to main content
Nerve Centre KPIs · Audit Profile · Sentiment Settings Vortex IQ Nerve Centre tracks 60 KPI pulses for SAP stores. Each metric has its own page: definition, calculation, why it matters, and what to do when it moves. SAP S/4HANA Cloud is the system of record for enterprise commerce, manufacturing, and B2B distribution finance globally. SAP is the world’s largest ERP vendor by revenue and the 800-pound gorilla of enterprise resource planning; S/4HANA Cloud is its modern, in-memory, cloud-native ERP product, the strategic successor to the on-premise ECC product line. Vortex IQ supports it as a first-class connector because enterprise commerce, particularly large multi-channel retail, B2B distribution, and process / discrete manufacturing operations running paid acquisition or D2C alongside their B2B book, is precisely the segment where cross-stack reconciliation pays the largest absolute dollars. A 5% revenue gap on a 5Brun−rateis5B run-rate is 250M of working-capital telemetry the CFO has never had cleanly visualised; SAP knows what was billed in the Sales Document and the Billing Document, but cannot natively see what was placed on the commerce front-end that never reached SAP. The persona running an S/4HANA Cloud dashboard is typically a Finance Manager, an SAP Functional Analyst (FI / SD / MM module), or a VP Finance / VP Controlling at a 500M+revenueenterprise(often500M+ revenue enterprise (often 1B+, frequently global Fortune 500). They live inside the SAP UI’s transaction codes: VA01 to create a Sales Document, VBAK and VBAP to query Sales Document headers and items, VBRK and VBRP for Billing Documents, FB60 for vendor invoices, MIRO for invoice receipts. The Functional Analyst configures Subledger Accounting (SLA), the Document Type configuration, the Account Determination tables, and the Output Determination workflows. The VP Finance reads SAP Analytics Cloud (SAC) dashboards and group-reporting consolidation packs. Multi-entity is handled through Company Codes (one Company Code per legal entity, typically) plus the Group Reporting solution for consolidation. The integration surface for Vortex IQ is the SAP OData APIs exposed via SAP Gateway and SAP API Management at api.sap.com, with OAuth2 authentication, SAP Cloud Identity, or basic auth depending on deployment topology. The three killer findings Vortex IQ surfaces for S/4HANA Cloud customers:
  1. Revenue Gap vs Commerce. The dollar gap between commerce-platform total revenue (Shopify Plus, Salesforce Commerce Cloud, SAP Commerce Cloud / Hybris, Adobe Commerce, BigCommerce) and SAP S/4HANA Cloud GL-booked revenue, broken down by reason: Sales Documents stuck in approval, Billing Documents Pending (the Sales-Document-to-Billing-Document conversion delay, often 7 to 30 days for B2B Net-30 terms), Customer master record mismatches (a commerce customer with no SAP Business Partner record), Material Master gaps (a commerce SKU launched before its Material Master was created in SAP), and Company Code routing errors (an order routed to the wrong legal entity). At enterprise scale, a 3 to 8% gap on a 1Bto1B to 5B run-rate is 30Mto30M to 400M of trapped revenue the Finance team has not previously diagnosed at this granularity. The cross-stack visibility is the value: SAP knows what arrived; Vortex IQ knows what was placed and never arrived.
  2. Dead Stock with Active Ad Spend. The cross-platform kill shot. Materials sitting in SAP Inventory Management (transaction MMBE for Stock Overview) with zero 90-day Material consumption AND active monthly ad spend in Google Ads, Amazon Ads, or Meta Ads. For Fortune 500 retailers and consumer-goods manufacturers with 1M+monthlyadbudgets,thistypicallysurfaces1M+ monthly ad budgets, this typically surfaces 200K to $2M / year of recoverable spend. The SAP Material Master (transaction MM03 for display) is the source-of-truth for the inventory side; the ad platforms’ product feed maps to the Material Number for the spend side. Vortex IQ is the join layer.
  3. Margin Erosion at the Material level. Per-Material margin compression alerts where unit margin has dropped >20 percentage points relative quarter-over-quarter, ranked by annualised dollar impact. SAP’s Profitability Analysis (CO-PA) module is the closest in-SAP equivalent and is enormously powerful, but requires significant Functional Analyst configuration; the Vortex IQ card operates on the GL Detail (table BSEG joined to Material Master) plus standard cost (table MBEW), so it is available without CO-PA configuration. For enterprise merchants with deep CO-PA already in place, Vortex IQ adds the cross-platform ad-spend join that even a fully configured CO-PA cannot deliver natively.
SAP S/4HANA Cloud vs SAP S/4HANA on-premise vs SAP ECC vs SAP Business One. SAP’s portfolio includes multiple ERP products, and Vortex IQ targets specifically S/4HANA Cloud (the modern, cloud-native, in-memory product) because that is the strategic forward-looking SAP deployment. S/4HANA on-premise is the same product on the customer’s own infrastructure; the OData API surface is similar, so Vortex IQ supports both with one connector. ECC (the legacy on-premise ERP, technically out of mainstream maintenance from 2027) requires a different integration approach (RFC / BAPI rather than OData) and is supported on a custom-engagement basis. SAP Business One is the SMB product (under $50M revenue typical); separate connector. The Vortex IQ S/4HANA Cloud connector is built for the strategic enterprise SAP customer, not the SMB or legacy lineage. SAP vs Oracle ERP Cloud vs NetSuite positioning. SAP wins on manufacturing-cost integration (CO-PA, Product Costing, Process Manufacturing depth), supply-chain breadth (IBP, EWM, TM), and any process / discrete manufacturing complexity. Oracle ERP Cloud (Fusion) wins on financial sophistication, project-based ERP, treasury, and enterprise services. Both compete at Fortune 500 / large-enterprise scale; the choice is typically made on industry vertical and existing-stack inertia. NetSuite is mid-market (30Mto30M to 200M) and Sage Intacct is mid-market US dimensional (10Mto10M to 150M); neither is a competitor to S/4HANA Cloud at enterprise scale. Companies migrating up-market from NetSuite or Intacct to S/4HANA Cloud is a recognised pattern; Vortex IQ supports all four ERP connectors so the cross-ERP analytics survive the migration. The AI OS positioning anchor: Vortex IQ joins your S/4HANA Cloud system of record to your live D2C and B2B commerce surfaces. SAP Analytics Cloud reports on what S/4 already knows. Vortex IQ surfaces what S/4 cannot see alone: the gap to commerce, the dead-stock-with-ad-spend, the channel-routing leakage. SAP tells you the canonical truth inside the ERP. Vortex IQ tells you the truth across the whole stack. Cross-connector reconciliation guidance. The Vortex IQ value proposition for SAP S/4HANA Cloud customers is not the in-SAP metrics on their own (SAP Analytics Cloud handles those competently for any merchant willing to invest in SAC dashboard development). It is the join across SAP and the rest of the stack: commerce platforms (Shopify Plus, Salesforce Commerce Cloud, SAP Commerce Cloud / Hybris, BigCommerce, Adobe Commerce), ad platforms (Google Ads, Amazon Ads, Meta Ads), CRM (Salesforce, SAP Customer Experience), payment rails (Stripe, PayPal, Adyen, CyberSource), and observability (Datadog, New Relic, AppDynamics). Every cross-platform card in this catalogue (Revenue Gap, Unmapped Sales Documents, Inventory Sync Drift, OOS with Open Sales Document Demand, Dead Stock with Active Ad Spend) operates on data SAP alone cannot see. The reconciliation patterns in priority order: (1) commerce orders to SAP Sales Documents via Commerce Orders Without SAP Sales Document, the largest revenue-leakage detector; the Sales Document creation workflow (transaction VA01) requires both a Customer master record (Business Partner) and a Material Master, so commerce orders that arrive before either record is created fall through; (2) commerce inventory to SAP Material on-hand by Plant via Inventory Sync Drift, the operational-risk twin of the revenue gap, decomposed by Plant (the SAP equivalent of warehouse / location); (3) SAP Credit Memos (Billing Document type G2) to gateway refund value, the GL-vs-bank reconciliation; (4) SAP slow-moving Materials to ad-platform spend via Dead Stock with Active Ad Spend, the kill shot for ad-spend recovery, joining Material consumption velocity from SAP to spend from Google Ads, Amazon Ads, and Meta Ads. SAP API freshness. SAP S/4HANA Cloud exposes data through OData services published via SAP Gateway and SAP API Management at api.sap.com. Vortex IQ uses the standard OData APIs (API_SALES_ORDER_SRV, API_BILLING_DOCUMENT_SRV, API_MATERIAL_DOCUMENT_SRV, API_BUSINESS_PARTNER, API_GLACCOUNTLINEITEM) for transactional reads, with OAuth2 or SAP Cloud Identity authentication. Refresh cadence is 15 minutes for posted GL data on standard workspaces; real-time event subscription is available where the merchant has SAP Event Mesh enabled. The S/4HANA Cloud OData APIs are dimension-aware in the sense that every line carries Company Code, Plant, Profit Center, Cost Center, and the relevant master data references; queryable but with rate limits configured per pod. Vortex IQ honours per-pod rate limits with adaptive back-off, queueing bulk reads off-peak. Note that legacy SAP ECC on-premise customers running BAPI / RFC integration are supported on a custom-engagement basis, with different freshness characteristics. SAP Analytics Cloud (SAC) complementarity. SAC is SAP’s native analytics layer, deeply integrated with S/4HANA Cloud subject areas via Live Connection. Use SAC for pre-built financial dashboards, period-close reports, group-reporting consolidation packs, and S/4-native KPI tiles. Use Vortex IQ for the cross-stack views SAC fundamentally cannot show because the underlying data lives outside SAP. Both layers running side-by-side is the typical Fortune 500 SAP pattern: SAC for in-SAP truth, Vortex IQ for whole-stack truth. SAC’s strength is that it speaks the SAP semantic model (Company Codes, Plants, Profit Centers, Material Groups) directly; Vortex IQ’s strength is that it joins those SAP semantics to commerce-platform and ad-platform data which SAC has no native bridge to. FAQ-style notes:
  • NetSuite vs SAP S/4HANA Cloud, when to choose which? NetSuite for 30Mto30M to 200M revenue, single ERP footprint, simpler operations, faster time-to-value (~6 to 9 months). S/4HANA Cloud for $500M+ revenue with complex manufacturing, deep supply-chain integration, multi-Company-Code statutory consolidation, and ASC 606 / IFRS 15 sophistication. The ERP migration motion from mid-market (NetSuite, Sage Intacct) to enterprise (S/4HANA Cloud, Oracle ERP Cloud) is well-trodden; Vortex IQ supports all four with the same KPI catalogue framing.
  • S/4HANA Cloud vs S/4HANA on-premise, do they share the same Vortex IQ connector? Yes, the OData API surface is largely shared. S/4HANA Cloud is the strategic forward-looking deployment; on-premise is supported with the same connector subject to the merchant exposing the OData services through SAP Gateway.
  • SAP ECC, do you support it? Yes, on a custom-engagement basis. ECC’s BAPI / RFC integration is structurally different from S/4HANA’s OData; the connector requires SAP NetWeaver RFC SDK access on the merchant side. The card catalogue is the same; the integration plumbing differs.
  • Multi-Company-Code consolidation, how does it affect Vortex IQ cards? Each Company Code is treated as a separate scope. Top-level group consolidated views apply Group Reporting elimination journals; per-Company-Code views show raw inter-co revenue. The dashboard filter respects the chosen scope.
  • Subledger Accounting (SLA) rule customisation in S/4HANA, what to watch for? Custom Account Determination tables can route revenue or COGS to non-standard GL accounts, affecting the standard 4xxxxx revenue / 5xxxxx COGS range assumptions. Confirm Chart of Accounts mapping with the Functional Analyst during onboarding.
  • Profitability Analysis (CO-PA) complementarity? If your account has CO-PA configured, the Vortex IQ margin cards align with CO-PA’s Material-level margin reporting. The Vortex IQ value-add is the cross-platform ad-spend join, which CO-PA cannot deliver natively. Use CO-PA for in-SAP margin sophistication; use Vortex IQ for the cross-stack waste detection (Dead Stock with Active Ad Spend, Margin Erosion with Active Ad Spend).
  • T-codes I should know to read these cards? VA01 / VA02 / VA03 (Sales Document create / change / display), VBAK / VBAP (Sales Document tables, header and item), VBRK / VBRP (Billing Document tables), MM03 (Material Master display), MMBE (Stock Overview), MIRO (Logistics Invoice Verification), FB60 (vendor invoice), F-43 (clear customer), KE30 (CO-PA report execution). Most cards in this catalogue map to data that the Functional Analyst would access through one of these T-codes; Vortex IQ exposes the same data via the OData APIs and joins it across the stack.
  • SAP Commerce Cloud (Hybris) integration, is that the same as the SAP connector? No, separate connector. SAP Commerce Cloud is the commerce-platform product; the SAP connector in this catalogue is the financial-ERP product (S/4HANA Cloud). Most enterprise merchants run both; Vortex IQ joins them with the commerce-to-ERP cross-platform cards.
  • SAP Group Reporting (S/4HANA Cloud Finance) complementarity? Group Reporting handles consolidation, eliminations, and group-level reporting on the consolidated entity. Vortex IQ reads the per-Company-Code data and surfaces the consolidated view via the dashboard filter. For audit-grade group-reporting figures, Group Reporting is the source of truth; Vortex IQ is the operational telemetry layer that keeps the day-to-day view current and joined to the rest of the stack.