Rahul Bhardwaj shares on cloud mindset, clean core, and winning with SAP S/4HANA Cloud Public Edition In this episode of Inside SAP S/4HANA Cloud, host Yannick Peterschmitt welcomes Rahul Bhardwaj from dsm-firmenich to share his remarkable ERP transformation journey. From unexpected surprises during onboarding to leading a pioneering Public Cloud implementation, Rahul discusses the importance of asking “why,” embracing a cloud mindset, and navigating change management. Discover how his team turned a business challenge into an award-winning innovation - and why pickleball perfectly describes his SAP journey. Show Notes: Download the episode transcript Learn more about dsm-firmenich: https://www.dsm-firmenich.com/en/home.html Check our enablement assets for SAP S/4HANA Cloud: https://chart-bdmaicr0au.dispatcher.eu2.hana.ondemand.com/index.html?hc_reset Visit the SAP S/4HANA Cloud Public Edition Community: SAP S/4HANA Cloud Public Edition | SAP Community Learn more about SAP S/4HANA Cloud Public Edition: SAP S/4HANA Cloud Public Edition
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 Foreigner Cloud. There is no customer success without product success and project success. I'm Yaoh Stanik Pederschmidt, and today we're diving into a fascinating journey of ERP excellence with our customer, DSM Fermanich. Joining us today is Rahul Badraj, who's had the pleasure to meet recently in Paris during the customer success. Day. Raul presented his personal Claudia AP journey and his companies and I thought, man, this is a great one for podcast. And here we go.
Welcome Rahul. Thanks for accepting invitation. It's a pleasure to meet again and listen again to your unique story and create a fantastic podcast out of it. Thanks Annek for inviting me. It was It is a pleasure to join the prestigious SAP podcast. Looking forward to a nice podcast with and. So am I, thanks for being with us. Thanks for your time. So let's kick it off and share with the ecosystem the personal story and the company story. Let's start with you, Raul, obviously. Can you tell us a little bit about yourself, your journey with ACP until now?
My name Rahul Bhardwaj, I am basically from India. So I started my journey of SAP from India, travelled a lot around the world, started my implementations in materials management module and then quickly moved to warehouse management and extended warehouse management. And also I did those implementation in various countries. So I moved around a lot. I stayed in Dubai, I stayed a couple of years in Germany and then Belgium. And then now I'm finally settled in Netherlands, which is a nice country to settled in.
And every year I try to do something different. So that's why I tried to shift my focus, what I've learnt and what I can learn in every project. That's why I was able to navigate through various modules in my career throughout my career like materials management, warehouse management, logistics, supply chain, extended warehouse management and also in the recent six years worked in private S4 cloud. And in my current company, I'm working in the public cloud
domain. So it has been an exciting and refreshing journey till now. Interesting. So you've travelled a lot in the world. And by the way, I hope that in your country today it's a bit cooler than in Germany, in the Netherlands, a traveller around the world and a traveller around a different line of business in the ERP as well, which I think is very interesting. So how is that journey? How does it feel like navigating different modules in different projects in SAP? That's a good question. So basically when anyone is
working in an SAP consulting world or solutioning world, the base of your knowledge should be very clear that why are you doing this? Why? Why a company is moving to end transformation? What do they want to achieve? And also in my beginning of my career, I started to ask question of why pretty often to myself that why SAP has built this product in this way. What would be the thinking behind it? And that makes it very easy for me to navigate because if I know
why, then I can connect the dots very easily and connect the dot for the business as well. So 2 important things here. I made sure that my base knowledge is clear of the business process of why the business wants to transform their ERP system. And the second why was why SAP has built the product in that way. So both wise help me to connect the dots. So that's that's one of the important things and. I agree, this is absolutely key. If you don't know the why of a
digital transformation, it will be a technical migration in the end, yes, And the customer will be pointed. Let's let's be honest here. So why did you accept this challenging new role in the organization at the SM Fermini? What is that role exactly? My role in my current organization is a product manager role which is not just related to a particular module. So a product manager should have insights on all the various changes which are going through a product. A product can be ECC, EWM As for any product, the end game is to benefit the business via
bringing transformation to this product. So our focus is not only on the product but also on the business. It's more of an end to end role where even if you are not from finance, you should be able to understand why there is a change needed in the financing module in order to effect maybe the revenue of the business. There is a chain of, you know, connections between the change in the system and the business benefit. So you need to understand that chain throughout. So that's basically my role. Thanks, Rahul.
Now from your role to the project, you have the honor to lead ADSN Fear Manage and you recently presented in the Customer Success Day that was super well organized by Elena Chabanu and her team in ACP location in Paris. So for those who are not familiar, what is the significance of the Customer Success Day and why did Elena and her team ask you to highlight ESM Firmani? Can you tell us a bit about the journey? What makes your story unique? Obviously. Our story is a pretty unique story is because our 90% of the
business in DSM Firminage is right now in ECC, there are only three business unit who went ahead and took the first step in the journey of S4 Public Cloud. So it was our initial steps. And with these initial steps, you learn a lot and not just for that business unit, but for the entire organization. So I was handling 3 business unit, but then I thought I would concentrate more on one business unit, which is I health based in the US as a product manager to maybe bring value to the
business. It's a very unique story because in our organization nobody actually knew about S4 Public Cloud and it's really hard to find people also to manage that. So everybody was in a learning phase and everybody is learning together. We are moving forward, but we are also learning. We learnt how to manage the upgrades together, which is mandatory in public cloud. We learnt how to navigate the system because in public cloud you already know that we are very limited in terms of
customization or in development. So how to navigate complex business requirement in order to fulfill that. It is a quite interesting journey. In the funny side of it, before joining DSM firm in IT, I was working for S4 Private Cloud in a company as a product owner for EWM and I had nice interviews with the company about how I understood S4. Since I told you the back story that everybody else was in ECC and these were the only business
unit in S4 public Cloud. People like to shorten the abbreviation. So everybody used to say S4 not S4 Public Cloud. So in the interviews, everybody just mentioned S4. So I was pretty confident that yes, I have done S4 for the last five years. I can easily manage it. And there were like 3 rounds of interviews and then finally I joined the company and then one day after joining, I was waiting for my SAPGY to be installed, but I got an e-mail saying this is your credentials.
Just click on the link and you are logged in. So I was a bit surprised that the credentials because I have not seen this type of credentials given before. Usually it's an installation in your system and then you get the credentials or reset your credentials. That's usually the way. So I just clicked on the link and I said OK, what do I do now? That's it. You are in your S4. So that was the first time I saw S for public cloud. And I I remember very clearly because usually when you are in the first day of a company, you
are in the office and then you can talk to people about how why this is. But it was a remote joining. So I had the laptop delivered to my home and I was alone so I could not even talk to anybody. When I received this message, I was like, OK, this is something new. And that was the first time I googled what is public cloud. So and I was very surprised that three rounds of interviews, everybody failed to mention that the S4 we are talking about is
public, not private. So that was my first experience of public cloud. But if you think that that was my first day that I was witnessing and I was really nervous and because everything rushes to your mind, you know when you start to question yourself, did you make a right move? But then I stood back to my basics that I discussed in the beginning that I know the base of the system of SAP, of different modules. Let me see if SAP has changed those basics or not.
So once I get into the system, I saw that OK, the base remains the same, it's just that they have improved on it. That made me a bit more calmer and then I started to explore more and more how to do it. What is the restriction again? Why? I searched for why SAP brought this product in the market? What was the need for it? Because S4 private was working fine, ECC was working fine. What was the need to bring this public cloud in the market? So I researched a lot on Wise and then I understood OK, this
is the reason why SAP brings it. And then I thought why our company chose for it. So I went back to my basics again like 1530 years ago and then that's where the journey started. It has been an interesting journey. Everyday it's something new, something exciting. And this story I've never heard, honestly, it's amazing because look, when you are in a recruiting situation, there's always a bit of, let's be honest, overselling on both side. But this one is very, it's a very unique story and it looks
more like a misunderstanding than doing some of the selling in a recruiting process. I like a lot that you said learn together. I mean, this is obviously why we do those podcasts too, to be able to share the learnings that you have with the SM Femenish with the rest of the ecosystem. Now to the why, you know, I was tempted to say wouldn't have been easier to go from ECC to private cloud for not only you but the organization, because in the end you would kind of stay in the comfort zone. Yeah, different UI theories,
different structure, of course, new code line, etcetera. So it's still a revolution, but not a revolution as big as going from ECC to public cloud, let's be honest here. So what is your point of view of that? What is the why for choosing public cloud? Yeah. So I asked that question a lot after joining because of my personal and knowledge as well. So when you look at these three businesses in our organization, they are very unique. Let's talk about ihealth, which
I'm currently leading. The ihealth is basically a contract manufacturing distribution center. They don't produce anything and there is no production site. Everything they have a process defined that we have contract manufacturers, we get customer orders, we do contract manufacturing for those orders and then we deliver it to the business. So the overall process is pretty much standard in order to think, OK, we have a standard process, can we align it with a standard system?
So that was the first thought in their mind that yes, it's not too complex, let's go for a product in the market which is also standard in our way and we don't have any complex scenarios. So let's look for a standard system. Second was cost efficiency. With the experience of ECC, they knew that over the years they customized a lot in the system through various developments, through various programs, which if you do an audit for like
after 10 years is hardly even used or hardly even I would say beneficial to the end goal of the business. At the end, if you do an analysis after 10 years, how much cost has been put in to build those customized programs and the cost of maintaining those customized programs, it was too high. So in order to avoid those costs and do the same mistake again, that was the second reason that they went for public cloud. And the third reason which is
also very important was that in our landscape we connect with a lot of third party systems. So we needed a product which has seamless integration with third party systems. You don't need to do much in your core S4 product, but you can seamlessly integrate with other third party products like with standard API. So there was a study done how much AP is are launched in public cloud and they were like enough to go ahead to build those connections between the
third party system. So that was the third and the most important reason for public cloud. OK, interesting. So standardization of. Processes. Yep. Cost control or cost reduction and seamless integrations? Yep. Let's take a bit deeper now. Rahul, I'd like you to please walk us through. You know the key. Phases. Of the ERP transformation journey of DSM fear manage from the Oracle system to mature SAPS for public cloud environment.
And maybe we want to highlight what are the biggest challenges during the migration and how did you with the team overcome that? Yes, the biggest challenge I would say, and I put this as number one challenge, it's not about IT migration, it's not about business process migration, it's about cloud mindset migration. Even today somehow some people also struggle to think about cloud mindset. And what does that even mean because cloud mindset can mean different from IT perspective and cloud mindset means
different from a business perspective. So to bring everybody on board to collaborate in a cloud mindset was the biggest challenge, which also in a way relates to change management. Usually in the previous ECC world it was a one way communication. Business has a requirement, they communicate to it, it delivers the requirement. Business says OK, we go live in production. That was a very simple one directional conversation and then everybody is happy.
But when you move to cloud mindset, you sit together because there are very limited options. How you want to proceed in your business requirement. First, it needs to understand why there is a business requirement. What is the end goal of the business requirement? Can it be achieved in a way that we don't need to do any As for customization because to reach our business goal, there are multiple solutions to do that. It's not just a field in a transaction.
It can be a different transaction in altogether. It can be a report, it can be a third party system. So there are a lot of solutions which you have to think together with the business because you cannot do it independently to bring everybody on the same table. That was the biggest challenge of collaboration, everybody to think on the cloud mindset. And as you know, everybody don't like change. So it was not a good, I would say, impression of the system because we were all forced to do
this kind of way because of a system we chose. The initial impression from everybody from the business was not good. They were like problems with maybe communication between the IT and business, not able to make the IT understand why they need it and IT also shutting down critical business requirement because you cannot do it that in the system. So there was a lot of back and forth and that's why you need somebody to hold everybody in a room and make them talk to each other so that we can come up
with a solution. Yeah, we can all talk about problems all day long, but we start then talking about solutioning and not just problems. What could be the solution? Is it AB or C? So at the end of the workshop, I always used to have like 4 or five solutions planned, even though I know that one or two solutions might be shut down by the end. But you need to have those options on the table in order to business to realize, OK, we can do this in the other way as well. I recall when I entered the
project, there was a big problem of carton labels in the warehouse in ihealth. So Amazon, who is the biggest customer of ihealth, they had demanded that every carton needs to have its own label because while receiving those pallets, they have scanners built in the warehouse doors when the truck enters. So what happens is the scanners scans the carton labels automatically so that manually
they don't have to do it. If you don't have them then a person from Amazon warehouse has to do it manually and they charge you for the X number of work hours that they had to do especially for a customer. So that was a very demanding, you know problem that we had because we were having we were getting chargebacks and that is not good. So then the finance team came to the warehouse that hey, what's happening, we are delivering to the customer and we are getting one and a half million of chargebacks.
So why is that happening? So everybody had to be in the same room in order to discuss what could be the possible solution. And the the solution basically it was to have an on demand printing because if a carton is getting packed, I don't know at what time it will be packed. So whoever is packing needs it at that time. These two things, every carton needs to be have a different label or its own label and it has to be on demand printing.
So these two were really complex for us to understand how we can do this in a S4 public cloud. So I went back to to the tools of SAP which has been given to us S4 BTP side by side extension. So we thought that, OK, if you cannot do it in the core, let's try to do it something in the side by side. But that also didn't workout. So what we said, OK, maybe we combine, we do a percentage of the solutioning in South Four and a percentage in BTP and then
in the percentage in 3rd party. So that's where we came up with a solution where we built an app in South 4 Core which gets pulled in, in BTP and then it brings to a printer which prints the labels at the time of packing. So basically it was a combination of the these three systems that we were able to satisfy the customer and of course bring down the chargebacks. And later we thought, OK, we, we were so busy in solutioning of
this product that somebody looked at it and said, hey, this is a very innovative thing that you did. Why don't you submit it to SAP? We submitted it and got the innovation award in the solution. So that was our journey from escalations, everybody not being happy, everybody coming in together, thinking about the solution and then delivering that solution and winning the innovation award. So it was quite a journey for us. That's impressive, Raul, because you know, some customer think cloud mindset mean we just have
to work with the existing best practice that ACP is delivering, which is of course the ultimate. It's a division, but it's not a limitation you can go beyond. And I think it's amazing from getting charge back from Amazon, which hopefully no one liked. And I can imagine how that hurts with the number of parcels that you ship from a reaction on a charge back to a business challenge to a business solution that turns out to be one of the best innovation of the year. Congratulation, great job, great
job on the team. Thank you, what did you personally learn from the journey? As you know that I started my journey of public cloud in DSM firmament. Previously when I told you that I worked in a module, implemented it, I tried to learn more. I always thought what is the knowledge gap? What more I can do in addition to functional if what I what if I do a technical also not coding, but to understand the code and you know, debug everything. So I also learned technical
during my EWM implementation days. I was always trying to figure out what can I do. At one point of time I remember I was debugging SAP standard code for six hours. So that was a journey and that made me a bit of an expert in my field. When you become an expert in your field, there is certain expectations that you enter a room and of business requirement everybody looks at you for solutioning that.
OK Rahul, what do we do in this case? What do we do in that case? Because I had multi module experience and pretty soon after some couple of years you start to like it that you are one of the smartest people in the room. So you start to like it. Then the expectations are really high with the public cloud. I was no longer the smartest person in the room because it is also I'm learning with everybody. So I had to think with everyone. Even there were like small, small things that I learned from my business users as well as the project managers or the
consultants who were there in the team. Because instead of being the smartest person, I wanted to be more listener at this role rather than, you know, acting as a leader. So I started to listen more to people, how they would work with the system. I remember 1 of the time I didn't even know how to make the favourites in the public cloud that because I used to always type the app name. So one business user said hey Rahul, why don't you, you know, build your own screen in the home screen, you know, for your transactions.
I said oh that's a good idea, can you teach me immediately? It taught me to being humble again in my field because I was sometimes you get too carried away in being an expert and then you are brought back with a system which is completely changed. So that was one of the biggest change that I wanted to learn from everybody and not just it was not on me that I am the expert. It's a new way of working. As we already discussed the cloud mindset, it was a new way of working for me. So that also changes your role a bit of a solutioning expert to
being a collaborator with the business. So that was one of the new way of working that I learned that how do we collaborate with the business, How do we change, maybe create ceremonies of inputs and then present it back to the business and then come up with different type of solutioning. So that was something new that I learned. I learned about clean core principle, which is everybody's talking about and the interpretation or misconception. First, when I heard about clean
core principle, there were some people who told me that clean core means no development as you were saying, that we have to follow the standard process that we have in the system. But as I grew into this public cloud field, I got to know it's not about that. There is a misconception also about saying no to any business requirement because we are clean core. There is also a misconception saying that every development needs to be done side by side. That's also not true. So it also depends on business
to business how you want to deal with clean core. There is a standard rule book and a rule book says that clean core needs to have a clean core system, needs to be updated, needs to be future proof and it needs to be aligned with the business. So it's not a religion. You don't have to follow it. You know by the book. Each business can make their clean core strategy differently because every business needs to have a competitive advantage. If everyone starts to follow the standard S4 public cloud, where
is the competitive advantage that each business wants to have in the market? So there will be some kind of customization, but how you do that customization, either you do it side by side or you do with the third party system with integration or like I explained in my solutioning a part of it in S4, part of it in BTP and part of it in 3rd party. That's one of the learning things that I had and I continue to learn. And also when we talk about saying no to a business from the IT perspective, there are ways
to say no, we can do it. So quite funnily, I was having this conversation with another customer in Safari Madrid. We were having this conversation and we are walking towards the lunch counter that they had. There was this stewardess who was standing in front and we did not even look at the time and we were just walking towards it because we saw the food is there, let's grab something. And then the stewardess said no, it's closed. Then we looked into time, OK that we were a bit early and then we went back and I came
back again because I remember, OK, I have to ask what time it opens and then she said, OK, it opens at 12:15 or something like that. So what we were discussing is when we get these requirements from the business, there is two ways that we can answer no, it's not possible or it will get open at 12:15. In both ways the answer is no. But in the second scenario, you get the information why at the moment, why I cannot go further. That was kind of a very live
practical example that we saw. And quite funnily, it happened in Sapphire that we were discussing this with the customer that yeah, there are different ways to say no. If you say no, it's a system limitation or we say no, can we tackle it in a different way rather than S4? Yeah, True, True. Yeah. So that's one of the things I love. And we all know it's hard to say no, Rahul, but a lot of people forget that we say yes to things that are much more important when you say no to some things much more important for the
bigger project. Yes, thanks for that. Interesting. Clean core is not a religion. I like that one. It's a guiding principle, but of course, it needs to work best for the company, right? In the end, the ability, you know, to make the system the competitive advantage. We've heard that at different customers, but they do like the standard stuff on the standard. But where it really matters, what makes you unique or gives you the competitive edge, this is where you will put the brain power of the people of the IT guys and the business guy and eventually develop that side by side car or all the
extensibility options those. Thanks for sharing. I would like to ask about role changes for you again so quickly ECC role As for public cloud role, internal IT now larger roles and responsibilities. How? How did all that come together for you? So that's an interesting question because since S4 transformation was everything new for me, I did not even know that I was going through an SAP S4 transformation.
When I joined the company, it just hit me and then I just went along. So in 2025, I thought, OK, let me try something new like I did with public cloud and I searched online. I used to play badminton, table tennis, pool, football in my past. So I was looking for something very new and exciting to get me excited about the sports again. So I searched online. I saw this new sport coming up, pickleball, which was quite unique and how they play, how the rules are.
So I was lucky enough to find a club nearby my house in the Netherlands. And when I started it, it was like, you know, my first day in public cloud, it was everything's new, the rules are different. It's played in a badminton court, which I have played, but everything is different. So the bass is there, just like my previous experience, the court I am familiarized with, but the rules are different. There is some kind of different paddle, different ball. So it was kind of an exciting and I thought I'll try something new just like I did with public
cloud. It is a good analogy. It's a good analogy. Thanks for sharing that. So Raul, before we close, please fasten your seat belt because now it is time for the fast five. OK, five questions and I'm expecting on the very short and concise answers faster as you can. First questions, what's 1 mindset shift that helped you succeed in SAPS 1A cloud journey? Always ask why. That's more of the important part that when you are hitting the mindset change, always ask
why. What was the biggest surprise during your transformation project at DSM Fairmanish? The biggest surprise was how big is change management? In one word, only one. How would you describe the Clean Call Principle Essential? What personal habit or hobby has helped you stay balanced during this big transformation? Listening to music, trying new sports. If you could describe your recipe journey as a sport, which
one would it be? I would be a biased, I would say a pickle ball. No mercy Boku, thanks so much. You shared so many anecdotes that I could not even pick my preferred one. But this is exactly what make your journey, your personal journey and the company journey very unique. Big big thanks for your time. It's much appreciated and I'm sure that our audience will appreciate it too. Thank you so much Anik for having me. Thank you so much. Thank you for joining this episode. Stay tuned for more insights and don't forget to subscribe to
sap.com/podcasts. You can also send us your comments and suggestion for the next topics via Inside S4 at sap.com. And if you enjoyed today's episode as much as I did, please give us a five star on Spotify or Apple Podcast TuneIn next time and be inside SAP Espana Cloud. Bye everyone, Bye Rahul. Night.
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,...