SAP Solution Manager 7.2 · Change Request Management (ChaRM)

What is a Defect correction (SMTM), and why doesn't it need its own approval or new RfC?

It connects directly to TMS and works with normal change to fix defects found in the controlled test phase — allowed only in the test phase (the formal integration-test window, where no new scope is allowed and you technically can't build a new normal change). It's ChaRM's only way to allow new changes in a dedicated test phase.

No approval/new RfC is needed because testing spans the whole release and can't be traced to a specific RfC/normal change — scope is already approved, and dev + test must collaborate to fix.

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?