SAP Solution Manager 7.2 · Retrofit

Why do organizations running dual landscapes (N/N+1) need to retrofit maintenance changes into the innovation landscape?

At a release cutover, objects flow into the maintenance landscape's preproduction then production — so any object successfully tested in the maintenance dev system must be synced to the innovation dev system, or the cutover would overwrite it.

Retrofit automates this sync, keeping the innovation landscape current with near-zero manual effort.

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?