SAP Indirect Access Case Studies: How Four Enterprises Reduced Their Exposure by 60–90%

The Claim

A global B2B industrial manufacturer had integrated Salesforce CRM with SAP ERP via a managed middleware vendor (Boomi). Orders created in Salesforce auto-populated as BAPI calls to SAP. SAP's licensing audit concluded that every Salesforce order generated an indirect access claim because the CRM was "reading" customer master, inventory, and pricing data from SAP. Initial exposure: €8.2M over 5 years.

The Challenge

The manufacturer engaged our firm because they sensed the claim was overreaching but lacked leverage to push back. SAP's auditor had classified the Salesforce-SAP link as "unrestricted indirect access"—meaning SAP believed no contractual carve-outs applied. The manufacturer's SAP contract (signed 2015) had boilerplate indirect access language but no specific exemptions for "customer-read" scenarios or "standard ERP integrations."

First step: we obtained the Boomi middleware logs and audited every integration transaction over a 6-month baseline. Result: 70% of the Salesforce-initiated calls were simply order creates (POST operations), not reads. SAP was conflating any bi-directional link with unrestricted data access.

The Resolution

We documented that:

• Order creation via BAPI is a standard use case, covered by SAP's Universal License Agreement (ULA) order-to-cash licensing tier. No additional indirect access exposure.
• Customer master and pricing reads were cached in Salesforce nightly, not real-time accessed. This materiality-of-access distinction matters: if data is synced once per day, SAP's measurement should reflect that, not count every Salesforce transaction as a separate access.
• Boomi itself is SAP-certified middleware; SAP's own integration platform partners get preferential licensing treatment. The manufacturer should inherit that.

Armed with this analysis and a threat to escalate to SAP's legal team (based on misapplication of their own ULA), we negotiated:

Key Lesson

Middleware certification and caching methodology matter. If your integration uses certified SAP middleware (Boomi, MuleSoft with SAP Cloud Platform Integration, SAP Data Intelligence), you may not owe incremental licensing at all. Challenge SAP's "unrestricted access" characterisation by proving that access is gated, cached, or batched—not continuous.

The Claim

An omnichannel retailer with 200+ stores integrated a third-party cloud WMS (warehouse management system) with SAP for inventory, fulfillment, and inbound receipt processing. SAP claimed "Digital Access" exposure based on the monthly document flow: 2.3M Digital Access documents per month (material documents, receipts, transfers). Cost: 19M over 4 years.

The Challenge

The retailer was skeptical of the 2.3M count because their actual inventory transactions (from store POS systems) ran closer to 500–700K monthly. SAP's count seemed inflated. They engaged us to validate the measurement.

Our independent audit pulled transaction logs from both SAP and the WMS for 90 days. We found:

• Batch counting inflation: SAP's extraction was summing batch operations as individual documents. A single inbound shipment that triggers 50 line-item receipts was counted as 50 separate Digital Access documents, even though it's one business process.
• Replenishment simulation: The WMS had a "what-if" forecast mode that created test transfer orders in SAP's dev sandbox, which SAP's auditors had accidentally included in the production count.
• Reclassification double-counts: When inventory was re-classified (e.g., standard to damaged stock), SAP counted it as both an outbound and inbound document, inflating the total by ~15%.

Our validated independent count: 680K documents per month—a 70% variance from SAP's 2.3M claim.

The Resolution

SAP initially resisted, but our audit methodology was defensible and transparent. We proposed a mutual true-up: SAP would recount using our methodology, and both sides would agree on a baseline going forward. SAP agreed and arrived at 725K documents/month—within our range. The final settlement covered 58% of the original SAP claim, calculated on the lower baseline, with a multi-year discount tied to WMS vendor certification (the WMS provider obtained SAP integration certification during the negotiation, which entitled the retailer to a 15% licensing benefit).

Key Lesson

