You are here:

Myth: Implementing the SAP Cloud ERP system takes too long and is too complicated

For years, ERP system implementations have been associated with multi-year projects, high consultancy costs, extensive customisation and the risk of going over budget. This perception still influences the way many companies view SAP.

A frequently repeated myth is: ‘Implementing SAP S/4HANA Cloud ERP must be a long, costly and complicated process’. In reality, a modern SAP S/4HANA Cloud implementation — particularly in the Cloud ERP model — bears less and less resemblance to a traditional ‘tailor-made’ project, and increasingly resembles a structured process of rolling out a ready-made, tried-and-tested business standard.

WHAT HAS CHANGED?

The key change lies in moving away from the philosophy of excessive customisation. In traditional ERP implementations – of both SAP ECC and many other systems – companies often attempted to replicate all their existing, local procedures within the system. This resulted in lengthy analyses, numerous modifications, costly development, more complex testing and subsequent problems with updates. SAP S/4HANA Cloud promotes a different approach: fit-to-standard, which involves aligning the organisation with tried-and-tested, predefined processes where this does not provide a competitive advantage. SAP Cloud ALM supports ‘fit-to-standard’ workshops, project schedules, roles, sprints, milestones and SAP Best Practices content.

DOES IMPLEMENTATION HAVE TO START FROM SCRATCH?

In practice, this means that the company does not start with a blank page. SAP provides ready-made process scenarios, pre-configured solutions and best practices for areas such as finance, procurement, sales, warehousing, production, controlling and reporting. Best Practices for SAP S/4HANA Cloud Public Edition are delivered as content ready for activation within the solution, which significantly reduces design and configuration time. Instead of spending months describing how the company ‘has always operated’, you can quickly compare current processes with the SAP standard and make an informed decision about which differences are truly significant.

WHAT REALLY AFFECTS THE COST OF IMPLEMENTATION?

Compared to other ERP systems, this is a significant advantage. Implementations of smaller or local systems may appear cheaper initially, but often require a greater number of customisations, integrations, workarounds and manual procedures. The system can be launched more quickly on a limited scale, but costs subsequently arise for development, maintenance, reporting, and integration with e-commerce platforms, banks, production systems, logistics or analytical tools. With SAP S/4HANA Cloud, the majority of business logic, process controls and integrations are built into the solution’s architecture from the outset. The cost of implementation should therefore be assessed not only in terms of the project price, but also in terms of total cost of ownership, scalability and minimising technical debt.

HOW DOES TECHNOLOGY SUPPORT IMPLEMENTATION?

Tools that support the transformation are also of great importance.

SAP Cloud ALM serves as a platform for managing implementation, testing, tasks and solution monitoring. SAP describes Cloud ALM for Implementation as a central platform that accelerates implementation through predefined processes and task-based content. Importantly, as a SaaS solution, it does not require separate infrastructure, and SAP is responsible for its maintenance, which reduces the total cost of ownership of the ALM tool.  

The second component is SAP Signavio, which helps to analyse, model and optimise business processes. This enables the company to see how processes actually flow, where bottlenecks occur and what changes are needed before implementation, rather than only after the system has gone live. SAP points out that combining Signavio with Cloud ALM creates a path from business strategy to project execution: Signavio supports the analysis and optimisation of processes, whilst Cloud ALM handles the design, development and testing of the solution.  

The third tool is SAP LeanIX, which supports the management of application architecture and the IT landscape. This is particularly important in companies that have built up a large number of on-premises applications, interfaces and spreadsheets over the years. LeanIX helps to organise this landscape, identify dependencies and mitigate the risks of transformation. SAP describes the integration of LeanIX and Cloud ALM as part of best practice for the RISE with SAP transformation.

SUMMARY

The myth of a long and costly SAP implementation stems mainly from experiences with legacy ERP projects, in which the system was heavily customised to suit each client’s specific procedures.
SAP S/4HANA Cloud ERP is based on a different model: pre-defined processes, best practices, the SAP Activate methodology, a ‘fit-to-standard’ approach, and tools such as Cloud ALM, Signavio and LeanIX. This does not mean that every implementation is straightforward — success still requires thorough preparation, sound business decisions and user engagement. It does, however, mean that an SAP project need not be a multi-year endeavour or runaway in terms of cost. With the right scope, project discipline and acceptance of the standard, it can be faster, more predictable and safer than many seemingly ‘lighter’ ERP implementations.

 

Author:

Dariusz Wiśniewski,
Team Manager,
Business Experts & Project Management