What every partner needs to know before starting an SAP Cloud ERP project. In this episode of Inside SAP S/4HANA Cloud, host Alina Keilbach speaks with Sebastian Wödl, SAP Finance Consultant and Partner Coach, about the realities and challenges partners face when delivering their first SAP Cloud ERP implementation. Together they unpack the core elements that drive successful cloud projects - from Fit‑to‑Standard execution to structuring the initial system setup and strengthening customer involvement. Listeners will hear how Partner Coaching provides proactive support that guides partners through methodology, scope handling, cross‑functional topics, and the shift from on‑premise habits to a true Cloud Mindset. Sebastian shares insights from real projects, common misconceptions, and the areas where partners often need the most guidance. Want to explore the topic further? Check the show notes for the related SAP documentation and learning resources. Follow Inside SAP S/4HANA Cloud for more expert insights! Show Notes: Learn more about initial configuration of the global settings Initial System Setup and Ledger Scoping: Project P... - SAP Community Follow Alina Keilbach to get updates on Finance in SAP Cloud ERP: (1) Alina Keilbach | LinkedIn Download transcript
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 SAP. As for HANA Cloud, there is no customer success without product success and project success. I'm your host, Salina Kailbach, and today we are diving into a topic that is crucial for success in the partner ecosystem. It's partner coaching. We've all heard the stories, right? A partner starts an exciting ACP Cloud ERP project and soon things starts to feel challenging. Maybe you haven't been there.
Suddenly, a project in distress lands on the desk of a special task force team and it needs immediate attention. The problem is, by that point the project might already be in serious trouble. And let's be honest, the first cloud ERP project is like stepping into a brand new game. It's not a traditional on premise implementation. There is a fresh methodology to get your head around.
You've got a three system landscape plus central business configuration. And the functionality is different because the code lines are different. And those mandatory 6 months upgrades, they're great for innovation, but they require totally different discipline. They mean a new rhythm for testing and analysis. And it's actually a paradigm shift. And it requires what we love to call a cloud mindset. And you can no longer stick to this is how it worked in the
past. That's precisely why our partner coaching service exists. And today with me, Sebastian Verdel, finance consultant, implementing SAP Cloud ARP at our customers and doing partner coaching for our partners, the partners who are starting their first Cloud ARP project. So, Sebastian, would you like to say a couple of words about yourself? Sure. Hi, Ali. Now first of all, thank you for the invitation. It's a pleasure to have the chance to talk about partner coaching in this format.
About me, I'm working in the SAP industry since 2017. Since the beginning of my professional career, I started at a medium sized implementation partner as a finance consultant. IN2023I switched to SAP where I first continued in Adobe Finance Consulting. Since last year, my focus has shifted to partner coaching. In this role, I can leverage the knowledge I've gained in the SAP Cloud ERP environment, 12 partners support their customers and alternatively Dr. SA PS
strategy to become a cloud company. Sebastian, let's start with the challenges that the partners face during their first SAP Cloud ARP implementation. What are those challenges and how do you tackle them in your partner coaching engagements? There are several topics we must address in each partner coaching engagement. To give you some example, one of the first topics we have to address in each engagement is the fit to standard workshop execution. Of course, fit to standard
workshops are standardized component in the SAP Activate methodology, but it's not defining in detail how to prepare and execute them. This is crucial because during these workshops the data configuration items are collected for the realized face. Another crucial topic is the initial system setup. This is very important because some scope items can only be activated during the initial setup and activation at a later stage is not possible. In addition, we notice that cross functional topics are
often underestimated. These include authorizations, migration and reporting. This is not totally AP specific, but we still address them when we have the chance to. Sebastian, you mentioned Activate methodology. Can you explain the key differences between SAP Cloud Therapy methodology and the on premise version? Traditional SAP projects are usually based on a waterfall methodology, which is linear and sequential. In contrast, Activate methodology is an agile approach
still with sequential phases, but within these phases the execution is based on agile sprints. On top of that, the methodology contains tailored milestones and content for Claudia P For example the sign of the backlog and the already mentioned initial system activation at the end of the explore phase or how to approach the half yearly release cycles. So. The Activate methodology actually supports the implementation from the kick off until the go live and even after. And why is it important to
involve the customers at the very early stage of the project? First of all, Cloudy RP is a highly standardized software, more than any other SAPERP solution. Customers benefit from pre delivered content and processes which lead to faster implementation cycles. But this requires the customer to familiarize themselves with the standard processes and content. Therefore, the involvement of key users is crucial for the success of the implementation. Typically, a lack of customer
involvement leads to extended test and hyper care phases. In partner coaching, we emphasize the importance of customer involvement and safe enablement, which is crucial for activate success. But to be honest, it still remains a typical project challenge. And you say that the partner coaching is actually adapted specifically based on the partner and the customer and the project requirements. Can you give us more insights on how you're working with the partners during this engagement?
Sure. What makes partner coaching unique is it's proactive and continuous approach. We don't wait until something goes wrong. We're more like a navigation system for the partners to have the best possible impact. We ideally start the collaboration at the beginning of the explore phase. Usually, we align on regular calls to proactively address current topic dependent on the project phase and continuously build a reliable cloud mindset together. It means that the partner coaching involves regular calls
to address the partner challenges and enhance the cloud mindset. Would you like to add something about the partner coaching, What it is and what it's not? Yeah, that's a very good question. So partner coaching is primarily methodological coaching for implementation partners. We are not customer facing and do not work directly in the customer system. The goal is to ensure the right information is available at the right time in the right place. Partner coaching is definitely not free of charge consulting manpower provided by SAP.
To return to the metaphor, the partner remains in the driver's seat, but we provide the route to a successful cloudy IP implementation. And you are driving all together to the successful implementation and go live. We've already heard about the cloud mindset couple of times today. Can you elaborate on that concept and why is it important to leave behind the old on premise way of thinking? Essentially, the cloud mindset means customers should build as much as possible on standard
functionalities. However, partners with long term on premise experience tend to propose developments and extensions much faster, as they should. This collides with the cloud mindset and can lead to negative impacts such as additional effort during implementation and the recurring release cycles. Therefore, we continuously highlight the need to build a strong cloud mindset to ensure a successful implementation and long term success. OK. Can you maybe say a couple of
words about a fit to standard workshops, how they are structured, What is critical in the cloud ERP implementation project and what is their clustering? Sure. To begin, the overall goal of Fit to Stand Up workshops is to define all the relevant configuration items for the realized phase. To achieve that goal, of course every consultant has their own style, but what has proven to be successful is a short theoretical presentation followed by a process demonstration in the starter system and in the end
collaboratively recording the configuration items in the backlog. When I was preparing myself for fit to standard workshops, I was already noting down all the items I know I had to check with the customer without the risk of missing something. Regarding the clustering. Functionalities are bundled into so-called scope items in Cloudy RP, but these scope items do not always correspond to the process perspective. For example, in finance, there are many separate scope items. Especially in asset accounting.
It is the partners responsibility to cluster the scope items in a meaningful, process oriented and digestible way. This is where we support during the coaching sessions. Thank you for this insight, Sebastian. And now to put a front spin on all this, it's time for my favorite section. This is the first five. I'm going to throw out five quick quirky questions about our topic, and you should answer the questions with just one word or a short sentence. Let's go. What's 1 phrase you would banish
from a public cloud project to sharpen the cloud mindset? I have to go with this has worked on on premise. What's the most common Houston We have a problem moment that the partner coaching helps to avoid? Selecting the wrong initial scope and Ledger set up during the system activation. That's a very good point, Sebastian. We put the link to our blog in the show notes. If partner coaching was a movie genre, what would it be? A body cop film, a training montage or a suspense thriller? Yeah, good question.
But I think I would go for the body cop film as we are building a close relationship with our partners at eye level which is even fun sometimes. In the world of partner coaching, what initial hurdle often becomes the most rewarding challenge for the newcomers? The first implementation itself. After that, you can leverage the gained experience. And finally, what's the quickest light bulb moment you see when coaching a partner on the cloud? ARP methodology.
Hard to say, but maybe the fact that business role templates are not meant for productive use. Thank you, Sebastian. Thank you very much Elena, it was a pleasure. Hope to talk to you soon. Thank you for listening to today's episode. If you enjoyed the insights, make sure you follow and subscribe to Insight SAP. As for Anna Cloud on Spotify or Apple Podcast so you'll never miss an update on Spotify, you can use our Q&A and poll features directly in the episode.
Tell us what you think or vote on the next topics you want us to explore. And on Apple Podcast, feel free to drop a quick rating or review. It really helps others discover the show. Stay tuned, stay curious, and as always, be inside SAPS for Mono Cloud.
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,...