SAP recently announced the release of SAP S/4HANA 1610, the third major on-premise release of SAP S/4HANA, which most experts believe is the first release of S/4HANA that ‘mainstream’ customers can adopt. It covers most industry capabilities, delivering innovation for all lines of business. This release focuses on core supply chain enhancements including embedded Extended Warehouse Management (EWM) and Master Data Governance (MDG), embedded Software in Product Development (PLM), simplifies Product & Portfolio Management (PPM) and a has a new UX for International Trade Compliance (GTS).
SAP’s Simplification List for SAP S/4HANA, on-premise edition 1610 outlines everything that has changed, reviewing over 400 pages and hundreds of cases. According to SAP: “they expect a typical customer system will be affected by an average of 30 to 40 of the currently 300 Simplification Items.” You can check some of the potential impacts in our previous S/4HANA 1511 blog post.
Every company I’ve talked to who’s already in the process of moving to S/4HANA describes the move as a “journey.” A 2-3 year project which usually starts in Finance and will slowly unfold across all other areas of the business. The good news for Winshuttle customers is that your organization is better prepared than most to take on this implementation. Let me explain why.
1. Winshuttle customers have less custom code in their SAP landscapes
SAP encourages customers to use the move to SAP S/4HANA as an opportunity to validate existing extensions and modifications, and simplify their solution. Earlier this year SAP published a white paper sharing shocking key figures based on their Solution Transition Assessment and follow-up services:
- Usage: 65% of custom code objects have not been used within the last 4 weeks
- Similarity: 12% of custom code objects are identical or very similar to each other (clones)
- Quality: 60% of all custom code objects contain code inspection messages
- Criticality: 23% of custom code objects were supporting critical processes
In fact, SAP admits in the S/4HANA FAQs that “it is not unusual for customers to realize 50% of the extensions and modifications that hamper fast release cycles and require long test cycles were no longer necessary to run the business.” In other words, companies don’t need to maintain unused custom code at all, and SAP recommends decommissioning unused custom code because it will cause additional work during each and every major SAP software lifecycle management event.
An SAP S/4HANA transition project is the ideal time to remove waste, an approach that is at the core of everything Winshuttle does. By empowering business users to solve their own data challenges with a flexible and easy-to-use solution, Winshuttle customers can reduce the amount of RICEFW objects (Reports, Interfaces, Conversions, Enhancements, Forms and Workflows) across all SAP modules that require costly ABAP resources.
2. Winshuttle customers don’t need to use LSMW for daily data uploads
The LSMW (Legacy System Migration Workbench) function is still available within SAP S/4HANA, (on-premise edition). However, according to the latest S/4HANA Simplification List, “the use of LSMW for data loading to SAP S/4HANA is not recommended and at the customer’s own risk.” LSMW is an SAP NetWeaver tool for data migration that was first introduced with R/2 to R/3 migrations many years ago, and might propose incorrect migration interfaces that can no longer be used in SAP S/4HANA. Because the use of LSMW is restricted for migrations to SAP S/4HANA, it should only be considered as a migration tool for SAP S/4HANA using workarounds and careful testing for each and every object.
Our customers don’t need to rely on outdated technology like LSMW, (a tool that hasn’t been updated since 2004) for their data migration activities. Winshuttle Studio transaction automation runs smoothly with SAP S/4HANA, and was one of the first SAP vendors to obtain the certification. The main advantage is not only benefiting from the power of automation during initial data migration, but also having the ability to use it as a daily mass data upload solution.
3. Winshuttle customers can manage organizational change more successfully
A significant amount of functionality will change with S/4HANA, and in many cases it might only be available through a Fiori app. Many companies have been running SAP for 10-20 years, and people are used to doing things a certain way. You can’t just revamp the whole user experience in one day – it will be a massive change management effort. Winshuttle users will have a much easier UX transition because they can keep the same Excel templates or web forms as their daily user interface, providing a seamless transition between an ECC system and an S/4 HANA system, increasing user adoption dramatically. If you are not a Winshuttle customer and are planning to implement SAP S/4HANA in the foreseeable future, don’t hesitate to contact us at an early stage, so you can obtain all of these benefits and join a customer base of over 2,000 of the world’s largest companies.
Questions or comments about this article?
Tweet @Winshuttle to continue the conversation!