4 ms·
The best advice about SAP I've had is that when a company is starting to use SAP, the company must adjust its processes to match the SAP model - not the other w
by theshrike79 7y ago
The best advice about SAP I've had is that when a company is starting to use SAP, the company must adjust its processes to match the SAP model - not the other way around.
If you do it the other way, you'll first spend millions and millions customising SAP and then your project will fail at some point. It will also make all SAP upgrades completely impossible and they will cost millions and millions.
All of the successful SAP stories have been about companies who either match the SAP model already or reconfigure themselves to match it.
All failures are the opposite.
- nsoonhui 7y agoThis nails it. The rest is just commentary.
- warpspin 7y agoWhile I share your general notion that companies better adjust to the process of SAP, I still want to comment on the "impossible to upgrade" part, as that is simply not true. First off, in SAP speech, "customization" is the act of simply adjusting the vast configuration options. This does not affect your upgrade possibilities at all. Even if you go so far as to add custom programming, as long as you (lowest complexity) just have programmed additional "transactions"/reports, you will usually not run into a problem. The system also provides various mechanisms to extend standard transactions via hooks or to extend standard tables and still be able to upgrade without additional effort. I was actually astonished how much customization SAP allows in that regard while still staying compatible to the standard codebase - probably one of the reasons everything is so damn resource hungry, because there are multiple layers of indirection at work to allow this. From a development point of view, the major annoyance here is there are so many different options to extend stuff from different decades, so for some use cases you will use BADIs (https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=133758980 https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=1...), for others "exits" (https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=189893877 https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=1...) and it is all a pain to lookup and locate. The one thing which will get you into trouble is if you manually patch standard programs - which you are able to, the whole business logic comes with sourcecode - and which is usually not necessary.
- jsd3 7y agoThat "customization" definition is not quite right. Configuration is not typically called customization. A lot of companies use "Z" programs (a prefix indicating something is custom) to front-end or augment existing SAP functionality. Companies may also create user-exits in SAP programs, or additional code to run when something happens ("send xx an email when the first sales order for a customer is created", for example). When they upgrade, these additional programs require regression testing. Those programs make upgrades risky, and those programs may need to be rebuilt. Historically, companies built a ton of these customizations, then had issues during upgrades. The most recent model (since S4 and HANA emerged) is to do as much as possible in configuration, and limit customization.
- warpspin 7y agoConfiguration IS typically called customization in SAP. "The Customizing" is SAP speech for the sum of all configuration settings and it IS DEFINED THAT WAY IN THE OFFICIAL DOCUMENTATION, even in the english version (the difference is more blatant in the german version, as "customizen" and "customizing" are not german words, but still used in the german docs to specifically refer to the configuration section of SAP) https://help.sap.com/viewer/521cd184dd2f491a9a4179edb66951c3/7.51.6/en-US/4dae4a3aa1352145e10000000a42189e.html https://help.sap.com/viewer/521cd184dd2f491a9a4179edb66951c3... Let me quote: "The term Customizing refers to the process of system configuration during which the members of the project teams make the required system settings. In the SAP System, Customizing activities are performed through the Implementation Guide (IMG)." And no, this leaves no room for interpretation. The IMG is basically the centralized config setting catalogue of SAP and does not allow programming. It may not be, what is typically meant with customization or with other systems, but in SAP "customization" refers by definition to anything which can be configured WITHOUT programming. All documents clearly differentiate between "customizing" = using the configuration, "extending/programming/development" which would be Z-reports etc., "enhancement" with user exits, BADIs and the like and "modifying", which would be patching the standard programs. And yes, of course upgrades still require testing. But saying it is "impossible" to upgrade just because you have z-reports and the like is plain wrong. Most of the time, especially if we do not speak about a full blown ECC to S4 migration, which involves large scale changes to the underlying database structure of the ERP unlike upgrades within the ECC line itself, you will not require updates to your z reports at all.
- petepete 7y agoMy brother, a SAP consultant, says exactly this.
- swarnie_ 7y agoI work for a competing ERP software house and this is the first bit of advice i give after introducing myself. Customising an ERP can be interesting, keeping it supported and updateable 5/10 years after the guy who wrote the mods retired is a nightmare i've seen one too many times before.
- hef19898 7y agoI have yet to not see it.
- carstenhag 7y agoA perfect example for a failure for this is Lidl's Elwis, they invested 500 million € into it and in 2018 they aborted the entire project. English article: https://www.handelsblatt.com/today/companies/programmed-for-disaster-lidl-software-disaster-another-example-of-germanys-digital-failure/23582902.html?ticket=ST-1784344-eCkejiV7igUviBx35ZI9-ap2 https://www.handelsblatt.com/today/companies/programmed-for-... Key quote: >Unlike many of their competitors, Lidl bases its inventory management system on purchase prices. The standard SAP for Retail software uses retail prices. Lidl didn’t want to change, so the software had to be adapted.
- thdrdt 7y agoBut I still think this is a failure of SAP. What if the business model of Lidl is way better than the standard? Then Lidl is very wise not to follow how SAP works.
- Aeolun 7y agoBut very unwise for choosing SAP. Should have spent 500M on something that fit their needs.
- cc81 7y agoIt is very possible but then that system is not for you. These systems are incredibly complex already and while there will always be some customization you should question yourself if this is where your competitive advantage is? Is Lidl earning more money than their competitors because they base their inventory management system on purchase prices while others do not? Then build/buy a system that handles that and it could very well be worth it if you look at the business case But if it is like that because that is how we started out and we cannot quantify how much better it is...then maybe you should just change your process.
- hutzlibu 7y agoI believe, that the difference between purchase price and retail price is a major and tricky one, if you set for retail, but if you can't solve it for 500 million, then there is something wrong with your software. Also "Critics inside Lidl say that KPS was too slow. But Matthias Nollenberger, a senior manager at KPS who was responsible for overseeing the eLWIS project, says his company was working too short deadlines compared to other similar projects" I belive when you have the choice between aborting 500 million and increasing some deadlines, I doubt they were the problem. It simply was not possible to adobt SAP with reasonable amount of money. And the consulting company or SAP should have said that at some point clearly.