Should I Stay or Should I Go to S/4HANA ?
Great song by Clash, I used the title of this great song to reflect the question among the existing/potential SAP customers' mind:
Should I stay or should I go now?
Should I stay or should I go now?
If I go there will be trouble
An' if I stay it will be double
So come on and let me know
S/4HANA is the new product that replaces existing Business Suite, has new code-line, has major simplifications in Finance and Logistics. Future destination is S/4HANA no-doubt, but when?
I have started to work on S/4HANA on premise 1511 after couple of days later from the date that it was announced. I was very curios about the new code-line and compatibility layer. I had many questions regarding the existing ERP functionality of new S4CORE which has replaced SAP_APPL. I have shared my findings in my previous post: S/4HANA 1511 Logistics Simplifications Deep Dive Collections - 1
Now the question is obvious: Should I move to S/4HANA or Stay?
Answer is not as simple as the question, but I have a personal roadmap:
1. For Net New Names / New SAP customers / Potential SAP Customers: Go with S/4HANA, it is safe and great, all simplifications are making life easier/faster/real-time without loosing any well-known SAP ERP functionality.
2. For Existing/Experienced/Mature SAP Customers: Migrating to S/4HANA is not a technical migration, please keep in mind. It is something moving from X system to SAP S/4HANA. I mean the version of SAP ERP system that you are using is not important, even if your SAP ERP system is running on HANA. I am strongly recommending you to start with fresh implementation of S/4HANA. Do not try to migrate and convert your existing SAP ERP to S/4HANA if you have such a possibility. Assume that your existing SAP ERP is not SAP product. Remember your first SAP implementation, do the same thing. This way is more safe, fast and cheap.
Cheers,
Sabbatical Leave
8 年Hi Sarhan, thanks for sharing. Am I getting this right? Analytics are not part of level 1 positioning anymore ??? Does that make sense?
S/4 HANA Enterprise Architect
8 年Many thanks for your comments K?vanc, from the Simplification document by SAP, Variant Configuration is available only : The following functionality is disabled in SAP S/4HANA, On Premise 1511: ? Object dependencies of type actions have been documented as obsolete. Creation of object dependencies of type actions isn't possible anymore (e.g. transaction CU01). Configuration models containing actions are still supported and behave like before, but new actions can't be created. ? It's not possible to maintain "Classification as Selection Condition" in Material BOM items anymore (e.g. transactions CS01, CS02). If in Material BOM items classes as selection condition are already maintained, the BOM explosion will work as before. But it's not allowed to use "Classification as Selection Condition" for BOM items, where it wasn't used before. 2.1.11.13.2Business Process related information ? Object dependencies of type procedures should be used instead of type actions. It's recommended to substitute existing actions by procedures in the configuration models. ? Class nodes should be used in Material BOM items instead of "Classification as selection condition". It's recommended to make this substitution also in existing material BOMs. Transaction not available in SAP S/4HANA on-premise edition 1511 CU51E -> Included in CU51 CU52 -> Included in CU51 CU52E -> Included in CU51 CU55 -> Obsolete CU80 -> Use PMEVC instead CUMODEL -> Use PMEVC instead Here is the simplification document : https://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/pdfa4322f56824ae221e10000000a4450e5/1511%20000/en-US/SIMPL_OP1511.pdf
Senior SAP SD Consultant
8 年Sarhan, A nugget/correction about 1. Net New Names: S/4HANA does not have SAP ERP's full scope right now, some functionalities of SAP ERP (i.e. LO-VC) are in the roadmap of S/4HANA, but basically unavaliable as of today. Keep up the good work,
Chief Information Technology Officer @ Graniser Granit Seramik |Victoria Ceramics Turkiye | Leading Digital Transformation
8 年It would better revisit ERP Implementation every decade to catch up Technology, Business Culture and New Generation working habits. So lets start a new must journey to S4 era...