Lesson 5 of 5
From ChaRM to Cloud ALM
11 min
Many SAP teams learned change control in Change Request Management (ChaRM) in SAP Solution Manager: requests for change, change documents of different types, maintenance cycles with phases, and a tightly scripted workflow. Cloud ALM covers the same need with a lighter model. Knowing the differences prevents two mistakes: expecting a one-to-one copy, and throwing away controls you still need.
The timing matters. SAP's transition page states that mainstream maintenance for SAP Solution Manager 7.2 ends on 31 December 2027 and recommends completing the transition to Cloud ALM before then. Contoso's ECC support organization still runs ChaRM today; the S/4HANA program started directly in Cloud ALM.
How the concepts map
| SAP Solution Manager ChaRM | SAP Cloud ALM | What changes for you |
|---|---|---|
| Request for change, with approval | Requirement, with optional approval workflow | The business ask and its approval live on the requirement |
| Change document (normal, urgent, administrative and other types) | Feature (one type) | Urgency is expressed with priority, tags or release, not a separate document type |
| Maintenance cycle and phases | Deployment plan, system groups and releases | Timeboxes replace phase switches |
| Status-driven import and phase locks | Feature statuses that allow or block transport actions | Similar idea, fewer statuses |
| Cross-system object lock, downgrade protection, retrofit | Transport checks (downgrade protection, cross-reference); no native retrofit documented at the time of writing | Plan how you will handle parallel landscapes |
SAP's own learning content frames the difference as change control versus change enablement. ChaRM is the stricter model: every change follows a configured document flow. Cloud ALM favors agility and continuous delivery, deployment on demand, with workflow, approval and history around a single change object. SAP's transition material maps a ChaRM change document to a feature, and a continuous cycle to a deployment plan with system groups.
Transition considerations
- Run the SAP Readiness Check for SAP Cloud ALM against Solution Manager to see what you use today.
- Check SAP Roadmap Explorer for capabilities you rely on, such as specific approvals or retrofit, before you set a switch date.
- Set up transport management for each managed system, then system groups, deployment plans and projects.
- Pilot with a simple, low-risk landscape first; test feature-based transport flows for three-tier and four-tier tracks.
- Decide how open change documents finish: complete them in ChaRM before the switch, or close and recreate them as features.
- Rewrite your change procedure so auditors see the new evidence path: requirement, feature, test runs, history.
- NowECC support stays on ChaRMContoso’s ECC fixes follow the existing urgent and normal change flows
- Program startS/4HANA project in Cloud ALMAll S/4HANA changes are features from day one
- Go-liveS/4HANA production on Cloud ALMECC changes stop except emergencies; ChaRM documents closed out
- Before end of 2027Solution Manager retiredRemaining processes moved; historic change records archived for audit
What to keep from ChaRM
Teams moving off ChaRM often discover that some of their best controls were never in the tool. They were in habits: the change advisory meeting every Tuesday, the rule that nobody imports into production on a Friday, the Basis lead who checks the import queue before each run. Write those down before you switch, decide which ones stay, and give each one a home in the new process. The tool changes; the reasons for the controls do not.
| ChaRM habit at Contoso | Keep? | Home in the new process |
|---|---|---|
| Weekly change advisory meeting | Yes | Luis reviews Ready for Production candidates from a saved Features filter |
| Urgent change with approval by the IT manager | Yes | Feature tagged urgent, very high priority, emergency release, Change Manager approval |
| Phase lock before go-live | Yes, as a rule | Release freeze date in the deployment plan; no new features assigned after it |
| Manual retrofit spreadsheet for dual maintenance | Replace | Covered in the dual maintenance course: a tracked retrofit list per ECC fix |
Deciding which ChaRM habits move with you.
What would you do?
Contoso's auditors ask how urgent changes will be controlled in Cloud ALM, since there is no urgent change document type. What is the best answer from Luis?
- ChaRM is a strict change control model; Cloud ALM favors change enablement around a single feature object.
- Change document maps to feature; continuous cycle maps to deployment plan and system groups.
- Urgency becomes priority, tags and release on a feature, governed by your written procedure.
- Solution Manager 7.2 mainstream maintenance ends 31 December 2027; ChaRM documents do not migrate automatically.
Check your understanding · not graded
Lesson check
1. What does a ChaRM change document map to in Cloud ALM?
2. When does mainstream maintenance for SAP Solution Manager 7.2 end?
3. How is an urgent change typically represented in Cloud ALM?
4. What happens to existing ChaRM change documents when you move to Cloud ALM?