Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Inside SAP Cloud ERP

Inside SAP Cloud ERP artwork

Episode 103: SAP Customer Transitioning Experience: SAP Business ByDesign to SAP S/4HANA Cloud Public Edition

Mar 6, 202433 minAudio
ShareXLinkedInFacebookWhatsAppEmail

We are now the podcast Inside SAP S/4HANA Cloud! It is a small change in our name and branding, but we keep the same focus and strategy: sharing project best practices, lessons learned, and successful go-lives with SAP S/4HANA Cloud. We continue to share perspectives from customers, partners, and colleagues. Show Notes: Watch this episode in video format on YouTube: https://www.youtube.com/watch?v=yqz1UkYnUY4 Check now the collection of enablement assets for SAP S/4HANA Cloud Public Edition: Enablement for SAP S/4HANA Cloud Public Edition | SAP Community Visit the SAP S/4HANA Cloud Public Edition Community: https://pages.community.sap.com/topics/s4hana-cloud Hear more from the host Yannick Peterschmitt: https://www.linkedin.com/in/yannickpeterschmitt/ Download the transcript as pdf file Tip: Read the transcription of this episode in different languages using the SAP Machine Translation Portal or your favorite tool: https://mtportal.int.sap/

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 our podcast. There is no Customer success without Product Success and Project Success. I'm Yanik Pederschmidt from Cloud ERP Product Success Enablement and I'm happy to announce that we're now the podcast inside SAPS Fohana Cloud. It's a small but important change on our name and branding to keep the same focus on the same strategy, sharing projects, best practices, lessons learned and certainly successful goal out with a CMP Esfahana Cloud. We continue to share.

Perspective from customers, partners and of course, colleagues too in today's. Episode we will put the. Spotlight on a very special topic that is relevant for many, many ACP customers, which is the transition of the ERP system SAP by design to SAPS Farhana Cloud public. Edition. Joining me today are Russell de Lamp, Executive VP at Navigator Business Solution, a customer and partner from the United States, Dirk DeVos, the MD of

Felina, our German based customer and Rafael Fink, the CEO of SNAP, SAP Implementation Partner of Felina. To kick things off, I'd ask I guess to introduce themselves. We start with you, Russell joining us remotely from the US. Yeah, rest of the lap I I run our services and support team here and Navigator we've been SAP partner for 15 years. We started with B1 and primarily have been working with by design for the last decade or so. And then recently, the last two

years we started our S4 practice and that journey has been a lot of fun. It's the fastest growing segment of our organization and like I said, happy to be here. Thanks for being with us. Let's move into the second customer, Dirk, from our customer, Felina. Can you go and say a few words about the customer, about yourself, of course. Well, so thanks for having me. Let's talk a little bit about Felina. Felina is a German company. Actually next year we will be celebrating our 140th anniversary. So we've been around since 1885. We are a manufacturer and

distributor of premium lingerie, premium of women's, women's lingerie. We are based not too far from here in, in Mannheim and we've been that throughout our entire history. And a couple of years ago, we came to the conclusion that our ERP system was no longer serving its purposes. And that is when we did a survey of the market and decided to go with SAP. Great. Thanks for being with us. And every good project and successful customers has a great

partner. So we have Rafael Fink with us, the CEO of Snap. Thanks for being with us. Welcome. So yes, before creating Snap eight years ago, I was myself on the customer side, implementing SAP product for almost 20 years. In fact, we created Snap with my wife here in Slovakia. It's a family business. We started the very small focusing on by design, exclusively and only SAP public cloud solution and two years ago we started the transaction transition to S4 public, of course with our first customer similar.

OK, thanks. Good. Let's not dig into the topic of the day. I'm very excited about your your answers and I'm first looking at you dear representing Felina. I think our audience is very curious to understand you know what really motivated you to move from one you know well running ERP system, cloud ERP system to SAPS 4 HANA Cloud public edition. Can you give a bit? You know the the why and what behind all that? So like I said, we at some points we made a choice to go with SAP and at the time we

chose to start with the BYD version of the cloud version of your ERP system. And even though Felina is AI would say an SME, it's a small medium enterprise. We are about 50 people, but it's a relatively complex business even for even for the size. You have to know that we run about 14,000 SKU, so 14,000 different products that we distribute globally to about 4000 customers.

