Unfiltered & hands-on: A real-world business use-case with SAP BTP

In the past, siloed departmental applications and technologies have sprung up across enterprises. The result, chaotic disconnected IT landscapes. This piecemeal approach makes it impossible to respond to changing market conditions and customer demands, let alone stay ahead of the competition in this dynamic fast paced business climate. Sounds familiar? It's time to get future proof. SAP Business Technology Platform, a unified cloud platform that delivers integrated technologies and solutions that work together, allowing to become more nimble, adaptable and responsive. It includes everything your business needs in four pillars on one unified platform to unlock data and processes across business functions. The data and analytics pillar consists of technologies that help you capture, manage and govern your data to drive better business outcomes. Analyze all that data to accelerate insights and transform it into the answers you need. Extended planning and analytics help you bring your people and plans together to increase agility and performance no matter what events unfold. You will drive agile decisions with planning and analysis combined in one solution. The application development and automation pillar empowers you to build apps faster with low code and code first solutions to meet business needs head on. Automate and improve business processes and workflows to enhance business efficiency. SAP's integration solutions enable connected business processes across the enterprise. Seamlessly integrate on premise and cloud based applications, processes, services, events, and data to accelerate innovation and response time to changing business needs. Finally, the artificial intelligence capabilities of SAP Business Technology Platform allow you to infuse AI into your business applications to help your business run smarter. Analyze with intelligence and automate with speed while managing your AI use cases to run responsibly with transparency and compliance. The technologies of SAP business technology Platform have an intrinsic understanding of the data and process in your existing SAP applications via business centric services, pre built connectors, and pre delivered business content. And, SAP Business Technology Platform is open. It's your choice which cloud infrastructure you trust. No matter what business challenge you face today or tomorrow, SAP Business Technology Platform empowers you to meet it head on. Future proof your business, adapt quickly to change, and respond to new demands. All you need to succeed in your market on just one unified platform. Hi, everyone. Welcome to today's webinar, the first in our Unfiltered series. We're excited to get into the real world applications of SAP business technology platform with a focus on Avidade Cables proof of delivery mobility solution. You'll see how SAP build apps can drive business transformation through low code development, plus get expert insights from Yanni Coetzee from Equis Labs and Andrew Barrison from g three g on overcoming challenges and unlocking the full potential of SAP BTP. G three g and Fuse Labs, both members of Group Elephants, collaborate closely to provide comprehensive end to end services to our SAP clients. With over forty years of combined expertise, our partnership delivers innovative solutions tailored to meet the evolving needs of our clients. We'll also have a fifteen minute q and a at the end, so feel free to submit your questions in the q and a box throughout the session. We'll do our best to answer them live, but if we don't get to yours, well, there will be another opportunity to ask your SAC BTP questions when we send out the webinar recording. Do kindly note that the session is being recorded, and by participating, you consent to being included in the recording. You'll also receive the presentation deck along with the recording for your perusal. So before we get started, we want to start off with a poll, and we want to know, what is your current experience with SAP build apps? So we'll be launching the poll in a few seconds, and you can reply to that with your answers. We'll just give everyone a few moments to give their answers. So the poll question to start off with is, what's your current experience with SAP buildups? Never used it but interested? Played around with it but still learning? I've used it for small projects, or I'm actively using it in business solutions? Let's just give everyone a few more seconds to answer. Perfect. Thank you so much. So, Andrew, just before we hand over to you, just to let you know, the majority of our attendees today, they have never used SAP build apps, but they are interested. Eighteen percent have played around with it but are still learning. And then we've got seven percent each who used it for small projects or actively using it in business solutions. Thank you so much, everyone. Andrew, over to you. Great. Thanks, Amy. Good morning, everybody. Alright. So I'm just gonna start off with the agenda. So three things we're gonna look at today. I'm just gonna set the context initially around the business technology platform, just to hone in on the particular area that we're gonna be focusing on today and give us the context around that. And then we really wanna get practical. So with permission, we're gonna talk through, a real world scenario that we've implemented at a client of ours, a long term client of ours. And as we do that, I really hope you'll be, you know, thinking about your own businesses, which, of course, may be in a very different industry, but you may have real world problems that you need to solve. So I just hope that this will make it a bit more tangible for you, as we move through what they did at Abodea. And the particular application that we built for them is called Sign for It. It's a proof of delivery application, and I'll be handing over at that point to Yoni Kasia, who, particularly for our tech more technical audience, will be going through some of the details associated with how that was implemented. Right. So to kick us off, many of you would have seen some sort of manifestation of this slide over the years, just sort of affectionately known as the hamburger slide. And, essentially, this is the latest one which has the core SAP solutions in the stack with the business applications, if you like, in the semicircle on the top, with the core s for HANA Cloud ERP in the middle. And then beneath that, you've got the business technology platform, which is essentially the innovation enabler across all those particular business line of business applications. And then if we just drop down to get the context of what we're looking at today, around the blue box towards the bottom of the screen, we've got four areas. We've got app development and automation, data and analytics, the integration suite that some of you may have used already, from a BTP standpoint, and then this is now all becoming, underpinned by artificial intelligence and the dual, Copilot, which SAP has recently introduced. So the purpose of our discussion today is going to be around how we use, build apps in the app development quadrant, if you like, of the business technology platform. Alright. So let's talk through, the use case that we're gonna explore today, which was implemented at, Aberde Cables. Aberde Cables is a leader in Africa around, cabling, interconnected energy solutions in South Africa. They're based in Gauteng and down in KZN and produce a lot of the cables that Eskom, use for the power grid. And one of the challenges that they had was around their distribution challenges from a process and compliance standpoint, particularly where they're shipping goods across the border. So that was the problem that we were presented with, and we'll explore it in a bit more detail in a moment. But, ultimately, the solution that was implemented, yes, was an application which digitized the process, but also behind the scenes, of course, that whole process is integrated into the end to end ERP system. So we'll show you how that, that fitted together as well. So if we go into a bit more detail around the challenges they were experiencing. So first of all, it started with some, some audit findings around revenue recognition. And what was typically happening, and I think a lot of companies that distribute goods actually do this, is they were in the warehouse when things were being shipped out, they were printing the delivery notes, posting the goods issue, and producing the invoice all at the same time, throwing it in the box and shipping it out to wherever it was going. And the challenge with this was particularly amplified when you had cross border ground transportation time lags, particularly at month end. So, for example, in that case, your revenue and your cost is not necessarily aligned and might be falling, in the wrong month according to the process that we're using prior to that. So in that particular context, that leads us on to the third challenge, which was around that time lag influencing the payment terms. So they're producing the invoice, you know, it could be three or four days actually before the transfer of ownership happens, and, therefore, the, the payment terms were incorrectly calculated, which then had a knock on effect into payment disputes, lack of process auditability as well where physical delivery notes were being signed by customers. And slowly but surely through the truck drivers these were finding their way back, you know, to home base, so to speak. So a very slow lag process, which was therefore causing a lot of ambiguity and creating an option where customers could say well I didn't actually receive those goods or I didn't receive the quantity that, you know, that you confirmed. So at that point as well we end up with lots of credit notes particularly where goods may have been damaged en route and not the quantity shipped is not the quantity that's received. And, of course, that difference could create an excuse for non payment as well. And then finally, the other challenge associated with this was around sales commissions for salespeople, which was based on when the revenue and the margin was being recognized, and this potentially could end up being in the wrong month as well, particularly when it's over month end. Right. So the process that we implemented around proof of delivery, nothing overly complicated, but fully integrated into the ERP system. The first step was, loading on the deliveries from SAP onto the driver's device and, in fact, their distribution was outsourced, so the outsource company makes use of, of this process and their application. Those get loaded on. And then in step two, this was where we fundamentally changed the way they dealt with their accounting where when the goods were put onto the truck, so to speak, they were moved to a stock in transit account rather than reflecting the cost of sales potentially in the wrong period. Step three, when the goods were delivered to the customer, the process was fully audicable with the proof of delivery being captured, along with the signature and any damaged goods or over or under delivery, was being captured with photographic evidence and so on. Right. So after this step, right there at the customer site, we would then have step four where the proof of delivery is immediately, updated in the SAP system real time along with any supporting documentation. So, you know, the, the signature of the customer, any photographs that are also attached against the delivery in SAP. And then what we perform is, proof of delivery related billing. Alright. So at that point, the customer has confirmed they've received the goods. At that point, we bill them resulting in accurate payment terms and the cost and revenue at that point, being reflected accurately against the sales and cost of sales accounts. So you can see it's a fairly simple process, but it touches on quite a lot of areas, where they were having some challenges and sort of resolved them, in a number of different ways. Right. So I'm gonna hand over to Yanni now who's going to take you through what was involved in building this application. Yanni? Thanks, Andrew. Okay. Great. Let me quickly share my screen here, and we can get going. Here we go. Right. So we, we did go through a couple of steps, and we've tried this blueprint that we created in the end a couple of times. And this is what we're gonna base our the next couple of minutes on to say, what is this kind of recommended blueprint we found works for implementing, you know, solutions? And this one specifically focuses on B2B solutions or let's say SAP cloud based, solutions. Right. So our blueprint is quite simple, and it is loosely based on the design thinking process as well. This is just a more practical view of this, with the focus on BCP. So you would need to define your solution, and this is also just to know what your business case is. You might not always know, and I'll get you that when we dig into that a little bit deeper. You do need to understand the flow of the data and the different components of your system. So that's the architecture. You need to choose the right tools and might seem simple, but BTP is vast. So there are more than one thing that can solve your problem, probably. Then you go build it. Once you have all of these things in place, that's only when you get to the building phase. And then once you've deployed this you can monitor and enhance it going forward. So the first part we're looking into is the define part. Now like I mentioned this process is based on the design thinking part or design thinking methodology. And the first part here as part of the, SAP AppVowels network, we do a lot of these exploration workshops. Now in Aperture Cable's situation, they knew what they wanted to solve. But we do see a lot of cases where, some of our clients might have B2B credits, and they basically will need to find or want to find a way to utilize those. Or you might get a new KPI or an objective to that you need to introduce AI into your business, and you're not exactly sure how to do that. And that's where we can do the explore workshop, and our beautiful app has available to do these workshops in, and that's what we found really powerful for users. So you get into a place where you define what you want or just and once you know what you wanna do, you define you go and unpack that further. Alright. Looking at step two, which is the architecture, the design, and the flow of the data, the components in there, there are quite a number of things. Now as you, as you know, BTP is quite bossed, and then SAP themselves took a turn into say we're going cloud first. And with that, they introduced the business accelerator hub, which documents all of their APIs that's available. So your first step would be, you know, I have an x four system. Maybe, you are still on prem. We can then there's another step involved. But if you are cloud based and you have BTP, your first step would typically be, let me go to the Accelerator Hub to make sure that the data I'm on to get you is available. If not, you either need to create request it if you're public cloud from SAP to open up or make the data endpoints available to you, or you can go and implement it yourself if you are a private cloud. But this would be a very good starting point. Like, can I do what I want to do? This excludes the step that you did before this to say, isn't there anything out of the box already? You know, there's so many Fiori apps out there. Maybe SAP already created an app for me to solve my problem. But if you know it's very specific to you, this is to where you will start. Now for our use case, for AirPADER cables, we checked proof of delivery, which makes sense. And, oh, lovely. Look. There's a blue proof of delivery, and we need to know also, the outbound delivery information. We need to get that to get the document delivery document information. Fantastic. The APIs are there, and we are happy. The one little snag that we did not realize in the beginning was a snag is the fact that the proof of delivery service is a SOAP service. It's not OData. Now without getting technical, it's just different ways in which you read data from an API. But build apps does not support direct link to SOAP services, only to OData. So our solution would have been delivered much quicker if that wasn't OData service as well. But I'll show you in a bit. We had to go and create a workaround for it, seeing that was a bit of a snag. There's another thing that you need to look into here as well. Look for the ones that are deprecated. Make sure that it is active. And then the last one is the modules, which these APIs are in. Because another, part of this application is using the attachments API, but that is not stock standard for all clients. So it's an additional module that they need to buy or utilize that they might not have, and that can also cause issues in your solution. So make sure that you know that the API is there, that it's deprecated, not gonna be removed anytime soon. It will still be supported. And then also that the modules will be available at the client or that you have the module that this that you're looking for. Alright. They're not only architecture wise, but just tool or component wise, you know, are the things that you're looking for available? For us, we had to go to the marketplace in the sample apps and look for something that can capture a signature and, great, there was a component that does it. We do not have to worry about creating our own thing because this can affect, what you do and what you decide on technology wise and, also, the architecture and the flow of your data. So just make sure that look into the components. If there's something a little bit different that you're looking for, is it available? Can you use it? And then looking at the architecture, this is what we ended up with as an architecture. Now if you look at the bottom here, we have your build app. It talks to you through the connectivity service, which is your SAP Cloud connector, to your public or private institute. There's the flow. You get you the data, you read it, it comes back beautiful. Because of that tiny little snag, that is the fact that we can't directly call the soap, soap services, we had to go and create this little sub route here, the little Cloud Foundry application that reads the soap service for us, translates it into an OData as a service, and then gets it that back to the build app. And this is a pro code part of it. You know? Now you're not in the low code, no code solution anymore. You need, you know, some more development skills to do something like that. And I think that was quite evident in this case that you needed some pro coding, in here. Nonetheless, this was the architecture that we ended up with, and we knew what we wanted to build now. Part of this architecture step is also figuring out your flow. You know, is the flow of information, the integration, the different systems, how do that connect up? And then also to make sure that you have a basic idea of what your interface might, you know, or this quality user experience, needs to be. In our case, we know that we knew we had to capture signatures and, you know, images. So it's not necessarily you need a tool and the right components and everything to do that and make sure that you design for that in place. And when you put it down, you can see, oh, there are parts that's missing. So make sure that you do the, you know, at least low fidelity wireframes in the beginning. Great. And now we move on to the tools, and the tools become very interesting, especially if you're looking at BCP. Now this image is a little bit older because it has those five pillars at the bottom. I just put it down there because it gives you an overview of everything that's listed in those pillars. And these are still high level. If you dig deeper, you get stuff like document information extraction and things like that, which is sub subcategories of the services and the tools available in BTP. There is a lot, and you need to make sure that you understand it and have a good enough idea of the new things that they add in and, you know, the capabilities of the stuff that's in there so that you can decide what you need to do. So if we take our Avedere Cables example, we knew that's an app we knew that it would be an application where we need to read data, so we get the document delivery document information. We needed to make adjustments and modifications on the items in there. We needed to capture signatures and photos, and then send that back to our s four system. So that's the basic flow. Now let's say we decide or we investigate automations, just BTP automations. You can probably do this and create a solution for that with a little form, but your user experience is not gonna be good because you will have to go and take pictures and then upload that and take a picture of signature and upload that. And then that form needs to post it to your s four system. So can be done. Your experience won't be great, and then people will probably not use it to and adopt the solution. So maybe not the best thing. If we look at low code, build apps, that's pretty much what we set decided on in the end. Definitely, much faster turnaround time. A lot of the functionality is already, or this stuff already built for you. So for instance, authorizations is there. You just tell it. You connect to your BTP with this through this destination or whatever it might be, and it will handle the logins for you, for instance, making it a little bit easier. It's also click and drag, user interface, and then workflows that you can more easily build out. So in that sense, you do save time. There are some functional limitations that you need to keep in mind. For instance, you can't call the SOAP service directly, and that might be limiting. So in this case, you know, we might have ended up with the same time frame if we went pro code, but that's debatable. Pro code, there are few to no limitations in terms of what you can do Technology wise, always within limitations, but, you have a much broader scope that you can work with. It is bigger efforts because you need to rein or reinvent or redo basically some of the components that's already done for you in build apps, but you have full control of it in there. So that is also not a bad thing. And then we have AI. You know? I love the hamburger image because from the beginning where they had AI as a separate pillar, I said it doesn't feel like it should be a separate pillar. It should be baked in as a foundation for any of the pillars that's, in BTP, and that's exactly what it is. You can use, AI to enhance what is there, but you should not necessarily, you know, do it at this or in this case, it wasn't an AI first solution. It shouldn't be a chatbot, and then you need to capture pictures, and it makes it a little bit difficult. You know, it's not gonna be easier. So AI is good. AI is fantastic and a very big, trend at the moment. But because it's a hammer, you shouldn't go looking for nails kind of, the situation here. So that's the tools. And just to give you an understanding that there's a lot in BTP that can solve your problem for you, but you should select the correct one. Right. And now after all of that, confining into building this app the app this application. Right. I'm quickly gonna pop over to, build apps, which is here, just to give you a quick feel of it, you know, it is really, an easy solution that you can use. This is the application signed for it that we build, and you'll see it in action a little bit later. But as you can see, you have your components here on the side, that you can use. There are some logic flows that you can use here. For instance, take a photo. That's you know, I can click on the barcode picture there, and this will allow me to I'll add the take a photo of flow and will open up my camera for me so that I can take a picture of the market. So as you can see, there are different kinds of things that you can do here. There's a little spinner running there. I need to you know, once everything is loaded on this page, I need to hide the spinner. Those are the types of actions that you build into the flows here at the bottom. If we look at our add button here, you know, if we enter a barcode or scan a barcode, we can say go and get this, and, basically, it will go and get that for you, and then set the variable, and then it will go to your back end. It will go and get the address information, create a record locally, and then add that to the list that it would be shown here in the end. You know? So it's a whole flow that you would go through when you add an item to this list. And that's kind of where you sit there. Variables you manage throughout here, so you can have global app variables and so forth. And then integrations is kind of where you end up first. If you wanna, just show you here, for instance, before you can do integrations, you will tell it that you add SAP BTP authentication in here, and that's gonna be the default login when you get into the application. It will authenticate use that as the IDP to authenticate you. Once you've added that, you can go and you can add, you know, through your very secure destinations and cloud connectors, you can go and add your in this case, our public, cloud instance here. So our escrow system sits here, and you can see the entities that is available. And you can go and add entities, from there, additional entities that you might not have there already. So that just gives you an idea that it is quite easy to, you know, connect this to my system, get the data. And then on the user interface side, I will go and I'll be able to use, you know, connect these values up to what is shown on the screen. It's a very click and drag, very interactive things are, there. And there is a learning curve, but it's definitely much easier than going to write an application from scratch. One little snag we ran into might not affect you, but we wanted to do the public and private cloud ones, together in one app and just make a logic switch, but you can't do that. You can only add the entities with a unique name, and these have the same names in the public and the private instances. So we needed to just split it into two apps. Okay. And that's good. I just want to give you a feel of it's quite easy to, you know, get things running, get them up here, get them working. And just to mention, there is still some coding little bit of coding or let's call it rather scripting that happens inside of build apps. And that's what we use to create sign for it as you can see. Right. Back to the presentation. This is my backup slides just in case it decided to not work. And now I'm basically at our last part, which is monitoring and harms for your end users. While I talk over this, I just wanna play our sign for a solution, a little video that we capture just on the side so that you can see the way that it's that it works. Monitoring is very important once you've deployed this application. You need to figure out if there's any, you know, issues or errors or if a bug pops up. So application logs is quite important, and that's typically what a developer will use. And that these things that I'm mentioning now, these come from directly from SAP. That is inside BTP already. Activity logs to see histories, the history and usage of users. This is also good to, you know, enhance your application, see if people are using features or not using features. Also, talking to those users are very important to build on what you have here. For instance, GPS location might be important to that building to this application going forward or AI that does some document information extraction. So depending on what your needs are, do look into enhancing what you already have. Don't just leave it there. And then audit logs, that's also quite important to know which people had information or access to which information at any given point. And those things are just important to keep your application running smoothly, to make sure things aren't going down, to make sure that there aren't any security risks to it, and then, you know, add to it, build on it as you go forward. Great. As you can see on the side, you hit that our solution. You select the document. The client can capture their signature there. You can capture any faults that might have occurred in the delivery, and then it is submitted, and you can continue to the next delivery. Right. With that, I am handing over back to, Andrew. Thanks, Johnny. So, yeah, so just to close off around this particular use case, I think, as you can see, I mean, through a very simple application in a sense, but it's actually had a powerful impact, on this client's business in terms of some of the benefits they've achieved. So, you know, touching on a few of them, of course, the revenue recognition, and triggering the billing off the back of the proof of delivery ensures that we have our revenue recognition compliance. And, also, you know, due to the reduction disputes and, you know, like digitizing that process of the proof of delivery, the clients also see an accelerated cash flow with the real time invoicing. So their day sales outstanding from creation of the sales order through to receiving of the cash has come down as well, and the natural implication of that is that your working capital improves. And then I think, you know, the process transparency that they've had, and they also they have certain partners that they use where, almost like trading customers, they're actually using the app now as well to even go through that process and work with them around receiving the, you know, the deliveries and ensuring that the billing goes through without any, any process disputes or payment disputes. So it's really helped this business, in a big way in a very in a very short time as well. And I think a big part of that comes down to the fact that, you know, the customer has formally accepted that delivery. It's fully auditable, and in a sense, you know, undisputed. So one example, I hope that just makes it a bit more tangible, to you as you think about the various scenarios within your business. Great. Thank you so much, Andrew. Thank you so much, Yanni. Those insights were really great to hear. Before we jump into the q and a session with the both of you, we just have one more poll for everyone. So we would like to know, how do you see SAP buildups fitting into your business? So let me pop up that, poll. I'll give everyone a few seconds to answer that, and then I'll share the results shortly. So the last poll for our session, how do you see SAP build apps fitting into your business? Rapid prototyping and innovation, building internal tools and automation, creating customer facing applications. We're not too sure yet. I'm still exploring the possibilities. Let's give everyone a few more seconds just to answer, and I'll share these with you shortly. Still changing a little bit there. I'm gonna end the poll. So just for a quick overview, the majority of our attendees, they are not too sure yet. They're exploring the possibilities. We then have around six attendees building internal tools and automation and, the rest creating customer facing applications with rapid type prototyping and innovation. Right. So we have received a few questions on our side. I would like to get started with a question from Philip Sutherland. Thank you so much for your question. This is directed to both of you. How is authentication managed? Similar to Fiori where you need a full user license, is that required? Okay. Sorry. Alright. No. In this case, it's not really a user that is on the system necessarily. So you can just use BTP as kind of an identity provider if you want to. Great users on there that is not a cost to something. You know, it is it's just users and identify them and they can use the application. So it's a little bit different in that sense. I think that the one would if they need a sorry, Andrew. If they need to connect to the back end and you need to make sure it's only that user, not a technical user connecting to the back end. You know, there are some situations where they might be the user so you know who they are connecting to your Sfour system. So I think that's the one case where you find it. But if your application doesn't require, you know, you knowing who this person is and that they have authorizations and things on their s four system, then you don't need it. So it's a little bit case dependent. Yes. And maybe just to add to that, I think, you know, depending on the scenario, you know, you might be looking at indirect licensing as opposed to user. So in the example that we went through, it was, you know, through a technical user and then indirect licensing because the specific, user was being captured elsewhere. Perfect. Thank you so much for those answers. We have, another question just around sign for it specifically. They want to know how quickly did it take you to develop sign for it? I can take that one? So, how long is the string? No. I'm kidding. So it was, in this case, it took us a little bit longer because of the soap, snag there than we wish to, but it's definitely weeks and not months if you're looking at development. And if you look at a normal app development, you're talking about months a lot of time. So that in this case, it was definitely an accelerator using build apps for it, and we can recommend it, especially if you're looking at a very basic application when you read, modify, write, basically. Build app build apps are perfect for those kind of solutions. Perfect. That sounds great. Thanks, Yanni. So, Andrew, over to you. Yes. So just to say, I mean, in this app, essentially, you know, as Yoni showed you, you know, we're reading the delivery, so it's pretty straightforward. And then we update the proof of delivery, which, again, is just some attributes against the, against the delivery and then post back, you know, documentation and so on. So fairly simple in terms of, you know, data transfer, but, of course, very powerful in terms of driving the subsequent process for billing that comes after that. Okay. Perfect. Thank you so much. And just a new question that popped up, and I can also answer that if you want. Oh, yes. That would be great. Thanks, Yoni. Okay. So the question is that, they're not on s four yet, but, they think that you can just use, BTP on ECC as well, and that is hundred percent correct. I always advocate to start using BTP immediately. Don't wait until you're on s four to start using it. You can enhance your processes, automate things. You know, there's so much that you can do even while you're on prem. And if you do it correctly, if you do the switch to s four, then, you know, porting those applications over to the new system as well doesn't necessarily need to be, you know, a big thing. What you can do is if you design your API layer, which will now sit on ECC because you need to go encode that OData service there. If you create it in the same way that the APIs are created for the Sfour systems, switching over is gonna be really effortless. So you will still have your investment, down the line as well. So, absolutely, don't wait to migrate while you're on ECC. Do it. Perfect. I know that in a lot of these SAP BTP conversations and webinars, a lot of people are talking about these SAP BTP credits. Can you provide a little bit more information about what those credits actually are and how you could go about using them for some of the projects that you'd like to get started with? Sure. I mean, I can comment first. Yeah. So, essentially, a lot of there's a number of different commercial models associated with procuring BTP. Often what we recommend for clients that are just starting to, let's say, explore the different services available in BTP is that they take what's called it's called a pay as you go consumption based model where it's almost, you know, like a mobile phone. You consume and start to get a feel for how much you're gonna need. And then at that point, you look at, at signing an agreement where there's a bit more clarity around the likely usage. So the way the credits work is often sometimes you can essentially, you're buying an amount of, you know, rands, essentially. So you might say about, I don't know, twenty thousand rand a month or a year or whatever it might be. And then that credit gets consumed depending on the service that you use. So whether you're using build apps or some AI service, AI core, or, interestingly enough, even some of the analytics applications like SAP Analytics Cloud are now available to essentially purchase as part of, the BTP credit. So it's a little bit of a minefield. I mean, as a partner, we're getting our heads around it slowly. And even, from an SAP side, you know, things are changing quite rapidly, but, essentially, the credits is an amount of rand that you then consume off. Thank you, Andrea. I think there was a lot of questions around that, so thank you for that clarification. Yanni, there's just one last question, for you. We want to know about offline applications. Is can you use SAP build apps? Is it relevant for these offline applications? So, yes and no. So there I think this basically creates, a React application at the core of it. So you can then port it over so that it is something called a PWA app or a, a progressive web app, and that offers some offline capabilities for you if you add that on top of that. But it's still just creating a web app in this instance. So I would rather say using, the libraries that is available to create native apps should your solution ask you know, require it. And there are very few times where you need a proper application the compared to a web application because the maintenance on it is definitely much more, extensive. Developing it is much more extensive. All of those things. So if you do have a good enough reason, then you would have to do a proper development from scratch for those kinds. And even for that, there are man a bunch of solutions like Flutter that can compile to both and web. So there are a lot of solutions, but build apps, I wouldn't recommend if you want an app. Thank you so much for that insight. Andrew, Yani, thank you so much for your time today, and thank you to everyone for joining us. We really hope that the demo provided you with, valuable insights into how SAP BTP can address some of the challenges that you may be experiencing. Of course, as we mentioned beforehand, you will receive the presentation along with the recording. If there are any other questions, we will provide a platform to submit additional questions, so that will be available to you within the next few days. And thank you so much again, and we look forward to you joining us at our next unfiltered session. Thank you so much, everyone. Enjoy the rest of your day.