SAP Solution Manager 7.2 · Change Request Management (ChaRM)

Why must you never operate on a standard ChaRM transaction type directly, and what do you do instead?

So that maintenance (SAP Notes, support packages) doesn't overwrite your config.

Always copy it into the customer namespace (Z or Y). Adaptations must be made on the copy — never configured or developed in the standard settings.

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?