SAP Solution Manager 7.2 · Retrofit

Why follow a one-to-one rule between maintenance transports and retrofit transports?

Build one retrofit transport per synced maintenance transport (1:1, not many:1).

Many:1 obscures which maintenance transport maps to which innovation transport — harder to troubleshoot and to use auto/semiauto. 1:1 makes Retrofit reports a usable record, eases distinguishing project/maintenance transports at cutover, and gives more visibility and control.

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?