Lesson 4 of 5
Cloud ALM and Solution Manager
7 min
Listen to this lesson
Many SAP customers have run SAP Solution Manager for a decade or more. It holds their process documentation, their change control and their technical monitoring, and in many cases their test management. Understanding how Cloud ALM differs, and what SAP's timeline means, is part of planning any S/4HANA program.
Two different products
| Area | SAP Cloud ALM | SAP Solution Manager 7.2 |
|---|---|---|
| Delivery | Software as a service on SAP BTP, operated and updated by SAP | On-premise system the customer installs, patches and runs |
| Built for | Cloud and hybrid landscapes, including all S/4HANA editions | On-premise and hybrid landscapes, ECC and S/4HANA |
| Process content | SAP Best Practices solution processes and SAP Activate tasks out of the box | Solution documentation the customer builds and maintains |
| Test assets | Test cases built from activities and actions, tied to solution processes; test plans and runs | Test Suite: test steps, test packages and test plans |
| Change control | Features and deployment orchestration | Change Request Management (ChaRM) and Focused Build |
| Updates | Continuous releases by SAP | Support packages the customer applies |
The vocabulary shift trips people up, so learn the main mappings early: a Solution Manager test step becomes a test activity with actions; a test package becomes a test plan; a ChaRM change becomes a feature; and a logical component group becomes a system group. SAP's own terminology page notes that a mapped term does not mean the features are the same.
| Solution Manager term | Cloud ALM term | Note |
|---|---|---|
| Test step | Test activity with actions | An activity is a business step; actions carry instructions and expected results |
| Test package | Test plan | Groups test cases for a cycle and assigns testers |
| ChaRM change | Feature | Carries the transports to production |
| Logical component group | System group | Groups the systems a change or test applies to |
SAP's timeline
- TodayStart new projects in Cloud ALMSAP's guidance is to start new implementation projects in Cloud ALM and finish running ones where they are.
- Before end of 2027Complete the transitionSAP recommends completing the move before Solution Manager 7.2 mainstream maintenance ends on December 31, 2027.
- 2028 to 2030Extended maintenance, selected functionsExtended maintenance to 2030 covers selected areas only, such as test suite, change control and ITSM.
- After thatCustomer-specific maintenanceOn-premise customers keep a perpetual license, but support narrows.
For Contoso, whose S/4HANA program runs well past 2027, starting in Solution Manager would mean finishing in a tool on borrowed time. Starting in Cloud ALM is the safer choice. The ECC estate can keep its existing tools for regression testing until it is switched off.
Transition help from SAP
- SAP Readiness Check for SAP Cloud ALM analyzes how you use Solution Manager today and points to the Cloud ALM functions that replace it.
- An SAP Activate roadmap for the transition to Cloud ALM provides the steps in the same format as an implementation roadmap.
- Selective Data Transfer moves chosen solution documentation from Solution Manager to Cloud ALM one time. It is a migration, not a synchronization.
Running both for a while
Most large customers run both tools during the transition years. The rule that keeps this sane is simple: every artifact has exactly one home, decided by the estate it belongs to. ECC changes and regression stay in the legacy tools. Everything for the S/4HANA program, from scope to defects, goes into Cloud ALM. Write that rule into the program's test strategy so nobody opens a defect in the wrong system.
Two practical consequences follow. Reports for the S/4HANA program come only from Cloud ALM, so nobody has to merge numbers from two tools before a steering meeting. And when ECC is finally switched off, the legacy tools can be archived as a unit, with exports kept for audit, without untangling S/4HANA work that was accidentally stored there.
What would you do?
Contoso's Basis lead proposes migrating all 3,000 ECC test steps and five years of run history from Solution Manager into Cloud ALM "so nothing is lost". Priya has to respond. What is the best position?
- Cloud ALM is SaaS operated by SAP; Solution Manager is an on-premise system you run.
- Learn the term mappings: test step to activity and actions, test package to test plan, ChaRM change to feature.
- Solution Manager 7.2 mainstream maintenance ends December 31, 2027; SAP recommends completing the transition before then.
- Migrate intent, not ECC steps; give every artifact one home during the transition years.
Check your understanding · not graded
Lesson check
1. When does SAP Solution Manager 7.2 mainstream maintenance end?
2. What does a Solution Manager test package correspond to in Cloud ALM?
3. What is Selective Data Transfer?
4. Which tool analyzes current Solution Manager use and suggests Cloud ALM equivalents?