SAP Solution Manager 7.2 · Downgrade Protection & CSOL

How do you activate CSOL locally versus globally, and what's the fallback if SolMan is down?

  • Locally — admin cockpit Landscape Overview → tick CSOL Check per client per dev system.
  • Globally/N/TMWFLOW/CONFIG_LOCKCross-System Object Lock Active.

If SolMan is down, the managed system's report TMW_CONTROL_PROJECT_LOCK can start/stop it directly; afterward reactivate and use TMW_TRKORR_LOCK_UPDATE to backfill the locks missed during downtime.

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 Downgrade Protection & CSOL

What are CSOL's three use cases?
How do you set up CSOL's RFC connection, and what must you avoid?
How do CSOL default and expert modes differ?
What software component must be deployed on SolMan and all managed systems to enable downgrade protection, and how should it be distributed?
What are the five downgrade check types?
What is a downgrade-protection import group, and when do transports belong to the same one?