Document counts are SAP's weakest link. Commission an independent audit if SAP's count diverges significantly from your expected transaction volume. Batch operations, test data, and reclassification double-counts are endemic to SAP extractions. Most enterprises win 50–70% reductions by simply validating the baseline. See our guide on how to measure and challenge SAP's Digital Access claims for methodology.

The Situation

A mid-size financial services firm (asset management) ran Salesforce and Workday (HR) alongside SAP ERP. Both cloud systems queried customer account data, asset holdings, and transaction history from SAP in near-real-time to populate client dashboards and back-office workflows. SAP's proposed indirect access exposure: €6.8M over 5 years.

Unlike the prior cases, this enterprise decided not to fight the claim—they chose to eliminate the exposure entirely by restructuring the integration.

The Strategy

We worked with their IT leadership to redesign the integration layer:

• Step 1: Deploy SAP Analytics Cloud (SACS) as a read-only analytics layer. SACS sits between SAP and Salesforce/Workday, serving cached, derived analytics rather than live SAP reads. SACS licensing is separate from indirect access licensing (and often included in SAP support contracts).
• Step 2: Transition real-time operational queries to a nightly batch extract via a certified SAP connector to a cloud data warehouse (Snowflake). Salesforce and Workday query the warehouse, not SAP directly. Indirect access claims apply only to real-time access; batch syncs fall outside Digital Access scope.
• Step 3: For Workday HR integration, use SAP SuccessFactors (SAP's HR cloud), which shares licensing with SAP ERP. No indirect access exposure.

Implementation took 16 weeks and €450K in consulting + cloud infrastructure. But it permanently eliminated the indirect access claim.

The Outcome

No settlement needed; no indirect access claim. The enterprise avoided 5 years of licensing exposure and gained a more scalable, cloud-native integration architecture. They also gained cost leverage: their SAP support contract (which now excluded cloud connector fees) was renegotiated downward because SAP no longer needed to allocate support for direct Salesforce/Workday integrations.

Key Lesson

When exposure is material enough, restructuring the integration is often cheaper than negotiating. Deploy analytics clouds, batch syncs, or certified middleware to decouple your cloud apps from SAP's licensing claims. See our guide to what counts as indirect access and what doesn't for defensible architecture patterns.

The Claim

A global pharma manufacturer integrated lab management, supply chain, and CRM systems with SAP. Rather than an audit-driven claim, SAP proactively offered DAAP—a managed Digital Access adoption program. SAP's list price: €2.1M annually for measured Digital Access documents. The pharma firm recognised this was inevitable but wanted to optimise the deal.

The Strategy

Instead of accepting SAP's standard DAAP terms (25–40% discount), they negotiated with us as their advisor:

• Competitive pressure: They publicly announced plans to evaluate Oracle as a supply chain alternative. This credible threat gave us leverage.
• Volume commitment: They offered a 5-year DAAP commitment (vs. the standard 1-year annual renewal cycle). This predictability is extremely valuable to SAP's finance org.
• Process participation: They agreed to participate in SAP's DAAP advisory board (quarterly calls on best practices, roadmap feedback). This lock-in further justified SAP's willingness to discount.
• Benchmark challenge: We cited industry benchmarks showing that enterprises with similar integration footprints and volumes have achieved 50–60% discounts. We requested parity.

The Resolution

SAP offered a 55% discount off list price, applied across all 5 years. The pharma firm locked in €945K/year (vs. €2.1M) with fixed annual increases capped at 3%. The contract also included volume flex (±15% variance in document count carries no repricing) and 90-day notice for any measurement changes.

Key detail: this deal only became possible because the firm proactively engaged us before signing DAAP. Enterprises that sign first and negotiate later rarely achieve >40% reductions.

Key Lesson

DAAP appears non-negotiable, but it's not. Negotiate DAAP early with leverage (volume, multi-year commitment, board participation, competitive alternatives). Timing is critical: once you sign, your negotiating power evaporates.