And also our product offering because we are essentially a fashion business, you know it's with the summer and the winter season, our offer to our customers changes every six months to about 30%. And so there's a there's a lot of innovation, there's a lot of change in in in our business and relatively big complexity even if the numbers as such are not are not that that big you know or not that that that important. So even the for a small business we need a powerful ERP system.

The step from our old ERP system into BY you know helped us a lot in even understanding our own business because we hadn't done the real in depth analysis of our business and our processes because you know things had been running quite well for for 15 years until they didn't anymore. So moving into BYD gave us an opportunity to really analyse our business and to much better understand you know where the difficulties are. But it also had a as a consequence that relatively soon we found out that BYD was actually not powerful enough.

And you know, we wanted to make that step up into S4. The fact that we didn't use BYD for that long was a bit of inhibiting factor I would say to adopt A new system. But thanks to the Lighthouse project that was, you know, offered to us by SAP that enabled us to make that step from BYD into you know S4 clouds or SA PS4 cloud a lot faster. So that really, really helped us. And then the other thing is for that second transition from BY into S4, our partner Snap came on board.

We had some experience with them from work that we had done before in our production units in Hungary. And I can't underline enough how important a good partner is in implementing, you know, a new ERP system like this, because we've had both experiences, you know where it was a a more difficult trajectory I would say. And then we learned with with Snap that it can also be very smooth and swift. This is great to hear. So a few things you mentioned that are very interesting. I think first of all is about the business process

transformation and build the business processes on the cloud, ERP. The second thing you mentioned is you've reached the technical limit of a system that kind of forces you out to the next one, which is thankfully the next Gen. cloud ERP from ASAP. And you mentioned then the Lighthouse program and I think the two projects that you guys represent today were under the so-called Lighthouse program. Could you please shed some light a little bit? When we moved into BYD that that was not under Lighthouse, but then but then the transition from BYD to S4 went under the

the the Lighthouse program. And for us, I think also for SNAP having access to all the the expertise and the consultants of SAP itself and you know the the S4 cloud package still being relatively young and we encountered some issues and some problems that were First off and that probably would have taken us a very long time to develop or or find solutions on our own and having access to the, you know,

directly to the SAP people. That helped us tremendously. We have a weekly steering committee where somebody from SAP participates, you know, together with our partners and our internal project management, and that made all the difference. Let's not talk about the solution, but you both are using both customer and I'd like to maybe ask you or Rafael first as as Felina's partner, you were certainly involved in the decision you know to move from cloud ERPA to cloud ERPB, lots of functionality from the one

inside, lot of functionalities on the other hand side more powerful capabilities. But how did you at the end make the decision that this is the right cloud ERP for your customer, but the? First thing which was challenging is to go through the journey with a customer about how to identify that by design was not anymore the right solution because it was already a big investment made in in this tool. In fact, we did something that was forgotten in the previous implementation is to make the sizing exercise and that's what helped you. You mentioned and very quickly realised that this tool was not

able to support your growth and also the volume of data that was needed to be in the transaction on a daily basis. Then we went with SAP and Fenina and DIA was involved was a digital discovery analyse we we wanted. I wanted to convince the Fenina to stay in the Recip family. It was not so difficult because Fenina wanted to stay in the Recip family. We said look, that didn't work, what is the best tool for us? And we came to the conclusion list for public cloud. So Digital Discovery Analyse is really a tool that didn't exist before and that's really helped

a lot to convince the customer to give them, to help them to scope the project and to understand what they will get and what they will not get. Rafael said that we absolutely wanted to stay within the SAP family. That is not entirely true in the sense we had really an open approach to the market that we also considered other suppliers if you want. But in the end, after the DDA, we came to the conclusion that probably the best fit for our needs and coming out of BOID would have been SAP. OK, OK. That's. It's not like we blindly just went again into SAP.

We we really did our homework and came to the conclusion that SAP would be the best solution. For us. OK. So there it was not just the not the natural extension, but there was a real assessment where you could as a good. As a good housekeeper, we did our homework. I think that's the that's the job that has to be done. It seems not too hard for us, was not necessarily not for the customer. OK, good. Russell, now I'm looking at you and and you have a special role here because you both customers and partners which makes that even more interesting that's safe because you have the the the two perspective in the in

the same house. First of all the the same questions that we just asked here is how did you came to the conclusion that Acps for HANA Public Cloud is the right solution for yourself for NBS as a company? Yeah. It's an interesting question because we've been running by design for over 10 years. So it was just kind of time for an optimization and we wanted to explore our options and and look at either optimizing by design for the future of what we're looking for or transition over

