A successor path for SolMan ChaRM — cut over on evidence, not on faith.
Solution Manager 7.2 reaches end of mainstream maintenance in 2027. TENSOR manages your SAP transports as changes, with the segregation of duties, collision detection, and landscape view that ChaRM gave you — and the ITSM platform around it that SolMan never had.
Preview, not yet field-tested. The SAP integration has been tested with SAP-shaped sample data only; no live SAP system has been connected in a customer environment yet. We pilot it with you against a non-productive landscape first.
Cloud ALM doesn't fill the gap ChaRM leaves.
When Solution Manager winds down, mid-size SAP estates lose a change-management capability that SAP's intended successor doesn't fully replace. Enterprise GRC suites can cover it — at enterprise scope and price. For estates without one, the transport process risks falling back to manual tracking, with no enforced segregation of duties and no collision detection.
TENSOR treats this as a successor, not a bridge. Your SAP transports become changes in a platform that also runs your incidents, problems, and CMDB.
What ChaRM did, and the part SolMan never had.
Transport requests as changes
A transport first seen in development becomes a Change, and release and import positions sync from STMS. The import into production closes it. When SAP moves a transport further than its Change allowed, TENSOR records the drift on the Change instead of hiding it.
Segregation of duties, enforced in code
The developer of a transport can neither approve nor import it — enforced by the platform, not by policy. Your SAP role assignments are checked against a curated catalogue of 53 risky role combinations, which feeds the Berechtigungskonzept export.
Object-level collision detection
Two transports touching the same object surface before they meet in production, not after. The object lists of every in-flight transport are compared until it reaches production. Forcing an import past a collision takes the force-import right and a written annotation in the audit log, naming who forced it.
Your landscape, mapped
DEV, QA and PROD per logical system, HANA replication and backup status, and CCMS and Solution Manager alerts raised as incidents — held in the CMDB alongside the rest of your estate.
Licence measurement facts
The agent collects the user-master facts for each scheduled USMM run, and SLAW aggregation counts a named user once at their highest licence type. A formal licence audit still runs USMM in SAP, and scheduling runs and viewing SLAW results have no screen yet.
On-prem and cloud, one module
SAP ECC, S/4HANA on-premises and Solution Manager through a connector agent on your network — TENSOR never opens an RFC connection inward. S/4HANA Cloud, BTP and Cloud ALM through OAuth, with Cloud ALM read-only.
Note: v1 ships schedule-and-confirm transport movement. Fully automatic outbound import via STMS is on the roadmap.
SolMan 7.2: mainstream maintenance ends 2027.
Extended maintenance is available to 2030 for paying customers, but ChaRM investment has stopped. Mid-market SAP estates need a credible successor — not an enterprise GRC suite.
What SAP Basis teams ask first.
Plan your SolMan exit while you have time.
Walk through transport-as-change, SoD, and collision detection against your own landscape. We'll be straight about what ships now and what's on the roadmap.