SAP Solution Manager 7.2 · Change Request Management (ChaRM)

The auto-copy tool misses two things when copying transaction types — what must you fix manually?

It misses the status settings for predecessor/successor document types (so a status change should auto-move the successor/predecessor doc to its next status).

For each status value of each customer ChaRM transaction type, check both the Predecessor Documents and Follow-Up Documents folders, copy the standard entries into the customer namespace, then delete the standard entries.

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?