SAP Solution Manager 7.2 · Retrofit

When can you start a retrofit, and why retrofit as soon as possible?

Retrofit data is generated when the original transport is released from the maintenance dev system — normal change at successfully tested, urgent at authorized for production.

Retrofit ASAP because the original transport's release is effectively production approval (objects not committed to production shouldn't sync), and retrofit data snapshots the objects at that moment. All transports must be retrofitted before cutover (innovation → maintenance).

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?