
Episode 100: Clean Core: Achieving Modern, Flexible and Cloud-Compliant ERP Implementation feat. Accenture
Show Notes: Download transcript as PDF file
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Show Notes: Download transcript as PDF file
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Welcome to our podcast Inside SAP. As for Hannah, there is no customer success with our product success and project success. I am Yanni Peter Schmidt, your host for this podcast episode and we'll talk about Clean Core, a concept and an implementation approach to achieve a modern, flexible and cloud compliant EMP implementation with SAPS for Hannah. Today as guests, we have Stephen Vazdov, our Chief Technology Officer for ACPS, for Hannah with ACP and Jack Abelhoff, EME
A/C, P Business Group Lead from our partner Accenture. Hey guys, warm welcome to this episode. Welcome, Yannick. Hi, welcome. Thank you, Yannick, and hello Stefan. Thanks for having me here. I'm pretty excited. It's it's a great topic to discuss. And so am I, to be honest, before we talk about. The topic itself I'd. Like to introduce yourself, guys? Maybe you'd like to tell something to our audience that people don't know yet about yourself so it gets remembered. Yeah, Stefan buts off my name and 22 years with SAP and in the S4 HANA space since 2013 since
its inception. Started as developer at SAP and former program leader of SAPS 4 HANA, also in development. And now I'm back in development as as Chief Technology Officer for Cloud ERP Private points. I love bicycles, everything. So I love mountain bikes, gravel bikes, race bikes. Especially doing it conquering the mountains. But I also love restoring bikes I restored for old vintage bikes and for some persons that have meetings or customers that have
meetings with me in my Home Office. One of this bike is also hanging behind me on the wall. Thanks chefan and lucky me I can see the bike. That looks pretty awesome, so let me share a little bit. So my name is Dick Appelhoff. I'm in the consulting business related to SAP for decades I would say. So I actually started with R2. Believe it or not, I'm really passionate about that topic. But in private there's two things which stack out I would say. One is music and the other one is sailing.
So there's two things I wanna share on the sailing side, when I was young I actually participated in the round the world race actually in one leg. So I sailed from Japan to Hong Kong which was really an adventure for me at that point in time, pretty exciting. And then on the Munich side I actually used the Corona time to get back to music myself. So I played the violin when I was young, but I always wanted to start playing the piano. So I actually took lessons and educated myself on piano since the Corona time and advancing
more slowly than I when I was young. But I'm really enjoying it and it's a good, relaxing moment after a long, long day of work. Very cool. Thanks to both of you for sharing those insights. And now back to the topic of the day, I'm sure that part of our audience is familiar or partly familiar with the concept of Clean Core, but of course not everyone. I think this concept of Clean Core as a target to achieve a modern, flexible, cloud compliant ERP. Stefan, What is clean Core? Concretely, what is included and
eventually what is? It not so for clean core. To describe clean core the best case scenario describes having an up to date system on the latest release with a cloud compliant extensions and integrations as well as an optimal master data quality and process design. This sounds super, but why is it so important? Because the technology is changing so fast. And now even with AI, generative AI, supply chain resilience,
etcetera. The faster the software is changing, the more often customers need to adopt these software. And in order to be flexible, to stay on the latest release and to consume the upcoming innovations that any software vendor is delivering, you need to put yourself in a place to upgrade your systems more frequently. And this can only be or more easily be achieved. If you reduce your system
complexity, if you reduce your customizations and stay close to a standard, if you build your product extensions in a way that decouple them from the software code. So providing creating extensions using only public AP is cleaning up your master data and your daters and your records, doing archiving to reduce the systems size and using cloud applications for example. Because at least at SAPSAP as a
cloud strategy and the future innovations will mostly only be built in the cloud, for example on the sub business technology platform. It's not an on premise only world anymore. And the more you foster to have a clean core using cloud native integrations, for example, the easier it is to consume side by side innovations like for example generative AI use cases to automate your processes.
I couldn't agree more, Stefan, and let me chime in here. On the digital core, we're using a kind of a picture to make it more grabbable, but the key point you mentioned is agility and flexibility. You want to have faster time to market in terms of innovation and you want to have a more direct investment in differentiating capabilities rather than spending, you know on a broad level into your complex system landscape. When we talk about digital core, we always use this picture of four layers and I think that's
quite helpful. So we we say that digital core was SAP comprises 4 layers and the initial layer is the cloud infrastructure and the security like you mentioned it. So if you need to have the scalability and the resilience in that layer, the next layer actually is the foundation enterprise system, which in our case is the software as a service, very cost efficient operation system you need. And then you have the composable technologies who are connecting those applications and enabling the the, the collaboration, the
the data topic you mentioned comes into play and you want to have interoperable solutions as we say. And then finally you have connected solutions. That's the agility and flexibility on top where you have your innovation, where you can apply Gen. AI quickly, where you can take the innovations from the market faster and more quickly and more distinct in terms of where you need them. And and those four layers in our terms define a digital core. So I hear you guys speed of innovation, adoption of innovation, agility,
flexibility. Now of course we're talking to customer that maybe are thinking about the next upgrade going to the to S4, right. And the deck you mentioned you started with R2, my first upgrade was with R33 OB, I remember that many customers. Really. Had not a fear, but we all know that it was always very disruptive with a very thorough project plan, a very follow upgrade plan etcetera, etcetera. And my take from what you've
said guys is that today and especially for the future with the speed of innovation and the time to markets, the customer are not willing to have this disruptive event correct. But most of the upgrade come with manual efforts, So what else do they need to consider as a challenge when they approach migration and upgrade planning? Very good question, Yannick. Definitely it's always easy to talk about it in the way we are doing it, more from a managerial perspective than doing it
actually. But there's obviously solutions for some of the challenges. So let me go back to the importance and you mentioned some point, but I just want to rephrase them. So all our clients need to get into a more agile and flexible architecture to respond to the changing market circumstances. So it's all about agility and flexibility. They're all asking for how can I do my investments more in the really differentiating areas in the innovation parts rather than spending a lot of money in the
areas where I look for very low total cost of ownership. That's where we go for standardization. And then the Third Point is the overall lowering of the operating costs. So if we take that, we can easily translate that in or related to some of the challenges you mentioned some when you teed up the question, Our clients have the burden of the complex legacy. They have built and invested in capabilities and they have an excellence in those and they also have a certain pride in those capabilities. Untangling that landscape and
really quote UN quote cleaning it and going back to standard and making the decision which is differentiating in the industry, in the market and which is not differentiating. This is one of the biggest challenges we have in the dialogues, so that costs and needs a lot of attention. The second challenge I would point out is something Stefan already mentioned also is the existing data structure. If you look at the legacy systems, if you look at this web
of applications they're sitting on that mean that you have a silo data structure and if you want to really gain the benefits of digital core then you need to re architect your data structure so that needs attention and work. And then last but not least, there's a big component of change and resilience. As I said, all of those clients have a certain excellence in their capabilities and they have
built capabilities, they have experts around and asking those to go away from something which is proven and working and gives them their market position right now and moving in something which is not crystal clear. This is a big, big topic for programs to be successful. So change and overcoming that resilience, I think, is really one of the most important challenges to address. Great. I like a lot when you said they have a certain pride in this
legacy because this is where they build the excellence and as well where they differentiate them from competitors eventually. And of course this is where you build the comfort zone, Stefan. We all know that the big strength of R3 of ECC is the ability to customize as much as you want. And I'm like look at the topic of the ABAP custom quote from their customers. What is the future of this concept? That was the strengths in the past of SAP that we shipped the core code, the ABAP code with every ERP on premise release and
customers were heavily using it and also partners, they cloned the code, they modified it, they built additional code add-ons, partner add-ons, customer add-ons on top as all the code was available. And you, for example, you have to build an own quotation engine and you're missing a data object or a business functions. You just searched in the ABAP workbench or in the dedic for objects, you found it and all of
a sudden you created also a dependency for example to Pharmaceutical industry solution or oil and gas etc. Everybody did it, also SAP. And with this we created a high tangled code. It's kind of spaghetti code with lots of references. Now the world is different, it's fast changing and we build more flexible code, more modular code. Customers and also partners, they look for more flexibility in the cloud for composable structures, also composable ERP structures.
As Dirk said, you want to have a core running running your core system, your financial system, your production systems, etcetera. But you want to have the flexibility to implement supply chain solutions for warehouse insights, for track and trace functionality, net business networks etcetera. So we want to become more modular and for this you need to also rethink the way how you build your extensions. We have created now under S for harder a new extensibility structure what we call the three
tier extensibility model. So building cloud compliant extensions and modernising your legacy custom code is the most important part of the clean core. And if you follow this so-called 3 tier extensibility model for private cloud and on premise helps a lot. So what is this 3 tier? It's not database, application server UI. So Tier 1 describes all cloud compliant code, so cloud compliant extensions and code
that run in the public cloud, private cloud and on premise and are super upgrade safe. Tier 2 describes public API wrappers around classical bodies where that is a workaround that we created now in case SAP is missing some public APIs and the Tier 3 are all your legacy custom ABAP objects. This is currently your set coding that you have and you go will should be under clean court to get rid of most of the tier 3
and move them to Tier 1. So tier one are all extensions that you create that follow the strict public cloud extensibility model which means they only use public released AP is they are built either inside S for HANA using other cloud or they are built side by side on the BTP connecting wire, public or data API or a business event to the s s for HANA back end.
So the goal is to review your custom code, rethink what you really need, move as much as possible into this so-called Tier 1. So build your extensions in the same way like you have to do in the public cloud, because the public cloud is always clean core per default. Now during this exercise you will find obstacles and struggles. You will find AP is public AP is that are missing. Why?
Because in the old ABAP world, in the old R3 ECC world there are more than 11,000 AP is bodies and Barbies and function models you can use. As for harder and the public cloud has I don't know don't nail me down. 6000 read AP is via CDs views and something around 1500 public O data AP is and business events and this will increase over time. Now you will come to the point that somewhere in transportation
management you are missing public API and this is the reason this what we call 2 tier SAP is now defining nominating classical bodies. Where SAP says this is a body and you can use it as a public APISAP won't change anything in the future year. We keep it stable and then you use the ABAP Cloud Development tools, code name embedded
steampunk in S4 harder. You create a wrapper around this body and have a public API and this public API can be then used in your Tier 1 coding. So this is a workaround, but it's also clean core that when you build these wrappers around stable bodies and then you have the Tier 3, this is really then that contains your custom legacy objects that customers converted
from ECC to private cloud and to S for harder and they do not comply with the clean core principles. For example, you use direct table access, direct file access, native SQL, etcetera. So getting moving everything into and writing completely everything new doesn't also make sense. So the goal is first delete unused parts and delete as much as possible from your custom code that you have, renovating the extensions and moving as
much as possible to tier one. And if you have 50,000 set objects, it's OK to have 20,000 left in tier 3. Then govern them, govern them, control them, let them run. Keep them as is. If they don't create pain during upgrade, it's OK. If some points of your legacy custom code creates problems during upgrades, Spower, SPDD comes up, etcetera, then you have to take an action.
If not, leave it as it is. Clean core doesn't mean to rewrite X all your zip code that you have. Clean core means control it. Get it under control and if someone in your IT department develops new extensions, they shall do it according to the tier one public cloud extensibility model, only using public APIs, et cetera, and not going to ABAP Workbench, looking up in DATAC, any kind of using
generated code, et cetera. So it's a change in mindset. I like that very much, Stefan. I think it's important that when we discuss the topic, we are not saying that the legacy world is something less valuable or not. It's all about making conscious decisions and starting a journey. And I think you described it very nicely in terms of there's no need to move everything to new from day one to day two. We have some time, but it's important to make a conscious decision when to do it and when not to achieve your overall
objective, which is this agility and flexibility you want to have and and less dependencies. How do you stitch the modules together and the components together in a more agile way to allow you to react more to the market circumstances? That's the key point, and it's all about a journey. Exactly. A journey maybe from the what Stefan called the spaghetti code model to the cloud compliant extent similarly model and many of our customers are already on this journey. So the I'd like you to please
share a concrete example of a recent project where this clean core concept and the journey that you've componied has really helped the customer to make a difference. How can a partner like Accenture completely help there? I'm picking an example where actually we work together with you guys in a large industrial client in South Germany and has been quite a discussion coming back to my point about a journey. But I think we are now doing the right things after thinking through everything in in in
joint workshops and sessions. So we have defined jointly SAP and Accenture with the client, the North Star, so to say where we want to go. And then we looked at how we can go there. And of course we had all kinds of accelerators and tools and ideas and methodology. But the main point I want to emphasize here is that we it took us a long time together to find a good governance to address the challenges. And this has started as a more you know, technology IT driven initiative and now has evolved
in a complete business initiative. And I think that's really important because while you define your clean core or digital core, you always want to look at the value you can create for the business side. So what's the business value for the investments you're doing? That's exactly why we are emphasizing this standardization so much Stefan talked already about. So let's standardize wherever we have no differentiation to the market where we want to go for low total cost of ownership. And let's spend wisely the money in the areas where the business
desperately looks for speed, time to market. Sometimes they want to try something and then after four months they go to a different solution. You can't do that with 20 year old architecture and solutions. It's impossible in this client. I think we have a very, very robust governance now which is led by the businesses very much in collaboration with the IT. Accenture obviously helps with a lot of as I said methodology and tracking and you know running
the program as we speak. But at the same time of course with expertise and specific functional areas with deep industry understanding to help with the business cases. So you need to, you need to really start from the strategy down in the business model and how you want to steer and operate your business before you go on the technology. So I think the benefit of us in this circumstances and in general in the market is that we have an expert pool which really ranges from strategy consulting to management consulting to
really in depth technology consulting, implementation skills. When I talked about the digital core and the four layers, we can bring in infrastructure and security people which is really important if you if you want to make sure that your future architecture is secure, but it's also robust. It's completely different from what what the client has today. Today they are sitting still on data centres and old architecture. So it's a, it's a really leapfrog. You need to make sure that you have the expertise and that's
why it's important that that we partner with with you guys in the market because we can combine our capabilities. You have so much expertise in the solution itself, but also in the infrastructure and in the technology space, which is really, really valuable for the client. So I think bringing that together and having an ecosystem which is helping the client to achieve the objective is important and we are doing that. It's still beginning of the journey. I I I have to admit, I mean we are not done, but it's a it's a big complex thing and I think
that this is one of the lighthouse activities we have in the market right now in our region. I think you said the key thing here, the governance is led by the business. You don't go for IT driven decision. It is the enabler obviously or you are business case driven and and Stefan I have a questions when it comes to extensibility and business case decisions, where do you what I've heard many times that some colleagues even within SAP but of course outside to understand that when
you want to be the extension you go by default on BTPI understood from you already there are more options. You mentioned Abedinstein Bank, but. What? Would be a good decision tree, you know, where do you go left? Where you do go out. Can you please elude on that one? Yeah. Absolutely, because keeping the core clean does by no means mean moving all extensions onto the BTP. The business technology platform is a key integral part of SAPS for HANA Cloud and we are eating
our own dog food at SAP. In development we are building future innovations and solutions side by side on the sub business technology platform. Think about sustainability management, a set of BTP apps, green Ledger that we will build or carb. The Carbon Accounting Hub, how it is called, is also a set of BTP apps, the digital manufacturing cloud and digital twin business networks also built on the sub BTP. So when you want to extend SAPS
for HANA, you have two options, first of all to build it on stack inside SAPS for HANA or side by side on the sub business technology platform. When to use what? So let's assume you want to extend an existing S for HANA process. You want to extend the financial accounting process or somewhere in production planning MRP where your extension sits close to the core S for harder data.
Then you do it on stick. If you extend the financial accounting process, it doesn't make sense to replicate the whole Universal Journal ACT doc A to the BTP to do logic and then copy it back whenever your extension depends on fast SQL Server access to the SAP data heavy data exchange, lot of data loads. One example, you want to extend the MRP, the material Requirements planning process with a bomb explosion of millions of data you do it on.
Stick with ABAP in S4. Harder if your extension needs strong consistency with the SAP transaction. Yeah, at the moment a sales order or production order is stored. Your custom object also needs to be stored. Do it on stack in SAPS for HANA and we have in S for HANA our low code, no code, so-called key user extensibility tools. But now also ABAP cloud embedded in S for HANA. We call it code name embedded
Steampunk. You have all the ABAP world flexible coding in South for HANA you can do then extensions but only against public AP is so. But for all other cases, please do it side by side on the Business Technology platform and especially when you build a hub scenario when you want to connect multiple S for HANA systems together, like you want to create a supplier portal or a customer hub or something like this.
If you are a partner and you want to build a multi tenant partner SAS solution, you build as a partner a track and trace functionality that you want to share multi tenant with multiple customers. Do it on the BTP. If you build an extension like a customer portal or a dealer portal for car manufacturers and those users should not have access to the back end system to S for HANA. Do this on the BTP, it's perfect because you have separate segregation of of duties and if your extension or your
extensibility, your application needs higher frequent shipment. See you want to update your BTP application or your extensions monthly, daily, hourly and the core is for harder system only upgrades, yearly, twice a year, etcetera. So these cases do it on the BTP. It shall be wisely checked when to use what and we promote this as a decision tree and guidance. It's also written in our extensibility guidelines and papers. And let me give you 1 customer
example here because the customer has also done this. And let me talk about shortly about Hitachi Haitesh. It's one of our reference customers and Hitachi Haitesh from Japan. They are semiconductors, HITECH company, some 3000 employees and they are they have currently a corporate ERP system and S4 HANA private cloud and two S4 HANA public cloud subsidiary systems. So private cloud plus public
cloud. And they started with S4 HANA already in 2018 and back then they had 9000 add-ons or 9000 extension components. They reduced them over the last five years they reduced them to 470 by deleting lot, cleaning up, moving processes back to standard functionality and out of these 400-7022 extensions are on stack in S4 harder and the
rest The 450 are outside on the BTP and they are using public AP is and they have really separated this and kept the core clean with only clear 22 extensions there. They are strictly governed and what is the benefit? Back then in 2016 they were on EHP 7 and they did an upgrade to EHP 8. It took them overall 1 1/2 years, 15 months roughly with Unicode enhancement package
etcetera. Now they are an S for harder private cloud, public cloud and they are doing yearly upgrades. 2020, they have done 20/21 and now 2022 and the last upgrade to 2022 took them 30 days. So end to end with setting up the project, testing, upgrading etcetera. Why? It sounds super but why? Because they have their extensions under control.
Most of them are using their decoupled from S4 HANA code via public AP is. But there's the real major thing is they trained their upgrade muscle, we call it, because they did so many upgrades between 2016 and now 2023 and the first years, it was painful, it took quite some time. And you get better, you get better the more often you do it. And now it's an easy way and they can fast consume the innovations. And this is mainly the mantra
about clean core, to put yourself in a position where an upgrade is not a painful event anymore. Fantastic example, Stefan. I, I really like it. I think the couple of points I want to highlight, it indicates faster getting the innovation in the market, if you want it right. I mean, one is the, you know the burden and the complexity a few years ago compared to today, but you can grab the innovation in the market more quickly.
That's one. Number two, there's obviously a lot lower costs, right? You do it in 30 days rather than in 50 months and you don't have all your talent stuck in some standard work, which doesn't add a lot of value necessarily. Last but not least, what I really like is you describe this also as a journey, as I said before. So this is not something which I can switch on and switch off. It's a learning for the organization and this is learning also for our clients in the markets. One thing where I think we need to get better as partners is to
explain what you started with, explaining in terms of really making sure that the market better understands our clients, better understand you know the logic and the decision tree and what do you put where and why. What I feel is that there's still a lot of uncertainty and probably lack of understanding and knowledge of this future architecture in terms of how you can best leverage the BTP, what you put in, what you shouldn't put in. There's probably also a bit of based on the uncertainty, there's tendency not to make a
decision and to grab more understanding before you make a decision. So I think we need to educate and guide our clients a bit more and better on that topic because this is key to get what you what you just described on this excellent detache example to get to the North Star and get to where you want after a couple of months, years and so on. Thanks a lot guys. Love what we shared. We talked about the why this is needed. So what it is concretely where should we do something that needs to very close to the transactional side of the house,
Where can you differentiate with extensibility on the BTP like a lot of the customer example. And of course I understand here from you the partner perspective is really to educate the market, educate our stakeholders on you know how to bring that concretely to the street. And question that I have now of course is what is the road map of all these concepts maybe the fun you would like to elude here what as AP in store to further advance the clinical strategy? Yeah, definitely. We are constantly helping our customers really to to move
here. And so especially on the BTP side with the sub build code tools, it's way easier now to build extensions on the BTP. In future, especially this year, we will also more put more generative AI into the code generation. We'll be much more easy and comfortable to build on the BTP cap applications cloud application programming model. The same we will do also on the ABAP cloud side. When you build according to RAP,
Restful ABAP programming model. As said ABAP Cloud is the new cloud like ABAP language version. SAP is using it also to build As for HANA public cloud versions here and we ask any kind of partners customers to move from classical ABAP to ABAP. Cloud roll out has been done on Tekkit last year and will be also done this year. In addition on the rise with SAP we are currently creating a clean core dashboard. It's a dashboard fury
applications that analysis your customer system, shows non compliant code, shows outdated data structures in compliant master data, gives you hints and also connections and links to tools to analyse it. You can define KPIs for example, usage of public APIs, usage of non public APIs and et cetera. In addition on the rise with ASAP, we are also discussing now to promote customers differentiated pricing migration
incentives for those customers that strictly follow the clean core. Because when you are on the private cloud on the rise with SAP and have achieved the Clean Core, we you drastically also can reduce your TCO. It's also easier for the partners and also for SAP to perform the upgrades and we are discussing partner certifications for clean core compliant at ONS. We want to really also promote partners that change the classical ABAP add-ons to clean core compliant decoupled from
the core, either moved on the BTP or using ABAP cloud. And here also, this is on the focus for 2024. Great. So, so we're approaching the ends. What I just understood is that tools are here to support there's a proven TCO impact. Before we close this session, I'd like for the two of you to, to help give a concrete take away to our audience, like a step by step that the company should follow to achieve the clean core. What are your top recommendation? Maybe you want to start Stefan.
The call out to all customers that are facing a lot of set codes and are sitting on an on the ECC and want to move to S4 HANA. Don't fear the code, get it in structured. The way to clean core is first of all analyse your custom code. Delete as much as possible that you have. If you have sub Guis or transactions that are only used once a year or haven't been used for the last three years, deleted. For the rest of the custom code structure it check where you can
move to a standard functionality. If you have an own track and trace functionality, use the standard one. If you have an own travel management solution, move to conquer etcetera. Then you are the pass for clean core and for the rest of your custom code. Gradually refactor it and it's code hygiene. The refactoring needs to be done. It's it's getting control over your old code. And then you are on the perfect way and the move to the cloud. And whenever you want to,
consider moving to public cloud. Public cloud is clean corporate default. If you currently do not achieve clean core in your on premise system, you're most probably not ready for the public cloud. So do it. Get it done and started. So we are happy here to help. I would have that said the same I would say to my clients, initiate the journey. There's multiple steps to do moving your SAPECC into S4, rise cloud, whatever solution public or private. This is only one step in a
longer journey as we have discussed. So I think start now is, is the key point make conscious decision is the other point. I think we we elaborated on that having a decision tree. I think it's worthwhile to spend time to think through more from the business perspective in terms of what your strategy is, what business models you, you most likely need, what management cycles you have, steering model, operating model before you move in technology as I said to the four layers. So when you define the North
Star and you look in the technology, you need to have a robust alignment with your strategy and your with your business. And then you can look into how will future infrastructure and security have to look like in the cloud, how the SAP should look like, how the composable technologies and the connected solutions tie into that. And then you can define a road map and that could be flexible in terms of which step you take. If you have a plan, which step you take at one, what point in time.
You don't have to do everything at the same time. But I think there's a bit of an urgency to start the journey because it's as we described, it's quite a certain complexity You have to manage. You need to think through staff, you need to make a conscious decisions. There's a couple of positives in the market. Obviously, there's a huge acceleration if you think about Gen. AI in terms of what it gives you, in terms of capabilities, but also in terms of delivering programs like that. So there will be a higher level
of automation over the coming months as we speak. There's a lot of investment in the market getting into accelerating delivery as much as providing new capabilities on the process side. So we will be able to achieve targets with lower cost and in shorter time. Then we have done that in the past. If we take all all our good things together already today, we have an acceleration, visible acceleration in how we deliver those things. And I expect over the next 12 to
24 months an exponential increase of capabilities which will help us to deliver those programs to lower costs and more tailored to the value case we have created jointly. So start the journey. It, it will be exciting, it's will be challenging as we discussed, but you have to start otherwise you will not have the all the benefits we described in
finally having a digital core in the market. Great closing words. Thanks a lot. In a nutshell, with a sense of urgency. So start the journey, make conscience decision, don't feel the code, but refactor the code and then you are on the right path. I'm sure our audience has learnt a lot from your respective insight and experience, so thanks a lot again Diac and Stefan for joining us on this episode. As always, feel free to drop us a note at the inside S4 sap.com and let us know which topics are
of your interest. TuneIn next time and always be inside SAPS for Anna. Bye, bye.
Nobody is credited on this episode yet.
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,...