to something like S4 Public Edition. And then we ended up moving over to to S4 for a variety of reasons. Number one, it's the fastest growing business segment at Navigator. So we wanted more expertise in house and there's a lot more depth and the financial services area for S4 than in by design. And ultimately it's just more resilient with additions of things like the BTP which allow us to innovate within the BTP and actually take that innovation and deploy it to our customers as well as other partners through the SAP store.

And other things like you know obviously working with SAP in the Lighthouse program was was a really neat opportunity for us to both kind of be that partner and customer. So we're we're really getting a lot of benefit both from our internal operations working with SAP, but as well as our implementation team being able to refine their tools and our methodology and then how we actually go to market with S4. The last big factor that ended up because it is an investment to do that transition versus optimization is a lot of the predictive elements within that are shipped kind of out-of-the-box. So a lot more innovation around

machine learning, artificial intelligence and again being able to leverage that with the BTPS. OK, thanks for this answer. Now I want to dig a bit more into the details of the, So let's call that the migration strategy because I mean you you said it already a lot of data, too many data, too many too much information and and and and I think you need to be very brave if you have from the ambition to move from one well running ERP system to the other because of the data. It's not only about the software

itself, but it's about the data and making sure that you keep the data that you need for the future, for future decision for example. So how did you, how did you approach that and maybe Russell, you want to enhance on that one? Yeah. Again, it's, it's kind of a funny story because Navigator, we're actually innovating in this cycle as well. That was one of our areas that we're investing in is this transition from by design to S4. But then when I started talking with some of the folks at SAP and begun our journey, actually implement implementing that.

SAP has provided what we call integration flows or I flows in the ETP where you can basically just extract data from by design, put it through this I flow and it kicks out a translated file for S4. So migrating most of our master data objects where it was very easy, the only things that we had to look at were basically the custom fields. So that dramatically increased our implementation time when you have that automatic transition translation of data. So it's it's literally just three steps. You download the data, you import it into the BTP and then

that kicks out a file that you then upload into the migration workbench for S4. So pretty pretty streamline process and then you just refine kind of the the, the custom data, the custom fields that you might have had in one same system versus the other? Rafael, would you like to add something on this point? So, needs you. You mentioned the Excel Lighters program, how important it was for you. But it was equally important for us because as you heard it from the ARC, it was not an easy project. It was not just, of course. It was a migration from by design to S4. And in this sense with the high flow that Russell just

mentioned, we were able to take the migration part away from Fenina key user workload. And that was mainly a work from consultant and technician and developer to migrate this date. And then we could focus with the customer on the best practice from SAP. And of course then it was another component that was important. It was one key functionality which is a pure retail functionality that was not available within S4 public that we were able to develop specifically for for the customer and that also made a difference. But with all the writers programs that means for the help

of the migration help us to understand the business process because we were both early adopter in this journey. Without the also the Technical Support we got for the specific development we made or the one specific add on we needed, we wouldn't be able to to achieve that. OK, OK. Good to know that you want to add something on this. This is one example of one of our concerns in moving into S4. Another one was also the size of our orders. The number of order lines that we have on a typical order is simply too much for BYD.

So that was one of the things that we wanted to be sure of that S4 would be able to cope with that because there was some scepticism with the users. We needed to develop a number of workarounds in BYD to be able to handle the size of the orders that was coming in from our customers and that put a lot of stress on customer service. So at the one time that created the scepticism from some of the users. On the other hand that was also like the carrots that we could hold in front of them because nobody was jumping up and down

to so quickly after a first implementation, we were going through a second one. But the carrot was that, you know, S4 would be able to solve a lot of the user interface and user issues that had arisen in BYD. So we took advantage of that to motivate people to go for it again. That's a good thing. We actually to my next question, we'd like to listen a bit about or learn more from the challenges that you guys have encountered, you know during the project, be it you know, functional challenges, technical challenges, extensibility

challenges. Russell, do you want to to start with this one? Some of the challenges with that migration is you know really just cloud is in our DNA Navigator. So we're we're very used to the cloud deployment method. We're very used to the Fit to standard workshop. But there is differences between by design and S4 fundamentally how they're designed. Whereas by design is more that suite in a box. So you get like a a mile wide in an inch deep type of functionality whereas S4 is much deeper in certain areas but not necessarily as wide. And so certain challenges with

