SAP Solution Manager 7.2 · Change Request Management (ChaRM)

Why can't a Normal change (SMMJ) use the continual cycle, and which cycles must it use?

A normal change must be packaged + sequenced + rigorously tested (sharply reducing production-buffer risk) — which the flexible, one-by-one continual cycle doesn't provide.

So it's not allowed in the continual cycle — it must go in a phase or release cycle. Used for new functionality/features/SAP Note corrections/minor defects.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app. We’re in private beta now; iOS & Android are coming soon.

Join the private beta

Already a tester? Sign in →

More in Change Request Management (ChaRM)

How do email notifications work in ChaRM, and what are they used for?
What must be done before configuring ChaRM?
What can you do in a ChaRM Attachments block, and what does the Advanced button add?
How does ChaRM control the release of the original transport request?
How do you triage which ChaRM transaction type to use for a given change?
What is the Release cycle (SMRE) used for?