EagleBurgmann | S/4HANA-Conversion

Before the project began, EagleBurgmann locations worldwide used around 30 site-specific ERP systems. However, a company data model for digitalisation should be available in a standardised ERP system. The driver for the conversion was therefore a harmonisation of the EagleBurgmann system landscape. The goal was to build an SAP Digital Core, in this case the S/4HANA system, to which all countries would migrate in the long term.

The question of whether a rollout of the existing ECC system would be a better alternative was quickly dropped due to the advantages of S/4HANA and the new business models. The digital core, which will initially be used in Germany, Austria and China, is to be rolled out to the other locations as quickly as possible.

• Provision of a company-wide S/4 digitisation platform for all producing units
• Conversion to S/4 using a hybrid project approach with the best mix of brownfield and greenfield
• Tight project schedule of ten months and thus limited optimisation options for existing processes and interfaces
• Code adaptation and S/4 readiness checks including the necessary pre- and post-conversion activities
• Ensuring the existing functionality of interfaces to SAP (non-S/4) and third-party systems
• Ongoing functioning of existing MES systems and customer add-ons under S/4
• Simultaneous introduction of SAP GTS

UI5 app masking

Development and introduction of a UI5 app to selectively display exception messages in the MRP run in a matter of seconds. The result: an 80% time reduction through the use of CDS view technology, as well as a reduction in administrative work and storage costs.

Production versions

Timely creation and execution of production versions before the conversion, reduction of administrative work through regular testing of the migration report.

MRP areas

Creation of a new process under S/4 and execution of MRP areas immediately before the conversion. Training of employees in subcontracting and warehouse disposition.

Variant configuration

During the conversion, an error occurred in the configuration characteristics; the variant configuration in the customer order and the production orders were not resolved. In close cooperation with SAP, missing coding was replaced, the error was corrected and the conversion was carried out promptly.

• Preparatory measures should be tackled early on and numerous sandbox tests should be carried out.
• Sufficient time and effort should be planned for the initial conversion.
• Risk management with a clear risk and fallback plan for the go-live and cutover is recommended.
• Testing as often as possible, ideally on a productive copy, enables important routine in the conversion.