How did we start?
We took our CRM 40 development system and copied it to a sandbox system. This sandbox system was transformed from a 32bit non-unicode system to a 64-bit unicode system before the actual 52 upgrade.
Scope of evaluation?
Our goal was to take and see how much would be broken/usable in the new webclient UI. We were expecting most of our previous PCUI customizations to be missing. However could we still do basic “standard” SAP CRM processes post upgrade. In addition we want to see how the standard processes would be performed in the new UI.
Initial areas of pain
1. SGEN, SGEN, and SGEN
Do not even attempt to try out your new system, until this is done.
You will need to have all your security adjusted and added before you can get started.
3. Don’t use the delete option for views in the UI workbench
If you use the delete on a enhancement of standard view, it can and will delete the delivered SAP view object.
4. EEWB for Business Partner beware.
Read note 757955 if you want to avoid short dumps if you created any table extensions with the EEWB for the business partner.
5. Understanding the new UI concepts
If you haven’t done any work with the IC webclient then your learning curve is going to be very steep. Learning how to do extensions in the IC webclient on a earlier release CRM 40 or CRM 52 will prepare you for learning the new web UI. Luckily we did some IC webclient work in our 40 system, so the new UI concepts aren’t completely foreign.
After going through the initial pain points we were able to get our system up and running in relatively quick amount of time We are now starting the UI configuration and process adjustment. We will cover in another blog, our UI/process configuration issues.