A real replacement for SolMan ChaRM — not a bridge.
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.
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 product to be replaced, not bridged. 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
Every SAP transport request becomes a Change record, synced bidirectionally with STMS. Move it through your CAB, and the platform keeps SAP and TENSOR in step.
Segregation of duties, enforced in code
BAIT 5 separation — developer ≠ approver ≠ Basis admin — is enforced by the platform, not by policy. A pull of your SAP role assignments against a ~50-pattern SoD risk catalogue feeds the Berechtigungskonzept.
Object-level collision detection
Two transports touching the same object surface before they meet in production, not after. Every in-flight transport's object list is scanned on promotion. A forced import still goes through — with an annotation written to the audit log, naming who forced it.
Your landscape, mapped
The DEV → QAS → PRD chain end to end, HANA monitoring, backup status, and CCMS/SolMan alert ingestion — held in the CMDB alongside the rest of your estate.
License measurement, automated
USMM and SLAW license measurement runs against your systems, feeding license management and true-up evidence.
On-prem and cloud, 1 adapter
Dual authentication covers SAP ECC, S/4HANA on-prem, S/4HANA Cloud, BTP, SolMan, and Cloud ALM — RFC for on-prem, OAuth for cloud.
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 replacement — 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.