Join the journey of Felina’s transition from SAP Business ByDesign to SAP S/4HANA Cloud Public Edition with the partner Snap. Hear firsthand experiences and lessons that ensure a smooth ERP transition. In this episode of Inside SAP S/4HANA Cloud, we revisit the journey of Felina‘s transition from SAP Business by Design to SAP S/4HANA Cloud Public Edition four months after go live. After the first steps featured in Episode 103, Yannick Peterschmitt reconnects with Dirk De Vos from Felina and Raphael Finck from Snap to discuss the current experiences, challenges, and lessons learned from this significant change. They delve into the importance of flexibility, partner selection, and internal resource allocation in ensuring a successful transition. Join us as we explore the ongoing impact and future steps for Felina in leveraging the full potential of SAP S/4HANA Cloud Public Edition. What topic would you like us to discuss next? Send an email to insides4@sap.com Show Notes: Download the transcript PDF Watch: Felina adopts SAP S/4HANA Cloud Public Edition for enhanced data and reporting Join the SAP S/4HANA Cloud Public Edition Community: https://pages.community.sap.com/topics/s4hana-cloud Learn more about SAP S/4HANA Cloud Public Edition: https://www.sap.com/products/erp/s4hana.html
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
Welcome to the podcast Inside SAPS for HANA Cloud. There is no customer success without product success and project success. A transition to a new software has so many facets. It touches on the IT landscape, business processes and most importantly the users of the system. In episode 103 recently, we discussed the initial stages of our customers Felinas transition from SAP Business by Design to SAP Eswana Cloud Public Edition.
If you missed that episode, I invite you to listen to it. Today, around four months post go live. We are reconnecting with the same customer, Felina and their partners Snap to delve deeper into the current experiences and inside gains from that significant change. Let's explore today how the transition has unfolded and what lessons have been learned along the way by both the customer Felina and the partners Snap. So welcome or welcome back, Deck DeVos from Felina and Rafael Pink, the partner Snap.
Good to have you back. Hello Yannick, good to be back. Hi, Yannick. Thanks for being with us today. And let's start with looking back over the implementation. I know it took actually more time than planned. Is this something you would have done differently to keep the project timelines? Maybe you want to start with that one that Rafael you can comment? So if we talk specifically about the the timing, the planning and the timeline, yes, if we would have known upfront exactly, then
we would have allowed ourselves a little bit more time. At the same time, when you enter, when you embark on a project like this, you have to keep some room for flexibility. I think it's impossible to really detail out everything in the plan from A-Z with the correct timeline to some degree of flexibility. Some degree of relaxation during such a project is needed. I call it flexible focus. Yeah, you keep your eye on the ball, you keep your eye on the
end target and you have to allow yourself to be flexible in certain areas to be able to come to a good end result. Yeah. And I think we shouldn't forget the context of the Fena project where they went to a first implementation of by design and just after the goal arrives, they realized they need another solution. They had to change partner to re engage the key user. That means we knew from the beginning that yes, we had a very good project plan, but we knew we will have to accommodate
that. Not so much to be ready from a technical point of view, but to make sure that the key users are ready. Because second goal live 18 months after the first one is a lot of workload and stress for the key user. Maybe in addition, what I would say is at some point, I think it was in January, we needed to decide whether we were going to go live or not. We had to take that go no go decision and we decided not to go live at that moment, but to allow ourselves a little bit more time to have a more successful launch.
I do not regret for one second making that decision. I think if we would have really stuck to the original planning and seen that as a fetish to go live at the moment that we said we were going to go live, we would have had a much more difficult launch and a much more difficult integration of the project and the rest of the business. So I'm absolutely very positive and still in favour of making that decision to allow ourselves a little bit more time. I like to love this idea and the wording you've chosen, the
flexible focus. I think you're the first time bringing that on the podcast today, a couple of weeks, a month after, Go live. How is life for you, the customer and from the partner perspective? I think the Go live were extremely smooth, much smoother than we would even have expected from the partner side. The integration work well from day one. We ramp up the activation of the 2000 EDI customer in few days or weeks, which was a complete opposite. That was the customer experience and the oath of Go lives that
took place few months before. Of course we had an hyper care situation for a couple of months. We watch very closely the 1st monthly closures. No, we are on five months after Goliath and the customer is contacting us on very rare occasion for additional support. I would agree with Rafael on this one. The go live and the hyper care, which was not a couple of months but a couple of weeks, six weeks to be exact, went very smooth.
I think everybody was very well prepared. It went better than anybody expected to the point where there was some disbelief in the project team and we were kind of bracing for something that was going to come and that we hadn't noticed yet. But it didn't come. So it went very well and I think everybody involved in the project is extremely happy with how it went. There is one area where we now see that there could have been better preparation and in our case that is in the finance area. Oddly enough, the finance area
was the first to say that they were ready well before the go live. But in fact, once we had the go live, they were struggling and the first month closure took an extra month for them to be able to finish it. We have not really done the postpartum or post launch analysis specifically on the finance area to understand why that happened. But it seems that a little bit of overconfidence has creeped in there and it kind of relaxed a bit after they thought that they were ready.
But overall, I would say it was a very successful launch. OK, thanks. Glad to hear that. Obviously. And you did all that with the team because you have a business to run, you have a business transformation for which you need new platform. So I'd like to understand from you what were some of the immediate business impact you notice post transition, you know, on the day-to-day operations, especially looking at business performance. Have you observed measurable improvements or benefits can be really directly attributed to the new platform to the fact that you are now running on SAPS
400 cloud Public edition? Yes, the area where the problem was the biggest, where the pain was the biggest with the old system that was inadequate with our customer service department because that is where everything comes together. You need to be able to give a quick and correct answer to any customer requirement or request coming in, whether it's new orders, whether it's order situation, whether it's questions from customers on when their delivery will arrive, etcetera, etcetera. Do you really need to be able to
look up the correct information in any area of the business? And the stress in the customer service department prior to the launch, even prior to starting the project was extremely high. Workload was extremely high. And then of course they went through a very hard time during the project because on top of that workload, they also had to run the S4 project. But now after the go live, we have seen an immediate relaxation within that team. The workload has come down
significantly to the point where we now have one person of the team who is on parental leave for a year who did not have the need to replace that person. The rest of the team can now relatively easily, and I have to be careful with my words because they might listen relatively easily. They can handle the workload that is there. Now they really have the feeling that the information is at their fingertips. That is really remarkable improvement that we are noticing and that is only possible because all the other departments are now capable of
providing the correct information via the system, which was also hard to do before. Logging the correct information, adjusting it where needed, updating it where needed was a real burden before. And now it's just a part of the day-to-day work and it happens very smoothly, including the exchange of information with our factory in Hungary and also the exchange of information with our external partners like our logistical partners and with our customers through electronic data exchange, EDI.
All of that is working much smoother than before. OK, that's interesting. And did you really get feedback from the users in the customer service department? You talk about this relaxation, so can you quote a few colleagues? What did they say to you? Yes, definitely. I think the most remarkable quotes we got was from one of our colleagues who's been critical throughout the entire process. She adeared extremely to the old platform that we had in in which she had been working for 13 years. And the biggest compliment that I heard was I've been really
trying to find something wrong, but I couldn't find any. That's a beautiful quote. Yeah. OK, good. But let's look at the other side of the cone. There are always some challenges and migration from ERPA to ERPB, It's a change. Management should bring a lot of people with you. Most people, including me, don't like to go from a new software because it was so nice in the past. We all know that, right? So what were the challenges that you faced at Helena? Unexpected hurdles that arise and throw the goal out. And how did you address them?
It's exactly what you said. The difficulty is all the things that we know from traditional change management. If people need to change their habits, it's a hard thing to do, and people tend to focus on what they lose and not on what they gain. It helped, of course, that the pain in the old system was really high. The pain level was high and it was relatively easy once we launched S4. The difference with what they had experienced before that was very important, not to say
immense. So that helped tremendously in the adoption of S4 by the users. But that was of course after the go live. While we needed to prepare before the Go live, all we could do was remind people of all the difficulties that they were going through with the old system, how this would be solved in the new system. And that took a bit of a leap of faith. It wasn't always there. The faith was not always there. But the best remedy or what you need to do in those
circumstances is communication. We had very regular, all staff meetings where we discussed the progress, where we celebrated little milestones when we could say, OK, now we've tested this and it was successful. And these are the benefits that you will live through once we go live. So layer by layer, we've been building up the confidence in the new system by demonstrating in the test system how things were going to work. And of course, you cannot
demonstrate everything in the test system, even only because the test system is not loaded with all the information and all the data that we're going to use in the actual production environment. But for me, the keyword is communication. One of the lessons learned is that having one person responsible who is not necessarily active in the project, but who is responsible for the constant communication between the project and the rest of the organization is crucial. Back in the days when we were in
the BYD adoption, we did not have that role. Now in the S4 adoption, we installed that role. We had one person from the marketing department who got the responsibility of keeping the communication between the project and the rest of the organization flowing, and that was a real asset. And that went through a monthly newsletter, through ad hoc communications to announce small successes or difficulties. And like I said, once a month we had what we call the town hall meeting with all the staff where
we gave an update not only on the S4 project but also on the S4 project. OK. That's interesting. With the person responsible, I'd like to dig just quickly into that. Is it someone coming more from the IT or from the business side? From the business side, OK, actually from the organization side. So in our case, we asked somebody from marketing who is also responsible for external PR. So somebody who is used to setting up good communication, who is used to making positive stories, so to speak.
We had our own PR manager for the project. OK, which seems to be a critical key success factor in the project. Yes. Good. Let's have a look now at some pathet of the IT landscape. Of course, these SAPS for an A Cloud public edition system is part of a larger landscape where end to end process has to run. Can you discuss how well the integration was achieved? What were the challenges and recommendations to your peers when it comes to the larger
infrastructure and the systems that are connected and have to work daily with SAPS for an A cloud public edition might be interesting in your point of view. Rafael as well, of course, the system integrator. One big difference is that we included in the project BTP and subcloud platform integration in the landscape and that's allowed us to manage all the interface and not with point to point interface like it was implemented in. By design, it had even such a good effect that suddenly the customer realized that they can also ask ATP check more easily
than the past to the points. And during one month, we had more than 13 million call during a single month, OK, which is more or less five call per second just to request an ATP check, which was a big surprise for us and of course had some impact. But the positive things here is that the system is even able to under such big workload and we were able to monitor where all these calls are coming in the system and so on and after to optimize a little bit the solution to reduce the volume. But going with CPI was a key
factor we were able to integrate, but first to make the data migration using I flows and using CPI we were able to connect more efficiently the manufacturing facility which is still running by design. And there is some information we couldn't get through standard interface from by design to by design. Putting CPI in the middle simplifies that and we connected the B to B platform where customer can put order directly in the system and I think putting the middle way in place was a game changer for failing
out. OK. Thanks, Rafael. Dick, do you want to comment into out here? Yes. Although I'm not a technical person so I can't give much of A technical explanation, but I know enough now of these SCPIS. And that was an advice that Snap gave us and really insisted on putting those in place. And that has really been a game changer for us because now all of a sudden the communication between us and our external parties went smooth, whereas before it had been a constant burden and a constant cause for
technical difficulties. Which also underlines that one of the key SuccessFactors of a project like this is your partner choice, the integrating partner that you want to work with. It is extremely important to make a good choice there and to make sure that you have somebody that not only understands the technical side, but also understands your business and your setup and the goals that you want to achieve. Because I've used the word flexible focus for Felina before, but that is also required from your partner. They may come in with a certain
vision, but then as they learn more about your business, as they learn how you operate, they also have to have some degree of flexibility to make sure that they can provide the solution that is actually going to work in your day-to-day life and every day-to-day requirements of the business. Good. Thank you, Derek for that. We're approaching the end of the podcast already, but I'd like for both of you have a little reflection on the advices you would like to give other companies who considering a similar transition from SP by Design to SCPS SWANA Cloud
Public Edition, because this is a very particular context. Maybe you want to stop Dick. Yes, I think there are four points that I would like to touch on. One, the pre work, the preparation before you actually enter the project phase is extremely important. So really understanding what are the problems that you are facing today with DYD, which are the points that you would like to see improved and making sure that S4 will actually solve
those issues. As I said in a previous podcast, we did our homework. We did not assume from day one that we would transition from BYD to S4. We really started with a blank slate. But based on our needs and based on the issues that we faced with BYD, it was clear for us that S4 would be the best solution and that's why we decided to go with S42. What I just touched on the selection, the choice of your partner is a key success factor to your project.
I've been through both sides of that coin. I've worked with a partner that was not adequate for our business and I've worked with one who was very adequate and we were extremely happy with the work and still are extremely happy with the work that Snap has been doing for us. 3, making sure that you give enough resources to your projects internally. It's very tempting to go with the minimum set up because of course there's also the rest of the business that needs to continue and you want to have as
little disruption of the business as possible during the project. It is a painful time when people have to wear 2 caps when they have to work in the business and also do the project work. It demands a lot of the people. But this is one of the areas where you can be Pennywise and # foolish. Trying to save resources on the project ultimately will bite you back at the end of the project. Either the solution will not be satisfying or you will not be able to reach the deadlines, resulting both in a longer, more
painful and more costly go life operation. And last. I've used the word twice now already. But the flexible focus is really important. Also, there is a plan when you start. But like Norman Schwarzkopf used to say, the plan is nothing. Planning is everything. So you have to be prepared during the project to review your plan, maybe even review some of the requirements or some of the outcome if it's clear that not changing or not adapting will give you a sub optimal solution in the end.
Sometimes that is hard, either for the organization or for the partner. Nobody likes it when things change when you are in flight, but both parties have to keep that flexibility and accept that this may happen during a project. So those would be my four critical SuccessFactors. Thank you, Dyac. Rafael, what are your key SuccessFactors? What would like to reflect on the journey? Yuck mentioned most of them, but I think what was very critical is that we took the time to understand the female business
challenge and technical challenge and to find a solution together as a partner. And from the beginning we were partner. We didn't guide anything. When we had a challenge, we put them on the table. And that was a very good environment. And maybe what I can also say, and I know it's not necessarily typical in the public cloud business, but we already had a team dedicated for the lengths of the project to failing out. They didn't focus on anything else. And that allowed us to understand correctly the business and the previous challenges the customer face in order to provide the right solution.
OK. Thank you. That was a great compliment though finally. So looking ahead, what are the next step for the Felina organization and leveraging the full potential of SCPS 1A cloud public edition? So you're using a big bunch of the scope, but not to the entirety. So can you dear comment a bit on the next step where the business will make more or run even more on the SAP application? Looking forward, I think there's two things that are still in the
pipeline. They're not defined precisely in terms of the timing of when we are going to do this. But one thing is that there are certain processes where we will look to further automate because some of the processes still require quite a bit of human intervention and we believe there are possibilities to relying more on the system than we have done before. There has been traditionally a tendency to control the system and keeping the possibility of
intervening in the processes. Now that the trust in the system has grown, we will take another step and let the system do more than what we have done traditionally. So that's one area. The second area is the reporting. There is a lot of standard reporting available in S4 and we are still learning a lot in that area. But there are some specific tailor made reports that we want to build and that is something that probably early next year, so early 2025 we will be
focusing on to develop more specific reporting. And then in the far future we will probably do more in the area of customer relationship management. So the CRM is something that we will also be looking at to develop that further. Thanks a lot. I think these are very good closing words alike, especially the trustee of the system and rely more on the system versus try to control the system. Thanks a lot, dear, for spending this couple of minutes with us. Thanks to you as well, Rafael.
It's been a pleasure for me to reconnect with both of you and thanks to you audience for joining this episode. If you like it as much as I did, even have ideas about the next relevant topic for this podcast, please just drop us a note at insides4@sap.com. TuneIn next time and always be inside SAP S4. Anna Cloud. Thanks again, Derek and Raphael and hope to hear from you soon. Bye. Bye. Thanks guys.
Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets into one of the most significant partnerships in the SAP ecosystem right now. Host Yannick speaks with Vladimir Shakhov, Strategic...
Recorded live at SAP TechEd 2026 in Berlin, this episode takes a refreshingly grounded, practitioner-first look at what AI in SAP really means in the field today. Host Fernanda speaks with Wouter Lemaire, independent...
Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP brings something the series hasn't had yet: the perspective of an actual large enterprise customer architect, not a consultant or partner....
Recorded live at SAP TechEd, this episode of Inside SAP Cloud ERP zooms in on the dimension of SAP transformations that gets the least attention - and causes the most damage when ignored: Organizational Change...
Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets to the heart of what the autonomous enterprise actually looks like when it's working. Host Yannick speaks with Sindhu Gangadharan,...