SAP Solution Manager 7.2 · Retrofit

Retrofit only partially supports SAP BW objects — what two cases force a manual retrofit?

  1. Transport variant GUID — some BW objects have different technical IDs on different SIDs (e.g. ISFS/RSDS/TRFN), so they must be manual.
  2. Duplicate GUID — objects generate a GUID at creation, so building the same object in both dev systems produces duplicates in production (e.g. query ELEM, DTPA). Better: don't build in both — transport from maintenance dev to innovation dev.

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?
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?
How does Correction Workbench retrofit merge changes, and what do its three Confirm-Changes colors mean?