Join host Alina Keilbach as she explores how SAP transformed its internal operations by adopting SAP Cloud ERP, showcasing the true meaning of SAP runs SAP. In this episode, Treasury IT solution owner Maximilian Stein shares the inside story of how SAP’s own IT organization modernized key Treasury processes through a move toward public cloud. Discover why SAP chose to shift to cloud ERP, how embracing standard functionality helped eliminate custom code, and what the team learned while applying the Activate methodology to redesign processes step by step. Max reveals the challenges, milestones, and vision behind creating a future cloud‑ready Treasury landscape through a hybrid, side‑by‑side architecture.Whether you’re planning your own cloud transformation or simply curious how a global tech leader evolves from within, this episode offers practical insights, technical takeaways, and a candid view into SAP’s journey toward a smarter, more agile ERP future. What topic would you like us to discuss next? Send an email to insides4@sap.com.
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 Vahana Cloud. There is no customer success without product success and project success. I'm your host, Alina Kalba, and today we are diving into a fascinating journey of how SAP implements SAP Cloud ARP system through its internal IT team. It's a tale of innovation, challenges and valuable lessons. Joining us is a key player involved in this significant shift towards public cloud setup.
Today with me is Maximilian Stein, SAPIT Treasury Solution owner. Max, would you like to introduce yourself? Sure. I'm Maximilian Stein. I'm the Treasury IT solution owner. I'm working currently at SAP. Of course, I joined SAP five years ago and during my time I made quite a lot of treasury related tasks. And with that after some time last year, I got not a product owner for that topic. And we are, yeah, most likely discussing today our cloud journey for that.
Perfect. Could you start by giving us an overview of this project and what motivated the decision to transition some key business processes to the public cloud? Sure, I will do. First of all, at SAPIT, so CPIT would call ourself, we always try to follow the principle of SAP runs SAP. In other words, we use our own products internally, what's often called eating your own dog food. This approach ensures that we experience what our customers experience and it creates a
tight feedback loop for our product engineering teams to deliver rapid improvements. Naturally, this raises the question, how do we adopt to the latest solution and stay close to cutting edge technologies? For us that means exploring migration to the public cloud. The benefits We are clear, greater functionality delivered more frequently, improved business efficiency and a reduction in our total cost of ownership. In our case, we realized that moving to higher releases would allow us to replace custom code
with standard functionality, which was only available in a newer version due to technical constraints. That insight led to us. Could the public cloud solve this challenge directly? Back in 2023, we decided to aim for the public cloud and figure out the best path to get there. So you kick the project off in 2023. How long has the project been in the analysis and set up phase and what have been some key milestones during that period?
We tackled the analysis phase quite proactive to our business to be honest. Basically there was a key point in the bank account management account review that the newest functionality was not on our OP 2023 FPS one release back in the days. So as a result, we began to consider how we could leverage the public cloud to provide this access for our team. We followed the activate guideline and started then for each treasury sub area the assessment and figured out a sequence. How we want to carve out our single process into the public
cloud was so-called side by side approach. Maybe in the final stage we really will have the so-called treasury workstation and the public cloud solely with a basic account replication to our centralized Wahana system. But we are still in the elaboration and with several partner teams we now also doing this approach. And yeah, to be honest, we are figuring out more and more teams are interested to move there. And with that, we have now, for example, group reporting and the environment safety and health team, which also wants to have some modules in the scope.
You've mentioned that the project goal is to bring Treasury bank account management, the environment safety and health module, and the group reporting to the cloud. Why were exactly these areas selected first? This is quite easy to answer that were the first teams which figured out that there are some processes they really need are currently only available in the public cloud. So there was a bit of a force for us to figure out, OK, how do we get there and how can we consume the solutions on our own based on that we needed to start
and align, OK, how do we get this public cloud into our system environment? What are the possible ways to integrate this path into our process and carve out single processes for the public cloud? Of course such a cough out is internally easier to be done maybe from ATCO perspective than for external customers. As we are within SAP, the license costs are a minor part for us. We try and also explore with our DNA always to be of course the customer 0. So therefore, we accept the risk
that during this adaptations, maybe we need to have closer loops with product engineering because the technology is not yet on the level we might need. And of course, we might figure out some loops which in the development area were not recognized. But in the end, yeah, we all aim to apply the cloud wherever it's possible and started this journey finally. And you were not alone on this journey. You got a lot of support from your team and other SAP colleagues, with the project's
team size ranging from one to 10 people. How have you managed resource allocation and ensured that each aspect of the project gets the attention it needs? It is a bit of a larger hurdle than only thinking. This is the sole project team for the public cloud. Actually, we're investing into this topic while still ensuring operations and further rollouts in the existing landscape are happening. So we also did in this time frame simultaneously the private cloud migration for our systems.
So this application team was doing that project actually in parallel while ensuring operations on the private cloud. Indeed, the benefit is that the public cloud of course safes us a lot of operational aspects as this is taken care by the public cloud operations team. Just thinking about node installation as some examples, we can see that the efforts for us as a team sticking on the standard so far will reduce. And only the testing efforts will be also covered by product
engineering. If we follow the the path and use also the Cloud ALM on the testing for that, for example. So that the Cloud LM integration was quickly done and we could set up their project following again the activate guideline steps there and link our transports to the task we are executing and getting a holistic overview over our current project progress. And this enables us to run with the precise resource allocation. So really with this one to 10 persons and of course, we learn here how to maintain and track
in a new tool. But after some time we got used to it. Let's discuss the lessons learned so far. Could you elaborate on the integrations like IAS and IPS and the challenges around authorization management that you have encountered? Sure. Basically the first big challenge of course where that no one of the application side, so neither the Treasury, the environmental health and safety or the group reporting team really have the experience with the authorization set up. Let's say no one of us really
touched this IES tenants ever before. That is usually taken care of our central team in our setup and in the end, now we need to make our hands dirty and make this real nice experience. Of course, although in the beginning it was big bumpy for us, when we explored it in the start, we had an issue to get access to our IS tenant at all. After we figured out how to get there, of course, we now needed to know how to maintain our internal authorization objects there. And yeah, after some time, we
figured out the IS team actually can support us and we get the new IS tenant, which was then maintained by this different team. So after some time really got it addressed also, but also some improvements due to this, we're done by the product engineering. So that in the end we had the ability that these IES tenants can be actually selected during the initial deployment of an SAS service and sub FORMI. So however, it was beneficial to observe for us how each
component interacts and contributes to seamless integration between the access request management to the IS and the IPS. And yeah, due to all various elements, of course, we then got to the level where we get again, the single sign on experience, but it wasn't very good, let's say knowledge sharing for us, of course. And as you say, or asked, it's a one of our biggest lessons learned. And did you have any instances in the project by the implementation really felt like
plug and play. Can you share an example or describe what made this experience stand out? I mean a real plug and play experience for me where the integrations with the different communication systems and scenarios while in our private cloud, the connector settings like cumbersome and it's only possible via tickets due to our internal structure. The public cloud offers here a great concept. You have predefined integration scenarios, for example, the MDI integration, the authorizations we were just talking about or market rates as some examples.
And you simply select the scenario update maybe 2-3 fields and you have all set up. So communication systems and scenarios was so straightforward that we really could retrieve market rates from our bring your own rate solution within 10 minutes. Oh, that sounds great. Did you also have some unforeseen challenges that the team had to navigate and how were they overcome? Well, actually the whole project, if you say, would be an unforeseen challenge. All the following, the discovery
assessment, we recognize that in many topics we need to involve other teams, learn new things as there are plenty of things which we are not solely in the context of the application, for example, group reporting, Treasury or AHS ever touched. Yeah, we talked just about the authorizations. Not only did we learn a lot about the authorization concept due to this, but I learned a lot about the MDI integrations, several BTP to public cloud integrations, and surely about general configurations in the Central Business Configuration
tool. Given what you have learnt from this project, what advice would you offer to other companies planning to migrate to SAPS Wahana Public Cloud? It's a very good question. So my advice would be maybe something like search for the explicit pain points where you believe a new setup, Greenfield for example would be ideal. Try to model it in the public cloud and once that is working to your needs, figure out the main integration points and you can get a new process in a side by side scenario.
And you will get the whole benefit of the public cloud running for you as a company by eliminating the pain points in your processes and accelerating the journey to a lower cost of ownership while still staying on the edge technology. Of course, that requires a given, let's call it cloud mindset. Within the cloud, you need to be ready for constant changes and validations leading to a higher speed, but of course a higher challenge to follow the pace and keep the colleagues on track with the changes so that the
process performance is not impacted. This challenges can be only addressed if the organization feels really ready for the pace of the cloud and has a cloud mindset as a consequence. So it's really important to have this cloud mindset. Thank you for this insightful conversation. We would like to close with our Fast 5 is our Fast 5 questions that are supposed to be answered short and give the audience a nice crisp answer to important key points. Are you ready?
Yeah. Remember, you should only answer the questions with one word or a short sentence. Let's kick up What's the one word you would use to describe the transition to the public cloud? I would use Curiosity. What's the most surprising element you've found in the public cloud? And how easy many things are now compared to a private cloud system set up. If the project was a beverage,
what would it be? I believe it would be a beer, always good for a drink to a lunch to a party accelerator, but still you should sometimes not drink too much. Name 1 superpower you wish you had during the project. Oh, a tough question. I think it would be something like I would like to have the superpower of time manipulation. Sometimes you are currently in the flow of the configuration or making progress and alignments and setups, and then your next
meeting is popping up in the screen and you lose the drive. What's the quickest win you've celebrated on this journey? I think the set up of the market rates was done for the whole corporate within several hours enabling a very good integration. Of course, the single rate still don't need to be configured like before in South Bahama, but it was still impresses how easy the market rates management PTP solution was connected with the public cloud. Thank you, Maximilian, 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 suggestions for the next topics via Inside S4 at sap.com. If you enjoyed today's episode, please give us five stars in Spotify and Apple Podcasts, TuneIn next time and be inside SAP S 400 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,...