the functionality that my team wanted weren't there. And so how we, how we really address that is we just took those fit to standard workshops, identified the gaps and really broke down those deviations to the best practices, escalated those to our steering committee and were able to make a decision on how to accomplish and resolve those issues. And again we ended up leveraging the the BTP for some integrations in a third party for for some more depth in the CRM area was one one example that we we needed to extend into do. You want to add something?

Yeah, in term of challenge, the first thing which is great with S for public is the way the tool is documented and to activate methodology and all the tools that we are available for the project. On the other side, there is so many tool that it was difficult at the beginning to digest all of that, but that's great. The other challenge is thing that project is complex because you have third party logistic, we have shops that means we are using also SAP customer checkout and we have an EDI partner and we have 2000 customers that are sending EDI message on a daily basis.

And we needed in the middle to put in the middle of sub cloud platform integration to orchestrate all of that and that was a a big challenge and to manage all the exception of all the customer of Fenina. And from the customer point of view, the the main challenges that you now remember after the process? The first thing is that that the SAPERP environment is a bit of a closed environment. You know, SAP uses their own vocabulary. There's there's a lot of very specific terminology a lot of very specific processes that are going on and we are not in the

ERP business. You know I'm I'm in the laundry business and so are my colleagues that's for us this is something else that comes on top of you know what is really our business and then what we are concerned about. So that took quite a bit of you know, getting used to and and if we go back to the early stages like the scoping exercise and then afterwards the the fit to standard, you really have to even before you know how the whole system works. You need to kind of get into it mentally and and understand the vocabulary and actually also find out three, four, sometimes

you know six months later that something that was meant in the fit to standards is not exactly how you understood it and now it comes back and you need to you know review that or or or make some some adaptations. So that was a big challenge. Like I said, the other challenge was, you know, to motivate the key users. Like I said, we're a small team. We're 50 people. There's only a handful of people that are capable of playing that role of key user. So they've been doing that now for three years in a row on top

of their normal jobs. So that was a big challenge. And how do you manage that? How do you manage the change management? What kind of decision do you take there? What initiatives do you take to keep people motivated? Also to make sure that the rest of the organization that is not so deeply involved stays aware of what is happening and doesn't see it as somebody else's problem. Now they need to understand that sooner or later they will also be working in this environment. So you need to constantly keep them abreast and keep them

informed of of what is happening. So those are some of the challenges that we had on top of managing the costs, managing the timing. Making sure that the quality of the output was what we needed and and what we expected. Thank you for that. Rafael, you mentioned the quality of documentation. I think you mentioned as well ACP Activate, which is the implementation methodology that you use for SAP as far on a public cloud. I'd like to understand from both projects how was this method, ACP Activate able to bring the

right structure, the right people, and ultimately make the entire project successful. Russell, would you like to start with this one? Yeah, I'd love to. So the Activate methodology is a really great tool. Like I said, kind of cloud is in our DNA already. That's all we've been doing is cloud deployments in the public environment. And so the Activate methodology is very similar to what we already do. However, it did give us a few more tools to use. I do agree the best practice explorers that come with S4 are a lot more robust and detailed and they're they're great to

kind of lay that best practice out and give you that foundation to work within. So one of the things that we use with the activate methodology is like I kind of mentioned before in the challenges was to do more of that documentation in that fit to standard workshop and that gave us our 80% fit. And then in the next phase before we moved on to larger testing, we just were able to focus on that 20% process engineering that we had due to fine tune the system. And then once we had that, we had that documentation that was provided for the baseline and we're able to create those SOP S

again in a very fast way. Another thing to point out is in SA PS Eyes Navigator is a small company. We're on the lower end of that mid market spectrum. And so we were able to scale the methodology down to a project team that was smaller than it was nationally intended to. So it adds to the foundation that it really is a good foundation and framework to work within for companies kind of all sizes for implementations on S4. What is your point of view here? Very similar. What is also great, which is coming on the top of the activate minology is SAP,

Claude, ALM and tools like the business configuration questionnaire. And that's come back to what you said here about the vocabulary might appear very complex, but at least we have a checklist to go through to make sure we don't forget something important, even if we don't necessarily go through everything with the customer. That's also the job of the consultant to simplify the absorption of the information. Of course we say night they were the first one, the next customer might not go through everything we we did with Fenya. We we will like also mentioned

