Growing IT organically: how Ecotone migrated its BI environment to SAP BW/4HANA


Earlier this year, Ecotone finalised its journey towards SAP BW/4HANA with the help of Expertum. In this blog, Expertum BW expert Erik Delpeut reflects on this joint project and highlights the considerations, lessons learned and the outcomes of the migration.

Let’s introduce Ecotone first: the company is a leader of organic and sustainable food in Europe. Their production facilities are located all over the continent, and they cover a large range of products such as tea, coffee, dairy alternatives, meals and snacks. Some brands might be familiar to you, either from your local supermarket or from grocery shopping abroad; think of Bjorg, Clipper, Abbot Kinney’s or Zonnatura.

Considering the way forward

Moving on to Ecotone’s BI landscape which originated from 2008, you can see an overview of it in the image below. Over the years, an SQL-layer was built on top of their SAP BW system, providing dashboard-like reports in Excel. Apart from that, about seven-hundred BEx Analyzer reports for more detailed analytical reporting were built directly on top of BW.


The SQL-layer became a thorn in the side of Ecotone; redundancy of data, bad tooling for data load-monitoring and dependency on DAX programming expertise were unwanted outcomes of the current situation. As more and more non-SAP systems (both data providing-and- consuming in nature) entered the BI-landscape, the need for more advanced connectivity and virtualization options arose. Additionally, increasingly complex reporting needs started to cause sophisticated data-preparation scenarios and front-end calculations. This development put big pressure on the data loading processes and reporting performance. All in all, good arguments for a renewal of both front-end and back-end systems.It was clear from the beginning that a complete replacement of the BW system, which was built over many years, was not an option: from a functional point of view the reporting was too valuable and the knowledge of the internal BI-team too vast. The choice for the combination of SAP BW/4HANA (BW/4) with SAP Analytics Cloud (SAC) as well as SAP Analysis for Office (AfO) seemed logical; the HANA-engine of BW/4 and the AMDP procedures would tackle the existing performance issues. Moreover, both SAC and AFO, working seamlessly with the backend system (via live connection), would provide a modern visualization experience.


In a nutshell, the BW/4HANA In-Place conversion path was as follows:

  • Get rid of redundant reports and convert all remaining reports to either SAC or AFO (BW/4HANA does not talk with BEx!)
  • Migrate from BW 7.4 to BW 7.5 powered by the HANA database (which is a prerequisite for an In-Place migration.)
  • Make all existing custom coding BW/4-compatible.
  • Execute the scope transfer (in some cases even a conversion of 3.x objects to 7.x was required). With Ecotone, we started with S-API to ODP and subsequently, top-down: MPRO and InfoSets to HCPR, Cube to ADSO and ODS to ADSO.

What did we learn and how could we improve?

Looking back at the journey, there are quite some lessons that we learned. Perhaps chief among them is that the migration path took longer to complete than we initially expected. The main reason for this was that the daily course of business also had to take place, in spite of all the project activities that were going on. A period of, let’s say two months, in which no new developments would take place and in which the team could focus on the migration job would have my preference. A project like this always hurts a bit, so it’s better to make it as short as possible.The next lesson learned would be to let the Tasklists do their job: Tasklist RS_COMPATIBILITY_TO_B4H for example, deletes a lot of incompatible objects we didn’t have to do manually. Also, you will run into issues when converting objects and you will (in most cases) need to perform these activities in a complete DTAP-street, so extensive documentation is very useful. For us, having all data sources migrated to ODP cleared the road to a smooth SAP S/4HANA migration as well, so this is something you might want to keep in mind if you find yourself or your customer in a similar situation.Another point that really demands attention is the MM Inventory Management model. It can easily be impacted by your implementation project. We decided to rebuild the complete flow according to standard best practices in advance of the migration; It’s working like a charm now.Finally; even before officially starting a migration project, you can already think about basic topics such as the cleaning of the system or alternatives for your APD’s. Considering the conversion of 3.x objects, such as 3.x-DataSources, InfoSources and Update Rules, is also an easy win if done in advance. Start thinking about the conversion to new BW/4-objects as well, or maybe even start building already if possible.So, how does Ecotone perceive their new BI-landscape after six months of operational use? Post-migration performance is stellar, and the customer could not be happier with the result. In the end, that is the final and only goal.

We're here to listen.
Get in touch with us.

About the author

Photo of Erik Delpeut
Erik Delpeut

Erik Delpeut is a Senior Sap Business Intelligence Consultant at Expertum.

Read more articles by Erik Delpeut

Related articles