SAP Solution Manager 7.2 · Retrofit

In SAP Solution Manager's Retrofit functionality, what five scenarios force a manual retrofit instead of an automatic one?

  1. Object check found nothing (target version must equal source original).
  2. Object doesn't exist in the target.
  3. Object locked by another correction document.
  4. Object unsupported by BC Set / Correction Workbench.
  5. Object unsupported by Retrofit (some BW objects, all non-ABAP).

Even when manual, Retrofit provides tracking and reporting so the synchronization remains traceable in SolMan.

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?