simplify it from the for SME. Let's go to one of the biggest moments of of an European implementation, which is the go live. I don't know if you as a from a partner perspective you if this is day zero or this is already the day 360 because a year has been spent or or a couple of months has been spent there. But it's definitely the day where the entire operation of the company works on this new piece of software. And I'd like to understand especially from our partners here the experience of the go live, the support that you've gotten from SAP as your of your

software vendor. We can start with you. Then we are going to go live in few weeks with Felina, but I can comment on the on the support from SAP. That was the reason why the lighters was important for SNAP as well As for FENA. Because we needed access to the SAP consultant and we had access to a full team of functional specialist based in India and they delivered some very good answer on some specific questions. We also had access to workforce for specific development and of course BTP is a main place where we develop things, but we also

wanted to develop things inside S4 directly in steam punk and for this we needed guidance. With all the support of SAP, we will just still try to look where to build things. What we know is that the go live is an important milestone, but it's not an end. Once we have the go live, we need to support the customer at least until the 1st monthly closure and after there is all the phase two implementation that is. That's something that Felina understood very early, although eat an elephant one piece at a time and of course we have a full scope for the phase one and

we have a scope coming for the phase two when when the team will have the digest as a go live. Typical cloud implementation, right? Yeah, but I think it's also important to point out here that technically we probably could have gone live on January 1st. We chose not to. And you know, people should just know that our go live with BYD was pretty rough. So we learned some lessons there and even if we could have gone live on on let's say January 2nd, from a technical point of view, we prefer to add on another 90 days or three months of you know, additional testing, some further fine tuning and

especially give a key users and all the users the opportunity to get much more acquainted with the system. So that by the time that we really go live on which will be on April 2nd, people are actually familiar with the environment, familiar with the technicity, have done a lot of your dry runs and specifically for their area off the business. And then hopefully we'll have a seamless go live, at least a lot better than the last one. Let me maybe you should say a little bit more about that because yes, you mentioned your

key user three years on a project. The first part was with a by design project and you mentioned just after we went to another point and all difficult it was that means six weeks you were without being able to ship we. Had four weeks without any shipping at all and then we could gradually start to start to build it up. So that was not a good year for us. OK. I can imagine. Russell, back to the go live this big moment, How was that for your company, for the end users? How did that all go for you guys?

So I think it all comes in order to have a good go live like you just heard from the other teams is testing is so important. And so that's what we always really focus on and we have different quality gates and you know peer review and certain benchmarks that we assigned to the users and we use the activate methodology for that feedback and not just making sure you can get through the process but also looking at the results that come from that process. And so our our mantra here is you know go live is just another day because you've done so much testing, you have the repetition, you can do your job in the new system.

We have change management embedded into the methodology and so our goal is always to have go live just another day. So it's not this big stressful event. And the second thing is then and you kind of mentioned it earlier, do you consider that day one or day 365, we actually don't a navigator, we don't consider our customer and same with our as being a customer as well. We didn't consider ourselves live until the first month and close. And so after you've been using the system for a month and then you can actually look at the results, close your books, submit your statutory reports,

that's the day that we really say, OK, now this phase and this implementation is now complete and we move into that kind of hyper care and support phase or different phase twos that have been identified throughout the project. And so for us we did have two phases and so the first phase went pretty smooth. The biggest challenge that we had is this user bandwidth, they're very consumed on the finance side with closing out you know last month at the same time using the new system for this month. But other than that, from a a functional system perspective, the team was was very ready to cut over and and start using the system. Yeah, you've already started a

bit to talk about, you know comparison as you can. It's sometimes doesn't help much to compare especially if it's apples and oranges. But we're talking about two cloud ear pieces and and I'd like you refer to dig a little bit in, you know the before after them comparisons, what is now working much better, what things you're eventually missing, you know from the previous software which would be an eventual road map element for AC PS road map. Would you like to do the best one? Sure. And we're actually we're actually working with some of the innovation teams at SAP right now based on our feedback. So that's what's pretty excited

about being both a partner and as a customer. So time entry is always just a challenge in in any professional service organization and while it's it's very functional and that's we're out-of-the-box. We're looking at leveraging things like AI to use natural language time entry and convert that into actually booking the time. So you can basically just use natural language and book my time the same as last week and then the the ChatGPT will actually use that and enter your time for you on that behalf. So just some optimizations on really that time entry part is

