Interrupted supply chains due to international conflicts of interest are putting companies under great pressure. In addition, customers are demanding more and more service, which can only be satisfied with innovative business ideas and new technologies such as IoT, automation and artificial intelligence (AI) using traditional ERP systems. There is virtually no alternative to switching to S/4HANA with its countless possibilities in order to master the current challenges and ensure competitiveness. SAP is exerting additional pressure by setting the end of maintenance for the ECC systems for 2027.
SAP user companies are therefore under pressure from several sides to ensure their competitiveness. There is therefore no alternative to switching to the new SAP system as soon as possible. Three paths are open to you:
What do users need to be prepared for when switching over? The most striking change is probably the new structure of the system. The new architecture replaces the classic ERP modules with lines of business (LoB). This means that each LoB comprises processes and functions for a specific business area of the company. An SAP LoB is therefore a logical unit in S/4HANA. The following LoBs exist:
In addition to the new structure, S/4HANA also focuses on the new FIORI user interface with its apps. SAP Fiori can be used on the office computer, but also on the go and even with various mobile devices - from smartphones to tablets, can be personalized (individual adaptation of layouts and fields, etc.) and enables role-based access. In theory, this means that the right information is available to every user at the right time via different user interfaces. Many users now fear that this will fundamentally change the operation of S/4HANA, which could possibly lead to resistance or resentment and reduce their efficiency because they first have to familiarize themselves with the new operating concept. This is a fallacy. In most cases, the introduction of FIORI is not accompanied by the deletion of transactions. The GUI functionality remains 95 to 99 percent the same in S/4HANA. However, some transactions will be removed or replaced in order to reduce parallel concepts for the same functions. For example, the transaction BP (Maintain Business Partner) replaces transactions for maintaining customer and vendor data, or the transaction MIGO (Post Goods Movements) replaces many of the MB* transactions - such as MB01, MB02, MB03, etc.
It turns out that almost all tasks can still be managed in the internalized SAP GUI. Users can therefore operate their processes as usual and are not forced to completely rethink. However, it is also important to be aware that SAP will only map new functionalities and innovations in FIORI in future.
A practical example from the QM area will illustrate this. The topic of "non-conformance management" (NC) has been integrated into QM, which allows defects to be recorded separately from inspection lot processing. However, this non-conformance solution can only be accessed via FIORI. Here, for example, individual defects can be created and processed with measures - for example using the 8D methodology. This involves a systematic approach and consistent documentation of individual solution steps. The approach is based on facts and ensures that product defects are traced back to their causes and avoided in future.
8D follows the logic of the PDCA cycle. The disciplines are:
SAP has also updated the integrated SAP FMEA with the FIORI app "Manage FMEAs". One highlight of the new version is the graphical UI5 user interface with new visualization, which offers various graphical network views to make it easier for those responsible to process their FMEAs. The views are always visualized as network graphics with nodes and lines for easier understanding.
There is also an app that enables simplified handling of initial sample procurement for the supplier. In addition to the standard functionality of working with a user status in the quality info record, the new initial sample processing can now also be defined in the quality info record via the production part release. Once this has been activated, the user must now define the PPAP level in Fiori and add the relevant purchasing document.
Although many things change when switching to S/4HANA, there is no complete break with the old system. Employees can basically work with the new system in the same way as before, as the changes to the SAP GUI are only minimal. However, there are many new functionalities that improve day-to-day work and make it more efficient. These include, for example, real-time insights into the company's processes, graphical overviews of defined key figures as well as contextual information and important aspects of central business process objects. However, these extended, innovative functions require a rethink and the use of the new FIORI apps.