SAP Solution Manager in Audits: What It Finds

Understanding SAP's compliance and measurement reporting system

SAP Solution Manager is often misunderstood as a support tool. In reality, Solution Manager is SAP's primary audit-preparation system. It consolidates SAP STAR measurement data, usage telemetry, and compliance metrics into a centralized reporting dashboard that auditors will use to build their case against you.

Solution Manager doesn't just report what you're using—it flags what it perceives as non-compliant usage patterns, highlights indirect access risks, and pre-categorizes licensing exposure before your formal audit even begins. Understanding what Solution Manager finds, and how to interpret (and challenge) its findings, is critical to audit defense.

What Is SAP Solution Manager: The Audit Preparation Engine

SAP Solution Manager (now called SAP Cloud ALM in newer deployments) is a centralized system for managing SAP landscapes: upgrades, patches, incident management, and monitoring. But embedded within Solution Manager is a licensing compliance module that continuously evaluates your licensing position.

The compliance module ingests data from:

• STAR measurement output — Indirect access detection, integration point mapping
• USMM telemetry — Usage frequency, Named User activity logs
• System configuration — Which modules you have activated, user counts, license assignments
• LAW trending — Historical usage patterns, peak capacity periods

Solution Manager then generates compliance reports, flags potential licensing gaps, and quantifies exposure. These reports become SAP auditors' primary evidence in audit meetings.

📬 SAP Licensing Intelligence

Get Independent SAP Licensing Insights

Expert analysis on SAP audits, contracts, and cost reduction — direct to your inbox. Corporate email required.

Please use a corporate email address (no Gmail, Yahoo, Hotmail, etc.)

Subscribe — Free Intelligence →

Solution Manager Compliance Reports: The Red Flags

Solution Manager generates standardized compliance reports that audit teams use. These reports highlight specific licensing risk areas:

How Solution Manager Detects Licensing Non-Compliance

Solution Manager uses algorithmic rules to flag compliance issues. These rules are pre-configured to be conservative — meaning they favor SAP's commercial interests.

Example: Named User Under-Licensing Detection

Solution Manager tracks login events from each Named User. If a user logs in 5 times per day but your contract assigns them only a fraction of a Named User license (e.g., a "pool" license shared among 4 users), Solution Manager flags this as under-licensing. The recommendation: purchase more Named User licenses.

Your challenge: Solution Manager's logic assumes each login = full license consumption. But pooled licenses are contractually valid. The tool doesn't account for this.

Example: Indirect Access Threshold Breaching

Solution Manager sets indirect access thresholds (often arbitrary). If your enterprise exceeds that threshold, the system flags it as non-compliant and recommends license expansion. But those thresholds aren't based on your specific contract terms—they're based on SAP's default licensing model.

Your counter: Demand that SAP show how the threshold calculation maps to your contract's actual indirect access definition.

What Solution Manager Doesn't Show (And Why That's Dangerous)

Solution Manager's compliance reports are designed to highlight risk, not contextualize it. They don't show:

• Business justification for usage patterns. Solution Manager sees 50 concurrent users during business hours. It doesn't know if they're all necessary to your business operations.
• Contractual provisions that may justify usage. Your contract may permit named users to "float" (share licenses). Solution Manager won't account for this in its compliance flagging.
• System dependencies and constraints. Maybe you have to keep a development system active for regulatory compliance. Solution Manager will flag this as unnecessary licensing cost.
• Data freshness or frequency requirements. Solution Manager might flag frequent API polling as problematic without understanding if your business operations require real-time data feeds.

This is where Solution Manager becomes dangerous in audits. SAP auditors will present its findings as objective fact, when in reality they're pre-configured recommendations designed to maximize licensing expansion.

Integration with STAR Measurement

Solution Manager doesn't function independently. It directly consumes SAP STAR measurement data and presents STAR's findings in a compliance context.

Example workflow:

1. STAR detects 847,000 API calls from your data warehouse to SAP over 30 days
2. Solution Manager ingests this data and flags it: "Detected indirect access from non-SAP system. Licensing exposure: TBD"
3. Auditors use this Solution Manager flag as the starting point for the indirect access conversation
4. You're now defending against Solution Manager's interpretation of STAR's data, not the raw STAR measurements themselves

This adds a layer of interpretation bias. Solution Manager is making assumptive leaps (API call volume = licensing non-compliance) that you need to challenge directly.

How SAP Auditors Use Solution Manager Reports in Audits

Audit teams have a standard playbook for deploying Solution Manager findings:

Your audit defense needs to account for all three dimensions of SAP's measurement strategy: STAR's raw measurement, Solution Manager's compliance flagging, and SAP for Me's baseline configuration data.

Challenging Solution Manager Findings During Audits

Solution Manager reports are not final determinations. They're SAP's recommended interpretation of your licensing position. You have the right to contest them.

Challenge 1: Demand the Underlying Data

When auditors present a Solution Manager compliance flag, ask: "What is the raw data underlying this finding?" Request STAR logs, USMM telemetry, or LAW trending that supports the flag. Often, the underlying data is much less clear than the flag suggests.

Challenge 2: Cross-Check Against Your Contract

Solution Manager uses generic compliance rules. Your contract may have specific definitions of indirect access, named user counting, or module licensing that differ from SAP's defaults. Force the conversation back to contractual language.

Challenge 3: Propose Alternative Metrics

Solution Manager's metrics are technical. Business metrics might be more favorable. Instead of discussing "API calls per day," discuss "business transactions per day" or "unique users accessing SAP per month." These reframings often reduce the perceived licensing exposure.

Challenge 4: Request Time-Based Context

Solution Manager reports often use static snapshots or averages. Ask for peak periods and baseline periods separately. Maybe your solution has spikes during fiscal close or month-end. That's context Solution Manager doesn't provide.

Solution Manager, USMM, and LAW: The Three-Tool Framework

Solution Manager is one component of SAP's broader measurement framework. It works in coordination with:

• USMM (Universal SAP Metric Monitoring) — Direct usage measurement and Named User tracking
• LAW (License Analytics Workbench) — Historical trending and capacity planning

Together, these three tools create a comprehensive audit strategy. Solution Manager provides the compliance flagging. USMM and LAW provide the historical evidence that supports those flags.

For a complete understanding of how all three measurement tools interact, see our comparison: SAP Measurement Tools Compared: USMM vs LAW vs STAR.