Upgrade from SAP CRM 7.1 to SAP CRM7.2 using SUM10SP11_9-20006540.SAR Error during the Pre-processing Phase shadow_import_inc
FATAL ERROR: Duplicate object LIMU CPUB ‘CL_CRM_ORGMAN_SCENARIO_SALE’ in transport ‘D41K909631’
The transport D41K909631 is our SPAU transport which is released.
Error : Sorting transports to identify identical objects. Marking obsolete
objects (LOCKFLAG ‘2’). Committing. FATAL ERROR: Duplicate object LIMU CPUB ‘CL_CRM_ORGMAN_SCENARIO_SALE’ in
transport ‘D41K909631’. Process with PID 30408930 terminated with status 20 at 20150214093954!
Looking into the error more closely we can see that we do have any duplicate objects which it is complaining about.
Public Header (ABAP Objects) LIMU CPUB CL_CRM_ORGMAN_SCENARIO_SAL
Class Definition (ABAP Objects) LIMU CLSD CL_CRM_ORGMAN_SCENARIO_SALE
I have few other objects of same type . We can see that these are not of duplicate objects.
Solution:
In such a case unfortunately you need to Stop and Reset the Upgrade. Then do not use SPAU as part of your upgrade.
The SPAU Transport can be imported after the upgrade as part of Post Upgrade steps by this way we can avoid this error.
If you have time then open message with SAP and see if they can help
Hy Pradeep,
You can bypass this kind of error with a little trick.
Just add the following line to file OPTIMPIGNORE.LST in directory <SUM>/abap/bin :
igndups: <TP>
e.g. if you have duplicates in SPAU Transport D33K900774
igndups: D33K900774
The original issue is that the same object has been adjusted in the same SPAU transport but in different tasks.
With the trick above you can bypass this check for the SPAU transport.
Regards
Eric
Brilliant tip, Eric!
Definitely did the tric for me 🙂
According to the text in the file, I just added my SPAU-transport to the line that was already there (SUM had already found a support package that needed to be listed here).
Regards,
Gørril