Show Notes: Download transcript as PDF file Useful Links: Contact Ilya Bibik to join the Extensibility work zone: ilya.bibik@sap.com Check more on Extensibility: https://people.sap.com/harish_mangtani Drive competitive advantage through differentiation in SAP S/4HANA Cloud, public edition - my experiences choosing the proper cloud extensibility technique to achieve business outcomes | SAP Blogs SAP S/4HANA Cloud Key User Extensibility: Easier Than You May Think | SAP Blogs Debugging custom logic using ADT in SAP S/4Hana Cloud | SAP Blogs SAP Extensibility Explorer for SAP S/4HANA Cloud (ondemand.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.
Hello and welcome to our podcast Inside Saps for HANA. There is no customer success without Product Success and Project Success. I'm Harish Maldani from Cloud ERP Product Success Enablement, your host for this podcast episode. One of the key elements in Saps for HANA Cloud Public Edition is the standardization of business processes in the cloud. However, we know that every customer is unique and may have different business requirements. To address this extensibility can be a key solution, which
we'll be discussing today in our podcast. Our guest for today are Ilya Bibbik from SAP and Vitali Harlukovich from SAP's Parta organization. Welcome to this episode. Now before we begin, let's take a moment to introduce our guest to you, our audience, Ilya and Vidali. Could you tell us more about yourselves and your role in the organization? Hi, it's Ilya Harish. Thank you for having me. First of all, so I'm with ACP quite for a while, I guess 14 years and my role is project management and my mom that was
for this particular project together with my manager Camila Jamal, my partner Sunil Sethi and from ACP side and. From Lever XI together with Alexei Romenko, Karlukovich and Vitali Gordienko to set up a team that will work on the topics of accessibility for us for HANA Public cloud, also for presales also for customers escalations. Basically we are building prototypes to validate a certain
scenario. Valuable and that was amazing journey actually. We work across all the lobs. And it was great experience and we had so much fun working with Leverex. So maybe Vitali, you can speak a little about yourself. Yeah, hi. My name is Vitali, I'm SAP Technical Architect at Leverex company and customer advocacy team. In this project, we are helping customers with any extensibility use cases for each SAP model in S Ohana Public cloud.
So this is a really short terms. Thank you. Well, great. Thank you and happy to have you. In this episode, let's now talk first about our partner, Librix. Librix is an international company with extensive expertise in serving businesses worldwide. Would I could you please explain to our audience what services Librix provides and how the company's partnership with SAP works? Librix is a global system integrator that provides SAP implementation services. And custom software development
to companies of all sizes. We have about 14 offices in 10 countries across four major regions, North America, Europe, Middle East and Central Asia. Leverage continues to show growth in digital transformation projects and F for HANA migrations and is seeing tremendous interest in ERP management simplification. Also data migration, AI and
sustainability initiatives. So our dedicated to work has helped the company earn the Honourable SAP Gold Partner, SAP Global Strategic Supplier and SAP Integrated Statuses affirming its strong experience and knowledge. Yeah, impressive journey and partnership. Well, extensibility is a key capability of an ERP solution that empowers businesses to tailor the software to their
unique business requirements, fostering agility, efficiency and innovation. However, some of our audience may not be familiar with the current cloud extensibility model. So Ina, can you briefly explain to us the current extensibility model in the public cloud and how it is different from extending solutions in an earlier legacy systems and what various options are available today for the users? If you look at it accessibility,
if you think about terms of on premise, it's a way of doing custom dev on the cloud. That's the message. This way you can get the best of both worlds, so you're also getting is advantages of the cloud to where you don't have to maintain the infrastructure. And it's plug and play you start out-of-the-box at the same time and gives you the flexibility of having your own solution and also because of the way how
accessibility is said that you don't have to worry about upgrades anymore and it's risk free solution. So maybe Vitaly you can give a little bit kind of feedback on the both way or we doing accessibilities. What I would say that current extensibility is related to the clean core concept. Because of this it's now easy to upgrade. As you mentioned you are always on top of innovation technologies and your system is
always stable and secured and you don't make changes to the core code. I can also point out is a learning curve for ABAP in cloud AKA. Embedded steam punk. Also speaking about simplification. Using key user extensibility, it is possible to have low code or even low code extensions. That's really cool. We know how extensibility
provides powerful capabilities to develop cloud ready and upgrade safe extensions like you said. So based on your on your experience in the last few years with customers, what are unique opportunities you see that customers can leverage using the cloud extensibility model in the public cloud? So it's kind of the experience that we gained and what we doing because you know we doing it for some time and we have this repetitive process and some cases that we we work on they kind of come again from
different customers and different scenarios, so reusing and sharing a sensibility concept. This is one of them for us. We actually created a small work zone where we share all different scenarios we worked on and then those scenarios after setting the quantities that we accumulated of the business started, it becomes repetitive. So if you are customer or partner and you in this domain, obviously the first few iterations you know like you have to discover the wheel. But after some time it becomes
repetitive work and it gets easy. And also we recommend actually you can also get our experience and if you e-mail me by my e-mail ilya.bibiccp.com so ILY a.bibikscp.com, I can add you as a member to our work zone and you might have a view of our use cases so that you worked on in the POC and it will give you ideas what can be done and maybe you can reuse some concepts. So easy learning curve to
migrate existing dev capacity from on premise to public cloud developments already have developers and the organization that ABAP. It's will be not too hard to move the skill set you have and implement accessibilities risk free. As I mentioned for the upgrade, I believe the customers that had the on premise custom dev and afraid of the upgrades, they can relate to it. And the low code, no code opportunity with the QS or
extensibility. Yeah, since custom use cases encapsulated from the core based on this, I see possibility of reusing these business cases in extensibility that can be easily customized for each customer. And as you mentioned, we have more information regarding this in our work zone. So I'm sure along with the opportunities, it could also be challenging in the beginning. So what are the main challenges
typically in the beginning when a customer or a partner can start using the extensibility model in the cloud according to you? There is a basically I would say, not challenges, but this is the process, right? This is a process how we tackle every problem, every task, every case. So we validate if you have required objects for our embedded development because as I mentioned there is two ways of doing things. You can do embedded development. You can do the key, user extensibility, the low code and maybe you can also do the side
by side application where we basically develop the full application. So for embedded development you validate if you have the required objects. If there is opportunity to use key user low codes and you validate. If you have the extension points for the key user, you try to always use internal APIs whenever it's possible instead of external APIs. This is CP guidance, but obviously you can use also external and this is what you have for custom interfaces, UIS
for the embedded ABAP that are not generated and available about by default. You will have to use the BTP subscription. This is something that you have to keep in mind when you have a use case and you have complex interface that cannot be auto generated. And the most important point that I find many people kind of many customers, partners don't realize that you can combine different technologies in your use case.
Also embedded ABA also key user and side by side in one use case. And that gives you pretty and good opportunity to solve various and complex use cases and again don't give up, you know you always go get back to business in any use case and there is always a compromise. So far it's almost never happened that we were not able to solve to certain way the problem customers facing that's
good. So I see that for the end users, there are various different options available depending on the business problem or the business need you have. So for now, let's move on to a real business example that would be interesting for our audience for sure. So let's take a look at how SAP and our partner Liver X have helped customers. So Vitali, could you provide us with some insights regarding a recent project where a customer successfully met their unique business requirements by
leveraging of a cloud extensibility model? One of our last proof of concepts was related to HR and service LO BS and was named as Joint Time and Service confirmation. In short, just imagine that service orders and projects can be done by the same person, but the processes of time reporting for project and time confirmation for service orders, they are completely different.
It will be more convenient for the user to have. All assigned work in one place and be able to report time for it. For these purposes we created our proof of concept. We developed the application for this because in South Ohana public cloud in the current release 2308, the person should confirm time and service separately in two applications. With different structures and
logic for confirmation what I can say about our application. By using this application, the user can display all assigned projects and service orders in one screen and he quickly can make and edit service confirmation. He can release items. He can be self assigned to to an unassigned service order. For example he can make and edit time reporting for a project. He can report time for a non
staffed project. Speaking about the project manager, he can manage team timesheet. Now I can already feel that how end users could be project managers. Consultant from customer side or partner side can achieve a lot and to solve the business need by consuming the release objects from SAP and using the cloud extensibility model in the public cloud. So thanks for explaining. Now let's say for all of our audience, whether they are customers, partners or project managers who are interested in learning more about this topic
and exploring especially various possibilities to extend their solutions. So how can they actually get started with it? So my recommendation will be, as I mentioned already, start with us. So start with our work zone where we listed different use cases we worked on. So obviously there is a city help but on top of it there is some useful blogs. So them overall blogs from Marco Valencia who is VP we work with and they give quite broad overview of the kind of topic in
general of the accessibility in general. It's very useful to read them to get a good idea. And also the two blogs from our side that we posted on Key User and on an embedded AWAP AKA Steampunk from Christina Adams. I also recommend as a good starter to for developers. Easy to read and easy to start. Yeah, I think that's quite useful resources you can start with And of course ICP help. Yeah, you know like this is the number one go to.
I would like to also add on this for our audience. As I told in the beginning, I'm coming from Cloudy Air pre Product Success enablement organization very closely working on this topic. You can follow me on SAP community, my name is Harish Mantani. Once again, we have hosted some sessions along with Ilya and Vitali already and we are planning to host more sessions where we demonstrate the business scenarios coming from various lobs on extensibility, showing how you can extend based on your business needs. A lot of more things to come, so
one center plays Also apart from the SAP work zone bids, which Elia mentioned is the SAP community. So where I'm trying to put all the central information, I can assure you that there's enough learning assets and more trainings to come in. OK, good. So I move on. Now that the audience know how to get started, my next question is what recommendations would you give for key steps or let's say the best practices for an extensibility project? The key is to validate if you
have the object or extension point required for your project. So you build the business case. You understand from the business case what objects you need to extend. Then based on this you decide are you going to use the meta development or using key user extensibility or combined or there is you will have to use side by side. What do you missing, what you have with what you work, what AP is you you need and what interfaces you will need. And this will be pretty much drive your decision making on
what technologies and what you can deliver. You work with business, it's you know like it's not development from the scratch. So it's not like the standard development team that pretty much you do exactly what customer needs, but you have certain kind of restrictions because it's still extensions. There is might be more close collaboration with the business as you work with the product owner or with the business analyst or whoever gives you the requirements and maintenance should be also considered with
regards that. Basically you have free pass with regards to upgrades. Things should be stable from when you upgrade the system and it should be seamless from your side and from the resources point of view always. You can reuse your existing resources to work on the accessibility topics and the learning curve should not be a big problem for other developers. We managed it with our local teams and with teams from Leverage where. That were ABAP and the switch
was not hard. And if you again reach out to us and go to the work zone and with those blogs that we have there, the switch in Learning profile can be even more simple for you. There is also Extensibility Explorer that you can use to find different use cases on smaller scale. Very interesting session and nice information to if I have to also summarize it before I end of course. In a nutshell I would say extensibility is a key capability. Like I said for every year B
solutions giving customers or partners the power to customize their business processes based on their unique needs. And the public edition of SAPS for On a Cloud provides a set a new upgrades table cloud extensibility model. So that allows you to consume SAP innovation smoothly leading to future proof extension that are life cycle compliant and required no adaptation during the innovation cycles. So with that, Ilya and Vitali thank you very much for your valuable insights and expertise shared on this podcast episode.
And of course a big thank you to our audience for tuning in. If you have any suggestions for future topics you would like us to explore on the Inside SAPS for on a podcast, drop us an e-mail at Inside S4 sap.com. Until next time, stay tuned and be inside SAP S for HANA. Thank you.
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,...