SAP Solution Manager 7.2 · Retrofit

Why maintain a second (innovation) development landscape — six systems instead of three?

  • Put larger-release implementation/testing in a dedicated environment (lowers production risk).
  • The production-support team shouldn't disrupt release/project timelines (hard to align).
  • Bug fixes need an environment close to production.
  • A release cutover into the maintenance landscape must never overwrite objects changed by normal/urgent production changes.

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 Retrofit

What are Retrofit's two layers of object checking?
What must exist in the N+1 dev system before automatic retrofit starts, and how does the ToC get merged?
Retrofit only partially supports SAP BW objects — what two cases force a manual retrofit?
Instead of transporting an object from the source dev system, what does Retrofit actually do in the target system?
On the Retrofit Transport Request Selection screen, what do the Critical Retrofit colors and Retrofit Status values mean?
What are Retrofit's prerequisites?