From my understanding, SLT configurations (mass transfer ID's) are not transportable or have the ability to be migrated between systems in an N-tier landscape. This seems to be due to the specific connection configurations (RFC/DBCo). I can see that as being more of a one time setup.
Now when it comes to some of the more complex transformations and code, and additional table extensions etc, is there a possibility to migrate any of that? I would imagine that the source code that is referred to from the configurations (simple abap programs) are transportable, but anything else that is contained directly in the configuration/mass transfer ID I would presume would have to be rekeyed in each system in the N-tier landscape.
Thanks,
Justin