Solution Manager is licensed differently from most SAP engines. It is not metered against its own usage. It is licensed against the productive landscape it manages, on the principle that Solution Manager's value scales with the size of the SAP environment it supports rather than with its own operational footprint. The derivation is reasonable in theory and produces surprising results in practice, particularly during S/4HANA conversion programmes.
This article explains how the Solution Manager licence is actually derived, the three measurement traps that produce inflated true-up positions, and the surrounding context customers need before they engage SAP on the metric.
How the Solution Manager licence is structured
Solution Manager is included in the SAP ECC and S/4HANA licence under the "Enterprise Support" and equivalent maintenance frameworks. The customer does not buy a separate Solution Manager subscription — the right to use Solution Manager is granted as part of the underlying productive system entitlement, on the basis that the customer needs Solution Manager to operate the productive system effectively.
The grant is not unlimited. The customer's right to use Solution Manager is bounded by the size of the productive landscape that Solution Manager is managing. The boundary is enforced by a measurement that compares the volume of activity in the Solution Manager system — specifically, the number of managed systems, the number of monitored objects, the volume of monitoring data, and certain functional modules — against an entitlement that is derived from the productive landscape.
The mechanism works as long as the productive landscape stays stable. The complications appear when the productive landscape changes shape: during an S/4HANA conversion, during a divestiture, during a major consolidation programme, or during an acquisition where the acquired entity's systems are brought under management by the existing Solution Manager.
The three measurement traps
1. Stranded managed systems
Customers retire productive systems through migrations, consolidations, and decommissioning programmes. The retirement of the productive system removes the underlying entitlement that justified Solution Manager managing it. But the Solution Manager configuration frequently retains the decommissioned system in its managed-system inventory, continuing to monitor it (or its successor in the migrated landscape) under the original configuration.
The trap is that SAP measurement extracts list every managed system, including stranded entries from decommissioned environments. The customer's licence entitlement no longer covers those systems, and the measurement returns a Solution Manager scope that exceeds the entitlement. The correction is a configuration cleanup that removes stranded managed systems before the next measurement, but the cleanup is rarely scheduled as part of system retirement programmes.
2. Test and development inflation
Solution Manager configurations frequently manage not just productive systems but also the surrounding test and development systems, on the legitimate basis that operating the productive system requires managing the entire delivery pipeline. SAP licensing recognises this through a productive-to-non-productive ratio that grants a defined volume of non-productive system management against each productive system.
The trap is that the ratio in the customer's contract is not always the ratio in the SAP measurement framework. Older contract vintages granted generous ratios. Newer contract vintages have tightened the ratios, and customers who layer additional non-productive systems into the Solution Manager configuration without checking the ratio drift over the entitlement. The measurement returns the over-ratio non-productive systems as chargeable, and the true-up follows. See our S/4HANA conversion analysis for how the ratios shift on conversion.
3. Functional module activation
Solution Manager has a modular functional architecture. Some modules — basic system monitoring, technical operations, change management — are included in the standard entitlement. Other modules — certain advanced functions like Business Process Operations, Custom Code Lifecycle Management at scale, certain ALM functions — require additional licensing depending on contract vintage.
The trap is that customers enable advanced functions during projects — a basis architect activates Business Process Monitoring during a stabilisation exercise, an ALM consultant turns on advanced ChaRM features during a release programme — without checking the licensing implication. The function gets used, then forgotten, and surfaces in the next measurement as an unlicensed activation.
The S/4HANA conversion dimension
S/4HANA conversion programmes change the Solution Manager licensing position in several ways simultaneously. The productive system underlying the entitlement changes from ECC to S/4HANA, which may trigger a contract conversion that resets the entitlement framework. The managed-system inventory grows during conversion as the team adds the S/4HANA target system, the conversion landscape, and the surrounding test and quality systems, often before the source ECC system is retired. The functional module mix shifts toward the more advanced Solution Manager functions that S/4HANA conversion programmes typically require.
The cumulative effect is that customers running active S/4HANA conversion programmes typically have Solution Manager configurations that look very different from the configurations they had under the original ECC contract. The measurement framework needs to catch up, and the customer needs to model the new entitlement carefully — ideally before the SAP measurement team does it for them.
The pre-measurement cleanup
A clean Solution Manager measurement requires four cleanup activities in the months before the measurement. The first is a managed-system inventory reconciliation: every system in the Solution Manager inventory should be either currently productive or in active project use, with retired systems removed. The second is a non-productive ratio check: the number of non-productive systems per productive system should be within the contractual ratio, with excess non-productive systems either consolidated or formally licensed. The third is a functional module audit: every activated module should be either within the standard entitlement or licensed under an explicit add-on. The fourth is a configuration documentation refresh: the customer needs a current map of the Solution Manager landscape that supports the eventual measurement submission.
The audit dimension
Solution Manager measurements typically arrive as a sub-section of a broader SAP audit rather than as a standalone exercise. The customer's audit response needs to address the Solution Manager position alongside the broader user and engine measurements. The defensive position is the same three-layer reading we apply to any audit request: the contractual core (current managed system list, monitoring data extracts), the discretionary middle (configuration documentation, change history), and the scope-exceeding tail (internal architecture decisions, third-party SI configurations). See our audit letter response analysis for the boundary framework.
The settlement framework
A defended Solution Manager position typically settles around the same three levers as other engine measurements: a ratio reset that recognises the post-conversion landscape, a functional module true-up at a negotiated rate rather than the list price, and a measurement-cadence agreement that gives the customer a defined window to maintain the cleanup. The settlement is rarely zero — some level of true-up is usually appropriate — but the negotiated outcome routinely sits at 30–60% of the initial measurement.
For the broader engine metric context, see our engine licensing topic page. For the methodology behind the cleanup framework, see our engine metrics decoded white paper. For a worked example of how a Solution Manager position was settled during an S/4HANA conversion, see our manufacturer S/4 conversion case study.