The time may come in your career as a consulting SAP developer or analyst when you are asked to help de-implement one or more SAP modules from a customer site, including migration of data inside SAP to another product.
Although any consulting SAP developer or analyst will have mixed feelings about participating in such a project, SAP Mentors may feel even worse about doing a de-implementation, since their very mentor status indicates that they have made a significant personal commitment to preaching the virtues of SAP.
But if you think about it, participating in an SAP DE-implementation will actually make SAP mentors better mentors than they were before.
Because in a DE-implemenation situation, SOMEone at the client site is unhappy with SAP in one or more ways – unhappy enough to move to a different product.
And what the mentor can do is get down into the weeds and find out how much of the customer’s happiness is due to true weaknesses in SAP’s product, and how much due to other factors. (I don’t mean what’s wrong with SAP in a general way – I mean – what’s wrong with this transaction, with this screen, etc.)
Such information is as invaluable to SAP (or should be as invaluable) as the most laudatory accolades you hear at Sapphire presentations from customers who just love every detail of SAP to death.
In fact, maybe there should even be a section of SDN/SCN entitled
“Lessons Learned from SAP DE-implementations”
where mentors and others could provide feedback on what they’ve learned about SAP product weaknesses during de-implementation projects.