our big goal and that's not necessarily a gap, but just looking to to add value to my team as well as take off some of the administration functions. That's not value adding to our organization, right. That gives them more time to be in front of our customers and obviously delivering value to. Them Diek and Rafael, would you like to add some words on this before, after? Well, obviously there's a big change for the users after having worked in for over 15 years in one system and then, you know, switching to SIPBYD, that was a big change in every aspect.

The look and feel, the, the navigation, the, the user interface. I mean everything, the whole logic behind the system was different. And you know you have as many different opinions on that as you have people, you know, because some people are really open for the change and we have other people that after two years are still, you know have some melancholy for the previous system. So that is very diverse. Now what we're really looking forward to with the transition to S4 is that you know we are confident, we know from the

testing now that means starts to show really in the in the testing that S4 is going to be much more performant than BYD was. And that will have a major impact on our organization because currently the users are much quicker than what the system can handle. Which means that we're actually putting some overtime and just getting through the work in BYD. And that will be a massive improvement once we make the step into S4. Which means not only that we will work more efficient but it will also free up additional time that will allow us to

actually engage with our customers more that we currently can do. We need to be we're working the system now. What really our focus should be is working our customers and that is something that we are really looking forward to for April 3rd, the day after. For that, Rafael, would you like to add something on this perspective? I can talk about the project. Obviously we didn't make the by design project and we know that it's very easy at the end of the project to come to have a different opinion and to finger point the mistakes.

We definitely made some more so during that implementation, but we tried at least not to replicate the same mistakes on the previous implementation. Of course we we have a team based in Slovakia and in Hungary and we are serving a project in Germany, which is already something different, but we try to be as much present on site as possible and that the project methodology we hope is making the difference today. Yeah and that may be something that can be stressed enough. You know where we did the choice of the partner for the for the implementation is paramount. You know with SAP that you have

a a thoroughly tested and built system. You know you, you can't second guess the quality of the product that you're buying, but how you implement it and what what it actually will do for your organization there, There is a big, a big difference there. And like I said as a small organization, we cannot focus on the system. We have to focus on our business and on our customers. So what we need is an implementation partner that has all the SAP knowledge in their back pocket and then is prepared

to invest the time to understand our business. Yeah. And really become that in between person, between the system and SAP and our business and be the translator of us who are really focusing on what we need to get done. And then translated that into the setup of the system, in this case of SAPS 4. And in selecting your partner, I think that is really, really important to make sure that you have somebody that is prepared and has the capability of digging into your business and

really becoming a partner in that sense as well. OK. I think it's a great call to actions for all the partners eventually watching this recording. Be prepared and the cloud mindsets, but it's possible. Yeah, it is. Big thanks to you, Russell, to you, Dirk, and to you, Rafael. I think this was a very interesting, very unique thing, and I think it would be super valuable for our audience. 1 main thing that I've learned personally is that it's not possible to outgrow the SAP portfolio. All the SAP by Design customers have the opportunity, if the

business needs it, to go to that next level and to start the journey with ACPS 4 HANA Cloud Public Edition. It was a very. Exciting episode again to our. Audience if you like it. And have ideas about the next relevant topic for this podcast? Please just send us an. E-mail to inside S. Four at SAP dot. Com TuneIn next time and always be inside SAPS for Hana Cloud.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. TechEd #10: How Joule Studio and n8n Orchestrates Enterprise AI

    Nov 20, 202616 minAudio

    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...

    • Apple Podcasts

    Credit the people on this episode

  2. TechEd#9: How AI Transforms Cloud ERP Migrations

    Nov 18, 202614 minAudio

    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...

    • Apple Podcasts

    Credit the people on this episode

  3. TechEd #8: The Benefit of Laying the Groundwork for AI

    Nov 16, 202615 minAudio

    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....

    • Apple Podcasts

    Credit the people on this episode

  4. TechEd #7: The Hidden Risk in Every SAP Transformation — Organizational Change Management

    Nov 13, 202618 minAudio

    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...

    • Apple Podcasts

    Credit the people on this episode

  5. TechEd #6: Five Days to a Working AI Solution — Inside SAP's Forward Deployed Engineering Model

    Nov 11, 202623 minAudio

    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,...

    • Apple Podcasts

    Credit the people on this episode