1 00:00:25,600 --> 00:00:29,440 Namaste and welcome to the the first podcast episode of the 2 00:00:29,440 --> 00:00:34,160 year 2025. On behalf of the whole SAP 3 00:00:34,200 --> 00:00:39,080 family, I would like to wish you a very happy New Year and we 4 00:00:39,080 --> 00:00:44,080 hope that you had a great start to it already set to achieve 5 00:00:44,360 --> 00:00:47,320 those New Year resolutions that you have taken. 6 00:00:49,120 --> 00:00:55,120 Also, thank you for tuning in and making the year 2024 a great 7 00:00:55,120 --> 00:00:58,600 success for us. It was only because of your 8 00:00:58,600 --> 00:01:03,840 support and motivation, we could reach more people across the 9 00:01:03,840 --> 00:01:09,200 globe, invite guests and talk about topics that are crucial 10 00:01:09,200 --> 00:01:13,320 for digital adoption with SAPBTP as the foundation. 11 00:01:14,240 --> 00:01:18,360 Please continue that support and we will try our best to bring 12 00:01:18,360 --> 00:01:22,360 you more such topics that will help your business process to 13 00:01:22,360 --> 00:01:26,960 become intelligent and more importantly, your enterprise A 14 00:01:26,960 --> 00:01:32,120 sustainable 1 to help you unleash digital innovation 15 00:01:32,360 --> 00:01:35,360 across your business functions with SAP BTP. 16 00:01:35,960 --> 00:01:39,400 In this episode, we have three main sections. 17 00:01:40,640 --> 00:01:44,520 First we will talk about some new additions done to the SAP 18 00:01:44,520 --> 00:01:49,560 BTP services, then deep dive into conversation with a topic 19 00:01:49,560 --> 00:01:55,080 expert at SAP BTP and how they are accelerating the application 20 00:01:55,080 --> 00:02:00,040 development and automation with the Locode, Procode and 21 00:02:00,040 --> 00:02:04,200 Generative AI tools. Followed by some road map items 22 00:02:04,200 --> 00:02:12,920 for 2025 S. Stay tuned till the end starting 23 00:02:12,920 --> 00:02:17,080 with the What's New section. Last time we talked about SAP 24 00:02:17,080 --> 00:02:21,600 BTP Cockpit and Jewel. There is this new feature where 25 00:02:21,600 --> 00:02:26,840 the team have added created by and modified by fields to the 26 00:02:26,840 --> 00:02:31,120 instances and subscriptions page of sub accounts and to the 27 00:02:31,120 --> 00:02:34,360 service instances page of Cloud Foundry spaces. 28 00:02:35,240 --> 00:02:39,320 Note that the feature is now available for all three types of 29 00:02:39,320 --> 00:02:44,600 entities that can be created in SAP BTP Cockpit, that is service 30 00:02:44,600 --> 00:02:48,520 instances, environment instances and subscriptions. 31 00:02:50,200 --> 00:02:53,360 With the document grounding capability in June, it now 32 00:02:53,360 --> 00:02:57,360 supports Oauth to Client Credentials authentication type 33 00:02:57,680 --> 00:03:01,320 when you create a destination configuration in the SAP BTP 34 00:03:01,320 --> 00:03:05,640 cockpit from SAP Business Application Studio side of the 35 00:03:05,640 --> 00:03:08,600 house. If you are subscribed to SAP 36 00:03:08,600 --> 00:03:13,560 Build Code, you can now use the Refactor feature to optimize 37 00:03:13,560 --> 00:03:17,240 your code, truly enhancing development experience. 38 00:03:19,360 --> 00:03:23,080 On the SAP BTP Developer's Guide there is now a reference 39 00:03:23,080 --> 00:03:27,520 application dedicated to SAP Partners that provides a 40 00:03:27,520 --> 00:03:31,960 recommended way to becoming a SAS provider of multi tenant 41 00:03:31,960 --> 00:03:38,480 applications based on SAP BTP. These were just few selections 42 00:03:38,480 --> 00:03:42,120 from the list of items that are new to SAP BTP services. 43 00:03:43,040 --> 00:03:46,760 To know more, take a look at the links mentioned in the show 44 00:03:46,760 --> 00:03:53,920 notes. Now moving to the section where 45 00:03:53,920 --> 00:03:58,040 we invite guests to discuss on some selected topics. 46 00:03:58,520 --> 00:04:03,840 And this time we will deep dive and understand how SAP Build is 47 00:04:03,840 --> 00:04:06,640 taking the application development and process 48 00:04:06,640 --> 00:04:12,040 automation to a whole new level powered by SAP BTP, where 49 00:04:12,040 --> 00:04:15,640 cutting edge innovation meets unmatched productivity. 50 00:04:16,560 --> 00:04:21,079 And for that, we have Hemantraj, who is a Senior Director from 51 00:04:21,079 --> 00:04:23,560 the Product Management Unit of SAP Build. 52 00:04:24,240 --> 00:04:27,600 Welcome, Hemant, to our January episode of SAPBTP Talk. 53 00:04:28,200 --> 00:04:31,000 Thank you very much, Karl. Glad to have you, Hemant. 54 00:04:31,000 --> 00:04:34,400 On our episode. Whenever we invite experts in 55 00:04:34,400 --> 00:04:38,240 our podcast, we play a small fun game with them. 56 00:04:38,760 --> 00:04:41,400 Do you want to give it a try? Sure. 57 00:04:43,480 --> 00:04:49,040 OK, so the game is you give me two or three words, could be 58 00:04:49,040 --> 00:04:52,280 something that you see right now, and I will create a joke 59 00:04:52,280 --> 00:04:55,800 with them. If you laugh, I win, and if you 60 00:04:55,800 --> 00:04:59,440 don't, you win. And of course, I can then put my 61 00:04:59,520 --> 00:05:02,240 generative AI tool on a learning assignment. 62 00:05:02,720 --> 00:05:04,920 So Are you ready? Yes. 63 00:05:05,440 --> 00:05:06,960 OK. Chair. 64 00:05:07,400 --> 00:05:08,920 OK. Coffee cup. 65 00:05:09,840 --> 00:05:11,400 OK. Whiteboard. 66 00:05:12,600 --> 00:05:19,840 OK, let's see what it generates. So I have the first response and 67 00:05:19,840 --> 00:05:23,640 it goes like this. Why did the chair, coffee cup 68 00:05:23,920 --> 00:05:30,600 and whiteboard start a band? Because the chair rocked, the 69 00:05:30,600 --> 00:05:34,400 coffee cup kept everyone energized, and the whiteboard 70 00:05:34,720 --> 00:05:38,920 was always drawing up big plans. Great. 71 00:05:39,160 --> 00:05:42,440 Yeah, great. I mean, I still remember that it 72 00:05:42,440 --> 00:05:46,040 is on the same lines. Last time my AI tool also came 73 00:05:46,040 --> 00:05:50,080 up with a similar line of joke, but I'll be sure to make it a 74 00:05:50,080 --> 00:05:52,800 learning plan and then do some learning on this indeed. 75 00:05:54,280 --> 00:05:57,600 So listeners, if the words matched to what you also see, 76 00:05:58,120 --> 00:06:00,520 give us a shout out on our social media channels. 77 00:06:01,000 --> 00:06:05,520 And if you can find a better joke, also boast that our social 78 00:06:05,520 --> 00:06:07,240 media handles is adding the show notes. 79 00:06:10,840 --> 00:06:14,440 Now we resume back to the topic for which we invited our guest 80 00:06:14,440 --> 00:06:18,560 to the talk and him and if my memory serves me right, it's 81 00:06:18,560 --> 00:06:22,160 almost 2 1/2 years. We introduced SAP Build for 82 00:06:22,160 --> 00:06:25,960 developers, IT professionals and business users who want to 83 00:06:25,960 --> 00:06:28,960 create and customize business applications. 84 00:06:29,760 --> 00:06:33,280 Last year, you and the team broadened its capabilities and 85 00:06:33,280 --> 00:06:37,680 integrated Java, JavaScript and ABAP development with AI. 86 00:06:38,000 --> 00:06:41,680 So many congratulations on that. Thank you very much. 87 00:06:42,040 --> 00:06:46,160 Yeah, in this episode, Raymond, we have, you know, some new 88 00:06:46,160 --> 00:06:47,920 listeners who are joining us today. 89 00:06:48,640 --> 00:06:53,600 And for them, let's take a minute or two to tell what SAP 90 00:06:53,600 --> 00:06:57,720 Build is all about and what it can do for line of businesses. 91 00:06:58,080 --> 00:07:00,960 So please if you can. Sure. 92 00:07:01,920 --> 00:07:06,240 So when we talk about the SAP Build, SAP Build is the go to 93 00:07:06,560 --> 00:07:11,440 solution for any app development, extension, building 94 00:07:11,800 --> 00:07:16,040 process automation surrounding any line of business 95 00:07:16,040 --> 00:07:22,160 applications our customers have. Sapbuild offers multiple tools 96 00:07:22,360 --> 00:07:27,200 as a services like Sapbuild code which comes with the generative 97 00:07:27,200 --> 00:07:31,800 AI capability to create the full stack applications, native 98 00:07:31,800 --> 00:07:36,400 mobile applications using the SAP Build code as a service. 99 00:07:36,880 --> 00:07:41,880 Then we also have Sapbuild Apps which is low code, low code 100 00:07:41,880 --> 00:07:46,960 capability to create the full stack and mobile applications in 101 00:07:46,960 --> 00:07:49,760 a short period of time. Within the build. 102 00:07:49,760 --> 00:07:52,760 We also offer the process automation capability to 103 00:07:52,760 --> 00:07:57,360 digitalize or automate manual repetitive rule based task 104 00:07:57,360 --> 00:08:01,360 workflows using the SAP build process automation capability. 105 00:08:01,960 --> 00:08:07,960 And we also offer to enhance the end user experience SAP build 106 00:08:07,960 --> 00:08:12,040 work zone for creating the collaboration workspaces as 107 00:08:12,160 --> 00:08:16,600 digital experience. So you see the SAP build has a 108 00:08:16,640 --> 00:08:22,040 lot many capabilities within a single tool set to realize many 109 00:08:22,040 --> 00:08:26,440 complex scenarios which comes around any of the LUB 110 00:08:26,480 --> 00:08:31,600 application be it finance, be it procurement, HR, etc. 111 00:08:32,559 --> 00:08:36,840 Awesome. What value does SAP build bring 112 00:08:36,840 --> 00:08:40,360 to line of business functions or let's say processes? 113 00:08:42,480 --> 00:08:47,520 So SAP Build brings multi fold of value to any line of business 114 00:08:47,520 --> 00:08:51,800 applications or functions or processes depending on where we 115 00:08:51,800 --> 00:08:56,280 are building those extensions, what we are digitalizing and how 116 00:08:56,280 --> 00:09:00,120 we are taking it up, right. So let me give some examples. 117 00:09:00,760 --> 00:09:04,800 Say for example, we are automating and building an 118 00:09:04,800 --> 00:09:08,360 extension to automate certain account receivable task in 119 00:09:08,360 --> 00:09:11,040 finance. Now when we automate or 120 00:09:11,040 --> 00:09:13,800 digitalize these processes surrounding the account 121 00:09:13,800 --> 00:09:18,480 receivable core process, what we bring in is the efficiency in 122 00:09:18,480 --> 00:09:22,040 the account receivable process, which means we shorten the time 123 00:09:22,040 --> 00:09:25,960 it takes to perform this account receivable task or the process, 124 00:09:26,400 --> 00:09:30,840 which means that customer have more cash in hand because we are 125 00:09:30,840 --> 00:09:34,000 squeezing in the account receivable process time frame, 126 00:09:34,280 --> 00:09:37,880 they receive more cash and now this cash they can deploy in 127 00:09:37,880 --> 00:09:39,840 enhancing and growing their business. 128 00:09:40,080 --> 00:09:44,320 Similarly, we can bring efficiency in any other line of 129 00:09:44,320 --> 00:09:48,600 business process as well, right, like be it HR for recruitment 130 00:09:48,600 --> 00:09:53,680 and onboarding, procurement for account payable, PR to PO 131 00:09:53,680 --> 00:09:59,920 process in supply chain, for example, in planning, in 132 00:10:00,520 --> 00:10:04,400 manufacturing processes, asset management, etc and the list 133 00:10:04,400 --> 00:10:06,760 goes on. So one first value which 134 00:10:06,760 --> 00:10:10,000 Sapbuild brings is the efficiency and directly 135 00:10:10,000 --> 00:10:13,880 impacting the business KPI associated with that business 136 00:10:13,880 --> 00:10:18,040 process of the line of business. The second value it brings in is 137 00:10:18,040 --> 00:10:20,160 the improvement in the data quality. 138 00:10:20,240 --> 00:10:24,800 So whenever we automate or digitalize the processes or 139 00:10:24,800 --> 00:10:29,000 functions as an extension, we are improvising the quality of 140 00:10:29,000 --> 00:10:31,240 data getting into the business application. 141 00:10:31,600 --> 00:10:35,720 That is a direct impact where we reduce the manual errors or 142 00:10:35,720 --> 00:10:39,280 rework required when we digitalize the processes, 143 00:10:39,280 --> 00:10:42,080 extensions, etc. Using the SAP build. 144 00:10:42,320 --> 00:10:46,400 The data quality improvement has a direct impact on the insight 145 00:10:46,400 --> 00:10:50,720 or AI which businesses generate using that data, right. 146 00:10:50,720 --> 00:10:53,960 So better quality of data as an input using the SAP Build, 147 00:10:54,360 --> 00:10:59,240 better output they get when they generate or utilize it for AI or 148 00:10:59,240 --> 00:11:02,600 for analytics. The third value which SAP Build 149 00:11:02,600 --> 00:11:06,760 brings is the experience itself, whether it's internal like 150 00:11:06,760 --> 00:11:11,000 employees or external like say retailers, distributors, 151 00:11:11,000 --> 00:11:15,560 partners, supplier with say new experiences which we create or 152 00:11:15,560 --> 00:11:18,280 digital experiences which we create, they get a better 153 00:11:18,280 --> 00:11:21,400 experience and hence the better satisfaction. 154 00:11:21,400 --> 00:11:23,560 So that's the third value which we bring. 155 00:11:24,160 --> 00:11:27,760 On top of it, there are more values which SAP Build provides, 156 00:11:27,760 --> 00:11:29,960 right? Say for example, if you use SAP 157 00:11:29,960 --> 00:11:34,840 Build for clean core surrounding the SAPS Purhana, then it helps 158 00:11:34,960 --> 00:11:38,920 ensuring that you reduce your maintenance or upgrade efforts 159 00:11:38,920 --> 00:11:44,080 surrounding SAP S Purhana cloud. You improve your upgrade time, 160 00:11:44,120 --> 00:11:46,200 etc. So reduce the total cost of 161 00:11:46,200 --> 00:11:49,600 operations when you use SAP Build for your side by side 162 00:11:49,600 --> 00:11:52,440 extensibility surrounding SAP S Purhana. 163 00:11:53,200 --> 00:11:57,280 Further, SAP build offers lot of prebuilt content which can help 164 00:11:57,280 --> 00:12:00,440 you as an accelerator. You can leverage these prebuilt 165 00:12:00,440 --> 00:12:03,000 content or templates to quickly get started. 166 00:12:03,200 --> 00:12:06,720 Deploy your application Oregon processes as is and you 167 00:12:06,800 --> 00:12:09,000 accelerate a complete time frame, right. 168 00:12:09,000 --> 00:12:13,600 So multi fold value which SAP build brings to various lines of 169 00:12:13,600 --> 00:12:17,280 business depending on their use case, their scenario where they 170 00:12:17,280 --> 00:12:20,240 are consuming SAP build or utilizing SAP build. 171 00:12:21,400 --> 00:12:23,720 Very well put him and then thanks for touching on that 172 00:12:23,720 --> 00:12:26,320 clean core topic and prebuilt content. 173 00:12:26,920 --> 00:12:30,440 There you go, listeners. With SAP Build, everyone can do 174 00:12:30,440 --> 00:12:33,840 application development, intelligently automate processes 175 00:12:34,360 --> 00:12:36,680 and design engaging digital workspaces. 176 00:12:37,960 --> 00:12:41,560 You mentioned about line of businesses Heman, so let's deep 177 00:12:41,560 --> 00:12:45,200 dive a bit on that. How do customers and partners 178 00:12:45,280 --> 00:12:49,040 set up SAP Build to use alongside their LOB 179 00:12:49,200 --> 00:12:51,280 applications? If you can put some light on 180 00:12:51,280 --> 00:12:55,160 that. Sure, here the way they can 181 00:12:55,160 --> 00:13:00,360 utilize SAP Builder set it up. One is the technical setup of 182 00:13:00,360 --> 00:13:02,440 SAP build is very straightforward. 183 00:13:02,480 --> 00:13:05,040 We do have lot of boosters available. 184 00:13:05,040 --> 00:13:09,000 So whenever a customer or partner logs into the SAP BTP 185 00:13:09,000 --> 00:13:13,000 cockpit, if they have right entitlements and they can go and 186 00:13:13,000 --> 00:13:16,560 check in the BTP cockpit about their existing entitlements, 187 00:13:16,920 --> 00:13:21,400 they just need to start these boosters and in a one click they 188 00:13:21,400 --> 00:13:23,920 can activate respective services. 189 00:13:24,160 --> 00:13:28,560 They can set up for example SAP Build Code or SAP Build Apps 190 00:13:28,560 --> 00:13:30,920 etc. By just clicking on the boosters 191 00:13:30,920 --> 00:13:34,560 and this will help set up the services which they can start 192 00:13:34,560 --> 00:13:38,080 utilizing or start building their application extension 193 00:13:38,080 --> 00:13:42,160 processes, workspaces, ETC. So that's more on a technical 194 00:13:42,160 --> 00:13:46,840 setup how you leverage SAP BTP cockpit and the booster to set 195 00:13:46,840 --> 00:13:49,640 this up. But when we look more on the 196 00:13:49,720 --> 00:13:54,280 integration side of the SAP build as well, there are various 197 00:13:54,280 --> 00:13:58,200 ways how they can integrate with LOB application. 198 00:13:58,200 --> 00:14:02,000 And for that, I think the right way of looking into it is that 199 00:14:02,240 --> 00:14:06,200 what problem they would like to solve around the LOB application 200 00:14:06,200 --> 00:14:09,240 that are surrounding the LOB application then can be many 201 00:14:09,240 --> 00:14:14,680 processes, many task, many I'll say requirement which they would 202 00:14:14,680 --> 00:14:19,000 like to digitalize. And does SAP build integrate 203 00:14:19,000 --> 00:14:22,280 with different business applications such as let's say 204 00:14:22,520 --> 00:14:26,760 SAP's for HANA Cloud, SAP SuccessFactors or SAP IBP and 205 00:14:26,760 --> 00:14:29,640 other solutions? Yes, that's a really good 206 00:14:29,640 --> 00:14:31,480 question. And if we look at this 207 00:14:31,520 --> 00:14:36,080 integration alongside LOB application, there are various 208 00:14:36,080 --> 00:14:40,080 ways we can integrate. Let me little go deep dive 209 00:14:40,080 --> 00:14:42,760 solution wise that how we can integrate. 210 00:14:43,160 --> 00:14:46,640 Let's say we are building an app extension using SAP build code, 211 00:14:46,640 --> 00:14:49,520 which is more pro code tool set there. 212 00:14:49,520 --> 00:14:53,800 In SAP Build Code, we have access to where we can connect 213 00:14:53,800 --> 00:14:58,360 with the API's of any LOB application, be it success 214 00:14:58,360 --> 00:15:03,040 factor, be it Sap's, Purana Cloud or Digital supply chain, 215 00:15:03,040 --> 00:15:06,480 etc. And then directly consume these 216 00:15:06,520 --> 00:15:10,400 API's or services either directly or through the business 217 00:15:10,400 --> 00:15:13,120 accelerator, hub etc within the build code. 218 00:15:13,120 --> 00:15:17,200 So that's one way of looking at the integration in the build 219 00:15:17,200 --> 00:15:18,800 code. But that's not all. 220 00:15:19,160 --> 00:15:22,360 We can also integrate via the events. 221 00:15:22,360 --> 00:15:26,080 So we can directly consume say for example within build code 222 00:15:26,080 --> 00:15:29,320 while creating the back end services or back end logic for 223 00:15:29,320 --> 00:15:31,800 the application which we are building. 224 00:15:32,120 --> 00:15:36,080 We can consume the events coming from different applications like 225 00:15:36,080 --> 00:15:41,040 say SAP, Sponhana Cloud. So there are various mechanism 226 00:15:41,040 --> 00:15:46,080 how then build code can consume or integrate or talk with these 227 00:15:46,680 --> 00:15:51,480 LUB applications utilizing these different methods which are 228 00:15:52,160 --> 00:15:55,000 possible using the SAP build code. 229 00:15:55,480 --> 00:15:58,600 Moving on, if we look at say for example SAP build process 230 00:15:58,600 --> 00:16:02,000 automation, if someone is trying to create a process as an 231 00:16:02,000 --> 00:16:06,600 extension to any of the LOB application or even cross system 232 00:16:06,600 --> 00:16:10,160 orchestration of data or workflow using build process 233 00:16:10,160 --> 00:16:15,200 automation, they can consume again the APIs using the actions 234 00:16:15,200 --> 00:16:18,120 functionality. So SAP Build also offers a 235 00:16:18,120 --> 00:16:22,680 powerful capability where customers partners create set of 236 00:16:22,680 --> 00:16:26,600 actions one time to perform the CRUD operation, create, read, 237 00:16:26,600 --> 00:16:30,320 update, delete operation across any of the LOB applications. 238 00:16:30,600 --> 00:16:33,840 And this is very simple. The source of the API can be 239 00:16:33,840 --> 00:16:37,600 business accelerator Hub, can be their custom specification, can 240 00:16:37,600 --> 00:16:40,080 be a ABAP, Restful programming, etc. 241 00:16:40,200 --> 00:16:42,600 And that's not all. They can also consume say for 242 00:16:42,600 --> 00:16:46,960 example SAP as Purhana Private Cloud, they can consume Bapis 243 00:16:46,960 --> 00:16:49,480 and RFCS etcetera as well as an action. 244 00:16:49,920 --> 00:16:54,000 And these actions then they can include in any SAP build 245 00:16:54,000 --> 00:16:58,120 process, automation process or SAP build apps as well to 246 00:16:58,120 --> 00:17:01,600 perform the CRUD operation. So that's one way of looking at 247 00:17:01,600 --> 00:17:04,560 it, how they can integrate with LOB application. 248 00:17:04,920 --> 00:17:07,960 Another way of looking at is again the events, right? 249 00:17:07,960 --> 00:17:10,720 So like with build process automation, it supports the 250 00:17:10,720 --> 00:17:14,720 event driven automation where you can trigger a process based 251 00:17:14,720 --> 00:17:17,800 on the event occurring in any of the LOB application. 252 00:17:17,839 --> 00:17:21,359 Let's take an example that an employee gets created in SAP 253 00:17:21,359 --> 00:17:25,200 success factor and on creation of employee, I want to trigger 254 00:17:25,200 --> 00:17:30,280 an extension process to automate say for example, given access to 255 00:17:30,280 --> 00:17:33,280 certain IT systems to this new employee, right. 256 00:17:33,280 --> 00:17:36,400 So that kind of integration is possible where build process 257 00:17:36,400 --> 00:17:39,360 automation can consume the events originating from 258 00:17:39,360 --> 00:17:42,720 different lines of business applications and then trigger 259 00:17:42,720 --> 00:17:45,640 the process. The third way of looking at it 260 00:17:45,640 --> 00:17:49,560 is from SAP Build process automation also because it has 261 00:17:49,560 --> 00:17:53,920 the RPA capability inbuilt robotic process automation. 262 00:17:54,240 --> 00:17:58,840 There we can also create UI or screen based automation. 263 00:17:59,360 --> 00:18:01,160 So that's third way of looking at it. 264 00:18:01,160 --> 00:18:05,000 Beyond the API's events that if I want to automate certain task 265 00:18:05,400 --> 00:18:08,760 on any specific Adobe application, whether it's a web 266 00:18:08,760 --> 00:18:11,720 application or a Java based application doesn't matter. 267 00:18:12,040 --> 00:18:16,640 You can then utilize the RPA screen recorder capability to 268 00:18:16,640 --> 00:18:21,480 create the screen recording or a UI automation and then automate 269 00:18:21,480 --> 00:18:25,000 that repetitive task surrounding that core application. 270 00:18:25,440 --> 00:18:30,440 So SAP Build offers various ways to integrate with the line of 271 00:18:30,440 --> 00:18:35,000 business applications as we saw in some of the examples right 272 00:18:35,000 --> 00:18:37,480 here. Thanks for that insight him. 273 00:18:37,480 --> 00:18:40,400 And then tying it to a real business use case, it was 274 00:18:40,400 --> 00:18:44,600 something new to me. You touched upon extension APIs 275 00:18:44,600 --> 00:18:48,800 and events and you would agree with me that a good application 276 00:18:48,800 --> 00:18:52,120 and extension development has some principles, right? 277 00:18:52,360 --> 00:18:57,200 So how does a customer or a partner identify when to use 278 00:18:57,280 --> 00:19:01,880 what from SAP build tool, for example, when to use Locode 279 00:19:01,880 --> 00:19:06,080 versus Procode app development, if you can also talk about that? 280 00:19:07,200 --> 00:19:09,640 Absolutely. I think that's very important as 281 00:19:09,640 --> 00:19:14,440 well for any architect or for the development team to follow 282 00:19:14,440 --> 00:19:17,560 the set of principles when it comes to the application 283 00:19:17,560 --> 00:19:20,440 development. And what we have done at the BTP 284 00:19:20,440 --> 00:19:24,160 level, we have created a complete BTP guidance framework 285 00:19:24,320 --> 00:19:28,480 which is available, which can be utilized to look at the 286 00:19:28,480 --> 00:19:32,760 reference architecture, which also gives the complete detailed 287 00:19:32,760 --> 00:19:37,040 guidance when to use what. So for example, if you want to 288 00:19:37,040 --> 00:19:41,760 create a Fiori extension for the UI on top of your SAPS Fulhana, 289 00:19:41,760 --> 00:19:43,680 then you go with the SAP build code. 290 00:19:43,720 --> 00:19:47,040 There's a technology, if you are creating a lightweight 291 00:19:47,040 --> 00:19:50,440 application for a simple extension, it may suggest that 292 00:19:50,440 --> 00:19:53,680 you go with a low code capability because then you just 293 00:19:53,680 --> 00:19:57,600 simply drag and drop and create a nice looking application in 294 00:19:57,600 --> 00:20:01,400 your branding and then ship it out in a short period of time. 295 00:20:01,680 --> 00:20:04,560 So depending on the use case, depending on the requirement, 296 00:20:04,560 --> 00:20:09,400 this DTP guidance framework will help customers and partners to 297 00:20:09,440 --> 00:20:12,640 decide when to use what and how to use it, right. 298 00:20:12,640 --> 00:20:16,440 So it's I think. Go to solutioning guide with lot 299 00:20:16,440 --> 00:20:20,680 of reference architecture examples etc which can give them 300 00:20:20,680 --> 00:20:23,080 the right guidance. Awesome. 301 00:20:23,480 --> 00:20:26,840 That would have really resonated with our listeners out there and 302 00:20:26,840 --> 00:20:29,120 we will link to the framework in our show notes. 303 00:20:29,120 --> 00:20:31,160 So feel free to check that out as well. 304 00:20:31,720 --> 00:20:35,480 My next question would be Hemant, can SAP build be used 305 00:20:35,520 --> 00:20:39,240 along or let's say around non SAP business applications? 306 00:20:39,920 --> 00:20:42,760 Yes, absolutely. I think many customers are 307 00:20:42,760 --> 00:20:47,360 already utilizing SAP built to automate, orchestrate or 308 00:20:47,360 --> 00:20:51,120 digitalize the processes across SAP and non SAP application. 309 00:20:51,760 --> 00:20:54,840 As I touched upon some of the integration mechanism and these 310 00:20:54,840 --> 00:20:58,440 integration mechanism are completely open which means that 311 00:20:58,560 --> 00:21:04,240 while I am using say for example an RPA to automate a UI or ASAP 312 00:21:04,280 --> 00:21:08,520 GUI, I can also use it for any other non SAP web application 313 00:21:08,600 --> 00:21:12,520 the same recorder. If I want to use for example 314 00:21:12,520 --> 00:21:16,480 actions in SAP build apps, then I can use those actions 315 00:21:16,640 --> 00:21:19,560 essentially coming from non SAP application. 316 00:21:19,560 --> 00:21:23,960 Also in SAP build apps, it's very easy to consume and 317 00:21:23,960 --> 00:21:28,640 automate or create extension on top of non SAP applications as 318 00:21:28,640 --> 00:21:32,800 well using SAP build. Of course, when it comes to 319 00:21:32,800 --> 00:21:38,440 automating SAP workload or extensions on top of SAP, we do 320 00:21:38,440 --> 00:21:41,640 have some technical differentiations or advantage, 321 00:21:41,640 --> 00:21:43,920 native advantage. Awesome. 322 00:21:44,760 --> 00:21:47,400 Let's zoom in on that technical differentiation that you 323 00:21:47,400 --> 00:21:51,080 mentioned for SAP build. And if we zoom in, can you 324 00:21:51,080 --> 00:21:53,760 please elaborate on that? Absolutely. 325 00:21:54,360 --> 00:21:58,360 When it comes to like utilizing SAP build, surrounding SAP 326 00:21:58,360 --> 00:22:01,880 business application or line of business application, there are 327 00:22:01,880 --> 00:22:05,440 some native connectors or integrations which are 328 00:22:05,440 --> 00:22:07,600 available. Yeah, let me explain it with 329 00:22:07,600 --> 00:22:11,200 some example. Let's say we are utilizing SAP 330 00:22:11,200 --> 00:22:16,120 build code for creating the app extension or UI extension. 331 00:22:16,720 --> 00:22:20,040 Now here when we are creating a business, service etc. 332 00:22:20,040 --> 00:22:24,320 As I mentioned, you can directly consume say events originating 333 00:22:24,320 --> 00:22:26,200 from SAP application. Right? 334 00:22:26,520 --> 00:22:30,560 You can directly connect with SAP system, let's say SAP as per 335 00:22:30,560 --> 00:22:34,840 HANA for utilizing those custom objects or accessing those 336 00:22:34,840 --> 00:22:37,640 custom objects which you might have created on a web cloud. 337 00:22:38,400 --> 00:22:40,920 This kind of a native integration is available when 338 00:22:40,920 --> 00:22:44,920 you leverage SAP build code, which no one else or no other 339 00:22:44,920 --> 00:22:47,600 tool can offer, right? So that's the technical 340 00:22:47,600 --> 00:22:51,040 differentiator and advantage when you utilize SAP build code, 341 00:22:51,040 --> 00:22:53,920 for example, surrounding the SAP application. 342 00:22:54,920 --> 00:22:58,920 If we move on like in SAP build process automation for example, 343 00:22:58,920 --> 00:23:03,400 while we do have certain native connectors for automating SAP 344 00:23:03,400 --> 00:23:08,600 success factor, SAP Arriba, SAP GUI, SAP Fiori etcetera, right. 345 00:23:08,760 --> 00:23:11,680 These connectors give an advantage where you create 346 00:23:11,680 --> 00:23:15,800 robust and scalable automations which again is the best in the 347 00:23:15,800 --> 00:23:19,560 market. You create very stable long 348 00:23:19,560 --> 00:23:22,760 running automation. So you reduce the manual efforts 349 00:23:22,760 --> 00:23:26,480 or the maintenance efforts on such process automations which 350 00:23:26,480 --> 00:23:29,520 you create using SAP build process automation. 351 00:23:29,520 --> 00:23:32,640 So these are some examples that how these technical 352 00:23:32,640 --> 00:23:37,600 differentiator can give you a lot of advantage and benefit in 353 00:23:37,600 --> 00:23:41,360 terms of the operations while utilizing the SAP build 354 00:23:41,360 --> 00:23:43,520 surrounding the SAP applications. 355 00:23:44,760 --> 00:23:46,960 Awesome. Thank you Eamon for beautifully 356 00:23:46,960 --> 00:23:50,600 articulating it. When creating and let's say 357 00:23:50,960 --> 00:23:55,040 deploying applications on hyperscaler, how does this piece 358 00:23:55,040 --> 00:23:58,800 of identity and access management handle with SAP 359 00:23:58,800 --> 00:24:02,480 build? I think all these SAP build is 360 00:24:02,480 --> 00:24:07,080 running on the SAP Business Technology platform and that's 361 00:24:07,080 --> 00:24:11,160 where it leverages the Identity authentication services or IAS 362 00:24:11,160 --> 00:24:14,440 service of the BTP. So let's say you are creating an 363 00:24:14,440 --> 00:24:18,280 app using build apps in a low code manner and you want to 364 00:24:18,280 --> 00:24:22,040 ensure the security. So you just on a click while 365 00:24:22,040 --> 00:24:24,960 you're designing the application, enable the BTP 366 00:24:24,960 --> 00:24:28,480 authentication. And here your application is 367 00:24:28,480 --> 00:24:31,760 completely secured and it's linked with your BTP identity 368 00:24:31,760 --> 00:24:34,760 authentication service, which you can leverage, right. 369 00:24:34,760 --> 00:24:39,720 So it utilizes BTPS securities and standard features and 370 00:24:39,720 --> 00:24:42,200 functionality to deliver this capability. 371 00:24:43,040 --> 00:24:45,520 Wonderful. So all those ISO requirements 372 00:24:45,520 --> 00:24:49,200 are already covered with the service over there human like 373 00:24:49,240 --> 00:24:53,320 infusing intelligence into apps and process development and 374 00:24:53,320 --> 00:24:57,360 making the tool do it for you is the ask in the market out there. 375 00:24:57,960 --> 00:25:00,600 So how does ACP build enable that? 376 00:25:01,480 --> 00:25:04,000 Really good question and I'll divide this question into 377 00:25:04,000 --> 00:25:09,680 two-part 1, is that where we provide the AI capability or 378 00:25:10,120 --> 00:25:12,880 some of the Gen. AI capability within the SAP 379 00:25:12,880 --> 00:25:16,880 built to improve the productivity of the designers, 380 00:25:16,880 --> 00:25:20,520 developers and different personas who are using the 381 00:25:20,640 --> 00:25:24,680 technology itself for creating these applications extensions 382 00:25:24,680 --> 00:25:28,480 for their line of business. And the second is that when you 383 00:25:28,480 --> 00:25:32,560 create these applications, extensions, etc, how do you 384 00:25:32,560 --> 00:25:37,720 infuse the latest AI capability within these applications, 385 00:25:37,720 --> 00:25:39,240 extensions, etc. Right. 386 00:25:39,240 --> 00:25:42,560 So these are two parts to it. So let me answer first. 387 00:25:43,120 --> 00:25:46,480 When you're looking at improving the productivity for creating 388 00:25:46,480 --> 00:25:48,920 these application extensions etc. 389 00:25:49,400 --> 00:25:53,800 We have already started rolling out the Genii capability with 390 00:25:53,800 --> 00:25:58,360 SAP Copilot called Joule. So Joule is already available 391 00:25:58,400 --> 00:26:02,600 within SAP build code for example, to create application, 392 00:26:02,600 --> 00:26:06,440 to create the test data, to test the application etc, right. 393 00:26:06,440 --> 00:26:10,280 So it already helps professional developers to increase their 394 00:26:10,280 --> 00:26:14,520 efficiency with this Genii based capability to generate the code. 395 00:26:14,720 --> 00:26:18,120 So that already is released as part of our road map. 396 00:26:18,120 --> 00:26:21,800 We are also bringing in this dual capability within the build 397 00:26:21,800 --> 00:26:25,160 process automation and build apps coming to the digital 398 00:26:25,160 --> 00:26:28,920 workspaces as well. We also release dual for SAP 399 00:26:29,280 --> 00:26:33,320 start and SAP build work zone standard edition. 400 00:26:33,680 --> 00:26:38,280 Now here again when end users are using say for example build 401 00:26:38,280 --> 00:26:41,640 work zone as a central entry point for multiple application 402 00:26:41,640 --> 00:26:46,000 as a digital workspace, then they can ask dual any query for 403 00:26:46,000 --> 00:26:49,960 navigation across say different applications or any transactions 404 00:26:49,960 --> 00:26:53,880 related data as per the underlying application which has 405 00:26:53,920 --> 00:26:58,120 enabled those use cases, right. So these are already available 406 00:26:58,120 --> 00:27:01,280 and these are more from a productivity aspect where you 407 00:27:01,280 --> 00:27:04,680 utilize the tool. Now coming to the second part of 408 00:27:04,680 --> 00:27:09,360 the question, which is more infusing that how I can make the 409 00:27:09,560 --> 00:27:15,040 extensions or applications which I'm creating using SAP build 410 00:27:15,640 --> 00:27:19,240 intelligent, right. So here comes a question that I 411 00:27:19,360 --> 00:27:24,160 want to infuse the AIML capability within applications, 412 00:27:24,160 --> 00:27:28,960 processes, workspaces, etcetera. Now this can be easily done. 413 00:27:29,080 --> 00:27:31,640 So there are two or three ways to do it. 414 00:27:31,640 --> 00:27:36,080 One is of course you can leverage the SAP Business AI 415 00:27:36,200 --> 00:27:40,440 standard services, right? Let's say Document Information 416 00:27:40,440 --> 00:27:42,840 Extraction Premium Edition which is a Gen. 417 00:27:42,840 --> 00:27:46,320 AI based OCR capability to extract data from scanned 418 00:27:46,320 --> 00:27:50,640 images, scanned documents across multiple languages. 419 00:27:50,640 --> 00:27:54,280 Now this service is already available on SAP BTP. 420 00:27:54,400 --> 00:27:57,920 All you have to do is enable that service, call that endpoint 421 00:27:57,960 --> 00:28:01,600 as an action within your SAP build application Oregon 422 00:28:01,600 --> 00:28:04,680 process, whichever you are creating and here you go. 423 00:28:04,680 --> 00:28:08,880 You have already infused the OCR kind of a capability within your 424 00:28:08,880 --> 00:28:10,880 application or within your process. 425 00:28:11,120 --> 00:28:16,600 That's one way of looking at it. Again, SAP BTP offers lot of 426 00:28:16,600 --> 00:28:20,600 capability to create the AIML models, right. 427 00:28:20,600 --> 00:28:24,520 So where we have this SAP BTP, AI Core and AI Hub where 428 00:28:24,520 --> 00:28:27,800 customers can leverage this technology to create their 429 00:28:27,800 --> 00:28:33,200 narrow AI use cases or create say RAG kind of a model. 430 00:28:33,680 --> 00:28:37,480 Once they publish this as an endpoint using Sapbtpai 431 00:28:37,480 --> 00:28:41,520 capability, these endpoints again can be consumed in the 432 00:28:41,520 --> 00:28:46,640 application as an action to infuse that AI capability within 433 00:28:46,640 --> 00:28:49,960 the application or extension which they have created using 434 00:28:49,960 --> 00:28:53,560 SAP Build. So multiple ways again use the 435 00:28:53,560 --> 00:28:58,480 ready to use services of SAP Business AI or use the SAP BTP 436 00:28:58,480 --> 00:29:03,040 AI capability to create your custom AIML model and expose it 437 00:29:03,040 --> 00:29:07,320 as an endpoint and then consume it within the application which 438 00:29:07,320 --> 00:29:11,000 you are creating using SAP Build or a process extension whatever 439 00:29:11,000 --> 00:29:13,120 it may be. Awesome. 440 00:29:14,000 --> 00:29:17,960 Thanks again Hemant for that. Mobile is also the way of 441 00:29:17,960 --> 00:29:21,640 working and you also touched upon SAP Start and mobile. 442 00:29:22,480 --> 00:29:27,400 Are apps developed using SAP Build Android and iOS compatible 443 00:29:27,400 --> 00:29:29,920 as well? Yes, absolutely. 444 00:29:30,280 --> 00:29:34,560 In fact, what we offer as part of the build code is also the 445 00:29:34,560 --> 00:29:38,960 complete mobile services or mobile capability where 446 00:29:39,120 --> 00:29:44,240 customers, partners can create native iOS and native Android 447 00:29:44,240 --> 00:29:47,120 apps. What they can also do is utilize 448 00:29:47,120 --> 00:29:49,080 this dual capability to create it. 449 00:29:49,520 --> 00:29:53,560 So it's very easy now for them to create mobile applications 450 00:29:53,560 --> 00:29:56,720 which are native to a specific OS. 451 00:29:57,000 --> 00:30:01,720 Similarly, in build apps also, we support the capability where 452 00:30:01,720 --> 00:30:05,800 they can create the native application using the build apps 453 00:30:05,800 --> 00:30:09,720 for iOS and Android and then publish it to the store as well. 454 00:30:10,880 --> 00:30:13,920 Awesome. This is great and I'm sure him 455 00:30:13,920 --> 00:30:18,240 and that with these inputs from you, our listeners must have 456 00:30:18,400 --> 00:30:22,160 definitely gained knowledge on how ACP build simplifies 457 00:30:22,240 --> 00:30:26,600 application creation, extension and automation with low code, 458 00:30:26,840 --> 00:30:29,240 pro code and generative AI tools. 459 00:30:29,880 --> 00:30:32,600 I would really like to thank you for taking out time from your 460 00:30:32,600 --> 00:30:35,560 schedule and getting along with our listeners. 461 00:30:36,480 --> 00:30:37,960 Thank you. Thanks Gaurav. 462 00:30:39,200 --> 00:30:42,120 I would also like to highlight to our listeners that if you 463 00:30:42,120 --> 00:30:45,280 have any further pressing questions around this, please 464 00:30:45,280 --> 00:30:48,920 refer the show notes there. We have given some links to help 465 00:30:48,920 --> 00:30:52,320 you get started such as the service catalog where you can 466 00:30:52,320 --> 00:30:56,080 check the pricing and end to end missions backed by success 467 00:30:56,080 --> 00:31:00,400 stories on SAP Discovery Center. You can also give us a shout out 468 00:31:00,440 --> 00:31:04,120 on our social media channels. Plus, you can also drop us an 469 00:31:04,120 --> 00:31:13,560 e-mail at platformtalks@sap.com for the third section. 470 00:31:13,560 --> 00:31:18,360 For today's episode, let's hear about some road map items for 471 00:31:18,360 --> 00:31:22,760 the SAPBTP services that will help your business run better 472 00:31:23,320 --> 00:31:26,480 with intelligence and sustainability at heart. 473 00:31:27,520 --> 00:31:31,600 From SAPAI Launchpad side of the house, there would be a new 474 00:31:31,600 --> 00:31:34,720 prompt registry for accelerated AI development. 475 00:31:35,440 --> 00:31:39,200 With this, you can connect to the central prompt repository 476 00:31:39,600 --> 00:31:43,760 within SAP AI Launchpad, which will include versioning of 477 00:31:43,760 --> 00:31:47,560 prompts, storing prompts to different AI models, and so on. 478 00:31:48,240 --> 00:31:52,120 This will significantly improve prompt discovery and reusability 479 00:31:52,440 --> 00:31:55,480 with a central location to manage and organize prompt 480 00:31:55,480 --> 00:31:59,680 templates, also enabling developers to leverage prebuilt 481 00:31:59,800 --> 00:32:03,120 high quality prompt templates for faster prototyping. 482 00:32:04,480 --> 00:32:08,880 On the SAP BTP ABAP environment. There are these cool innovation 483 00:32:08,880 --> 00:32:13,160 coming up such as ABAP AI Software development kit with 484 00:32:13,280 --> 00:32:17,240 intelligent scenario life cycle management enabling you to 485 00:32:17,240 --> 00:32:20,920 consume large language models in ABAP and ABAP developer 486 00:32:20,920 --> 00:32:25,600 capabilities in Jewel with some key features such as ABAP cloud 487 00:32:25,600 --> 00:32:29,720 generators in Jewel enabling you to create a transactional app 488 00:32:29,720 --> 00:32:35,520 from scratch, Jewel Copilot and many more from SAP AI Core. 489 00:32:35,520 --> 00:32:39,120 You will be able to make SAP AI Core available in the 490 00:32:39,120 --> 00:32:43,880 hyperscaler data centers of each customer's choice such as Google 491 00:32:43,880 --> 00:32:49,880 Cloud Platform in India, W Japan E Tokyo and Amazon Web Services 492 00:32:50,000 --> 00:32:54,040 in Brazil, Sao Paulo. There are more such items on the 493 00:32:54,040 --> 00:32:58,160 road map and all these items that we discussed are planned 494 00:32:58,160 --> 00:33:03,000 for Q 12025 release. Also very important point you 495 00:33:03,000 --> 00:33:05,960 should know that all forward-looking statements are 496 00:33:05,960 --> 00:33:10,120 subjected to various risks and uncertainties that could cause 497 00:33:10,160 --> 00:33:13,560 actual results to differ materially from expectations. 498 00:33:14,000 --> 00:33:17,080 You are advised not to place undue reliance on these 499 00:33:17,080 --> 00:33:21,440 forward-looking statements which speak only as of their dates and 500 00:33:21,440 --> 00:33:24,360 they should not be relied upon in making purchasing decisions. 501 00:33:25,000 --> 00:33:28,360 To know more about other road map items, please refer I Show 502 00:33:28,360 --> 00:33:32,200 notes. I also wanted to highlight that 503 00:33:32,200 --> 00:33:35,560 we are rolling out multiple learning and enablement 504 00:33:35,560 --> 00:33:40,960 opportunities with one goal and that is to help you and your 505 00:33:40,960 --> 00:33:46,080 businesses to be ready. And for that, we have SAPBTP 506 00:33:46,080 --> 00:33:52,400 Innobytes, SAPBTP Garage, both in virtual format and then also 507 00:33:52,400 --> 00:33:56,400 in person mode with Hands on Excellence Workshop program for 508 00:33:56,400 --> 00:34:00,600 partners, where we bring in content experts and their 509 00:34:00,600 --> 00:34:03,440 knowledge directly to you and in person. 510 00:34:04,360 --> 00:34:07,760 So please check Events tab in SAP Discovery Center to register 511 00:34:07,760 --> 00:34:10,239 yourself. Links are in the show notes. 512 00:34:14,159 --> 00:34:21,199 That concludes our first episode of the year 2025 and #115 of 513 00:34:21,199 --> 00:34:24,679 SAPBTP Talk. I would really like to thank you 514 00:34:24,679 --> 00:34:28,239 again for tuning in and staying till the very end. 515 00:34:29,239 --> 00:34:32,600 If you were listening to us for the first time and they were 516 00:34:32,600 --> 00:34:37,199 terms like document grounding, multi tenant apps, AI software 517 00:34:37,199 --> 00:34:41,840 development kit and so on that were not clear to you, please 518 00:34:41,840 --> 00:34:46,159 let us know on our social media channels or drop us an e-mail at 519 00:34:46,159 --> 00:34:51,679 platformtalks@sap.com so that we can help you understand them. 520 00:34:52,600 --> 00:34:56,760 Plus, we are always here's to your feedback, so let us know 521 00:34:56,800 --> 00:35:01,160 what you liked, what you didn't, and most importantly, what you 522 00:35:01,160 --> 00:35:05,440 wish for in the next podcast. Sharing is scaring. 523 00:35:06,160 --> 00:35:09,840 If you agree to that, please share the podcast with your tech 524 00:35:09,840 --> 00:35:12,960 friends and family. Don't forget to subscribe to the 525 00:35:12,960 --> 00:35:15,640 podcast, leave a rating and review. 526 00:35:16,520 --> 00:35:20,480 You can listen to this podcast on various mediums like Spotify, 527 00:35:20,760 --> 00:35:25,680 Apple Podcasts, to name a few. With that, I was your host, God 528 00:35:25,680 --> 00:35:31,200 of day AKG, reporting and recording from Bangalore, India. 529 00:35:31,960 --> 00:35:36,080 Talk to you in the next episode. Until then, keep listening, keep 530 00:35:36,080 --> 00:35:38,760 learning and keep growing. Cheers.