Hi Lisa,
In that client's case, we were succesful in activating DIMP_SDUD as well as several other business functions.
It is imperative that you execute your activation in Client 000 and harvest and analyze the logs to confirm what happened. Any intersections with customer changes to SAP code will cause the activation to stop since the program cannot be modified because of a changed origin. This is quite similar to a Support Pack condition. However, we found several areas where configuration was impacted and this guided our testing which was similar in nature to what you would do following a support pack.
Please note that most of the new configuration used to drive the new processes will be in Client 000 only and will need to be copied over to your development client. Total run time for activation in development for activation was just over two hours. In QA and PRD it was much quicker because we used a transport to migrate the activation through the the development path.
The cross system compare tool and Excel will become your best friends :-)
In our case we did 3 full runs in the sandbox before we developed and understood our recipe.
Hope this helps encourage you to proceed. Do not hesitate if you have more specific questions.
Ricky