SAP Solution Manager 7.2 · Change Request Management (ChaRM)

How do branches and change control landscapes differ as the two dimensions of defining a release track?

  • A branch defines what role a part of the landscape plays.
  • A change control landscape defines which products/systems are in the solution.

Combining the two dimensions makes change-management planning easier — for ChaRM, QGM, and Release Management alike.

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?