ChaRM Retrofit in SolMan 7.0 Ehp1
Our client has a SolMan 7.0 Ehp1 SP26 system in which Retrofit is configured.
When doing the setup for a demo, I noticed that within customizing request, no object check is performed. For example: when I retrofit an object from the DEV system in the maintenance landscape (source system) to the DEV system in the implementation landscape (target system), the object in the target system is simply overwritten. No matter the object in the target is system is newer or not.
Shouldn't SolMan perform a check before performing the retrofit?
Thanks in advance.
we came across similar issues for customising using the retrofit tool, we found that when applying table changes it copied the entries over the top of what was already in the target system. With this in mind to avoid any risk we had to incorporate an additional process that had the developer check the table between source and target development systems (using cross system table comparision of tables) prior to applying the retrofit to see if retrofit was permissable. If not it had to be done manually, although we found it safer to perform the customising retrofit manually in most cases anyway.