SAP Joule Full Course | ZaranTech

Hello everyone, welcome to Zarantech.

Did you know that nearly 80% of companies worldwide are now using or planning to use artificial intelligence to improve their business processes?

This shows how AI is no longer a future idea. It is already here, helping

idea. It is already here, helping businesses move faster and smarter.

Today, we will explore how this amazing tool can change the way you work. SAP

Juul is an AI powered digital assistant, also called a co-pilot, built into SAP.

It helps users by answering questions, guiding tasks, and turning complex data into clear insights. With Juul, you don't need deep technical skills to get quick, accurate results. Studies show

that companies using AI assistants like Juul make decisions 30% faster and see 40% higher user satisfaction as tasks become easier and smoother. This makes

SAP Juul a valuable skill to learn today. It is more than just a tool. It

today. It is more than just a tool. It

is a career advantage. As more

businesses adopt SAP AI features, professionals trained in Juul will stand out and gain stronger opportunities.

Learning it now ensures you are ready for the future. In this course, we will guide you step by step through its features, benefits, and use cases. By

the end, you will feel confident to use Juul in real business work. Let's dive

in.

>> Good morning. Good evening once again.

So hi I'm here just before starting the session you know this small disclaimer for you all. All right. So this is the agenda for uh like for the today's um

introductory day more for jaw. So SAP

who are new to SAP just one minute introduction for SAP. SAP is a German multinational as uh everyone knows that it's 1970 is being done and then from

there we got a lot of innovation happened on SAP's system from R3 to R4 or right now to whatever we seeing in the cloud space how it occupied and you know how it's delivering the global standard solutions for these industry

specific needs and you know requirements for different users and different sectors as well right so yeah Zo is the most advanced one in such a kit that

we're going to use that. Yeah. So coming

to import very importantly on the Zel job outlook. Yeah. It's the most most

job outlook. Yeah. It's the most most most trending in hot cake right now because yeah it's a recent one but yes on the because as old is moving into the

generative AI or business AI kind of things. Okay. So Jolie is also one such

things. Okay. So Jolie is also one such a baby which was actually been you know done in SAP. Okay. So you might look for now right now yeah there is a huge market coming out for that but as in

addition to that you might see roles right now as we are seeing right now the SAP consultant so you might get a new positions for AA specialist jaw a specialist job consultant jaw developer

the kind of things you get into the space now it's very demanding we are now learning this one so you might get into a huge demand raised yeah across the globe not only from your space yeah the globe so these are the latest latest

salary ts which we have been keeping the market for start you know like a median of $100 $1,000 to $180k you know in the US market is what we have been estimated of that is a salary trend for that yeah

and coming to zul sector yes it covering lot of sectors but basically the major sectors that are concentrating is these are the sectors very importantly finance banking the manufacturing digital

manufacturing you know entertainment sectors public sectors these are the ones health healthcare basically on the pharma sectors all they're looking for it where they need in immediate solution immediate answers you know like

immediate resolutions kind of things where they're looking for that without any delays on that. So these are the main sectors which are grouping and interesting on this particular part and there is a huge huge huge demand on you

know and sap zulu for that. Yeah. Yes I

have been telling that kind of lot of things on that but yes what is SAP zool and what we'll be understanding on this let's let's go into this one. Yeah this

is the course objectives before I start for that. So SAP zool so I'm just

for that. So SAP zool so I'm just looking for the screen for you just for a half a minute right so let's explore SAP zool today

like you know it's an SAP's a copilot that revolutionizes you know productivity by providing the intelligent business specific insights and you know the very importantly the

bold term the automation directly within your SAP cloud applications This is what SAP zoo does. So what is SAP zool? So as

I said already, this is the SAP's generative AI assistant. This is

completely designed to seamlessly integrate across your organization's SAP ecosystem. Okay. So what it does, it

ecosystem. Okay. So what it does, it will assist with your data analytics or data analysis. It will have our flow

data analysis. It will have our flow automation and it will generate the insights you know like most kind of chart like ops to you where you have all the NSL interface which is a natural

language interfaces will be there. So

that is what SAP zool is. So this is generally like you know emphasizing efficiency expert is there who called James Prescott Zuul after his name only

SAP named this one. So this is built specifically to empower the users and the decision makers also to work smarter and then you can leverage the secure

enterprise data in this manner. Okay. So

now when you go for u you know like you know what what is that we have to know about that what is the architectural thing that we have you know a lot of things comes into our mind right so

SAP's key feature architecture when I want to highlight you know like so this is completely a driven as I said end to end a driven so this is contextual assistance will be there so that is the

reason you have to put all the natural language things also into it and not only SAP any integrated cloud applications you want to make it you are welcome into it. So you can do that for

that. So this is completely NLP based

that. So this is completely NLP based for all the intuitive interactions because um uh it might take a lot of languages also it might ask it might give you the answers also the it is

innovating in such a way. So all your realtime data analysis and personalized recommendations can be easily done and crossunctional workflow supports will be there like for finance HR support chain

pharmas the procurement manufacturing.

So a lot of industries are covering in that. So wherein which you can get all

that. So wherein which you can get all these cross functional support for you and very importantly this is secured and compliant with all the data privacy. So

you might think that something I'm inputting will be data be gone somewhere else or it might be played with something else. No, it's completely

something else. No, it's completely secure and completely compliant with the GDPR and CCPA standards know where which all the data privacy standards are adhered into it. Yes. Now when we talk

about the jaw architecture so let me show you what is this jaw architecture what it contains.

Let me open my notepad. So here it is architecture I want to show you. So

Jules generally leverages the SAP's BP architecture basically. So you need SAP

architecture basically. So you need SAP BTP access for this. I'll let you know what actually it needs for you to you know like before you go for Joel's setup and all the things. So Joel

basically it leverages this BTP. It's a

it's a mother for it and not only that it use the SAP S4 HANA cloud as well.

Okay. So this is a completely multi-layered approach. So where I'm

multi-layered approach. So where I'm saying multi-layered means it will be having importantly flow four layers will be there in which you'll be having your first of all the data management layer

will be there.

This is the main layer which integrates your SAP and third party data. Okay. And

then you have your application layer.

So this layer you will use all your interfaces no code agent builders because we have Zulu studio is there. So

in which you will build lot of flows, automations, interfacings with all the no code agents will be there. that you

will be leveraging through this application layer and then you have your more important layer is data management layer.

So in this data management layer you integrate all the SAP and third party data and the final layer will be your

analytics layer. This is the A layer.

analytics layer. This is the A layer.

So in this layer you'll have all the real-time insights all your machine learning on LP all kind of this a things will comes and sit in this layer where in which interact with this. So this is

your top down approach which I have just told to you like this. So where in which you have this multi-layered setup in which it will uses to interact with your

based front end. Okay. So now to speak more on that you know like when you ask okay fine what are the core use cases I get you know like into this practical benefits I get you know when I go into

this zool for example if you take any cross department application I told cross department application the financial planning will be there so it will request revenue forecast realtime

KPI dashboards on behalf of you it's not separately you can do that so zulu can do it and help you for that for HR level if you want to query for top performers turnovers how many recruitments happened

this this month how many have to be done a kind of these kind of things you know zu will easily answer you don't need to depend upon someone else for that okay and zul can also schedule interviews can

also you know like follow up on that as well so let me tell you on that it is innovation is already there in that and the procurement level if you want to optimize the supply selections using real-time performance data so we can use

the procurement chart bots for the zool for the sales level also if you want to identify the customer trends no to get the product recommend recommendations where actually I'm getting defaulted where I can actually get into you can

you want to make some decision making on top of that for the sales and marketing zul can help you on that immediately it will also give you suggestions where you can improve it also so this is what in the cross departmental applications I'm

telling so let's come to business benefits so let me open this one one more time here so when you come to business benefits

basically let me go into this It will increases the user productivity up to 85 to 90% of productivity can be expanded on the SAP Z's business

benefits. The major thing as you know AI

benefits. The major thing as you know AI is replacing the humans right now as you everyone knows that but yes to run that that needs humans again that's a second story but yes it reduces the manual work

through automation so a lot of manual interactions can be reduced and zulu can take it as a head on top of that it will facilitate a lot of computation making also with all your instate and reliable

data so as I said it uses context awareness respecting your roles and responsibilities in data for example in the role if I ask I want to use this this data for a particular reserve it will not allow you because it's

compliant with SAP and S3 security standards you can also block the data that someone want to see the same it will also do in the same in the tool respective one so you cannot there will be no any data violations on top of that

okay so this is how generally this will work and not only that for example for abappers also like you know for the developers kind of thing also if want to do unit testing if want to understand what their code where their code was

actually being done for the build code level what is their code deficiencies you know it will jol will correct that and they will help you on that. So it it will speed up by 30 to 40%. It's not

that it's not completely what I want to say is like occupying a developer role but yes it will give suggestions it will give solutions it will give you the recommendations for you know betterment

of it than you think for days for example if a small buggies came if you want to see for one day or 1.5 days will quickly resolve it for you where the bugget it will help you on that in half a day or you know on a quarter day like

that so like this is how it will help you for efficiency and not only that for all the unit testing cases and all these things you don't need depend upon humans right now So for the appers who want to do that they will help you on that. So

this is such innovations are coming in the jaw studio. So so this is this is these are the total work. So it will understand your system provides responses you know you can have the

diverse unified user environments will be there and a lot of experience with the precise information. So what are the information that you're going to get it right? It will get a more precise thing

right? It will get a more precise thing for that. Okay. Now this is one such

for that. Okay. Now this is one such thing and compared to zool right now. So

you might be experiencing SAP zool versus lot of co-pilots and things that are coming in the other environments as well like if you guys know that you know like there is Microsoft copilot is there

there is a Google do is there so now we're comparing to these how can SAP zool can help you on that okay so let me give you a small comparison so you'll understand what SAP zul can actually

leverage you on this front so if you see here let me write a small comparison for everyone's understanding so if you can see a feature wise this comparison

let's say it is SAP Zul it's your Microsoft copilot and this will be a Google do it okay so the core focus if we can say

the core focus of SAP zul is all the enterprise processes. I can say entire

enterprise processes. I can say entire enterprise process.

Okay. But here in your Microsoft copilot, this is completely um for 365 dynamics. That's it.

dynamics. That's it.

Okay. And for Google D8, it is a complete can say it's a workplace kind of tool wherein which you can see all these Google cloud-based documents will be there. So it was only for your it's a

be there. So it was only for your it's a workplace kind of tool where it will help you only for the at the Google cloud level and the document

level. Okay. Not for the enterprise. It

level. Okay. Not for the enterprise. It

is very clear for you now. And then

coming to the native integration.

Okay. So why I'm saying is differences because people of different sectors will be there. They have to understand if

be there. They have to understand if there is any similar tools that are already working in the industry right now. So what can it does from SAP so you

now. So what can it does from SAP so you have to understand it. So that is the reason I'm opening this bracket for you so that you can walk easily for your customers as well whenever you want to understand on that. Okay. So the native

integration here is it is completely SAP ecosystem where it has all S4 the success factors know the okay and all the other things that has in SAP and it

will support all the non SAP asset as well. So now here it will be only being

well. So now here it will be only being taken for your MS apps, Microsoft apps.

Okay. Plus whatever the Azour cloud is there that will be taken by this here as you know this will be only for Google apps and then Vert.x AI is there which is one such thing this Google D is doing

right away for the native integration.

Okay. So in the data context SAP zool has strong enterprise specific context will be there. So whatever you are dealing with

there. So whatever you are dealing with there will be strong data foundations will be there in this.

Okay. Whereas in Microsoft copilot this is completely semicontextual. It is

based on your recent actions.

So it will not it not be a complete set of data foundations will be there whatever you are going to ask for the Microsoft copilot. Okay. And Google Date

Microsoft copilot. Okay. And Google Date it's completely limited business process awareness. So I can say send me business

awareness. So I can say send me business process awareness.

So you won't get complete replies from what you're going to ask for the Google data. Okay. And yes coming to the custom

data. Okay. And yes coming to the custom models because yes we we might want to see more into it because yes you have to do lot of not only standard you want a lot of customization on top of this as

well but yes here in SAP zool you have leveragement of that. So you can use SAP trained models plus partner LLMs as well and you can custom your models as well

as per your need. It's more specialized for enterprise process. Okay, because

the others are just their broader productivity tools but here it's an end toend enterprise process tool. That is

what enterprise looks generally for. So

I can say this is for your SAP trained plus LLMs. Both models are partner LLMs or enterain. So you can easily train

or enterain. So you can easily train your models what you're going for that in the AI space. Okay. This is

completely as you know it's a RGBT is there. It's a open AI. Okay. And you

there. It's a open AI. Okay. And you

know Google Germany also this is a PM tool. PM palm tool tool is there. Okay.

tool. PM palm tool tool is there. Okay.

So this one okay this is nothing but which will help you on that. So this is the total order scope of differences I want to enlighten you because this is you have to understand what ZU generally

does with compared to the others one.

Okay. Because end of the day when you are working with zulu so you have to understand that is it's completely natural language interface it has the embedded recommendations where you can deal with all your suspenders kind of

thing you can do a conversational interface to interact with SAP apps basically wherever automating automation is there the auto it will automate your repetitive task like for example if you

want to do invoice matching anomaly detections no or you want to make a uh month end activities periodic weekend activities or you know generating the HR dashboards a repetitive kind of things

also it will automatize and it will saves you time for that. So the end point you have to understand it is not to replace manual efforts but yes it is manual workforce it is to replace the

repetitive manual work that is going to happen and taking time. So that is what the prime intention and prime focus where SAP or any other AI is now doing with okay and very importantly

contextual awareness is one of the important thing. So this understands the

important thing. So this understands the company specific vocabulary also because some company to some company's vocabulary will change. So that is also there in the system. It will understand the company's vocabulary it will respond

to that as well. Okay. Now yes coming to the configuration level. So what

actually needs for me to work on this?

What actually I have to to be in to work with the job. So if you come here let me explain this one.

So these are your it will run on the SAP BTP as I said this is running on SAP BTP platform. Okay. So people should know

platform. Okay. So people should know BTP. Okay. So this uses a core

BTP. Okay. So this uses a core a launchpads.

Okay. Business context APIs.

Okay. And this is integrated with data spear which you are seeing right now.

The data intelligence cloud S4 HANA cloud these are the primary interfaces within they have other interface like success factors Aribba and whatever you are looking for that.

So those are also there in that but yes this is the prime focus in which this will be built on top of that. Okay. The

moment when you want to build a data application with Jaw, okay, or the moment when you want to use a Jaw to automate business workflow, first thing you have to use, you have to go for Joel

Studio. So this is how it looks like.

Studio. So this is how it looks like.

Yeah. So

Joel Studio where in which you can go for an application or an automated process or a business suit or a job skill whatever you want to take it out.

So if you want to build application so based on that it's all a navigational wizard kind of thing you have to just port it. If you want to build automated

port it. If you want to build automated process you can simply build this is a studio where you can do everything on top of that. Okay this is a suit where you can customize any applications or any code based things that you want to

make it you can do it from here. Okay

this generally looks like this if you can see in the screen. So this is a kind of studio where you can just you know generally act just drag and drop nothing to do just you have to know what your process should be. You have to drag and

drop all those features. It'll put it.

For example, if you can see in the right side, I have dragged and drop a certain based thing. So I created a service now

based thing. So I created a service now ticket. When I create a ticket, it will

ticket. When I create a ticket, it will put the URL and that's it. The moment

when you create this, you will see this screen the jaw screen where it will gives you a pilot for that a co-pilot for that where it will gives you and it will activates for you a small kind of service now tool where you will ask ticket. It will give you the status of

ticket. It will give you the status of the ticket. Okay, small thing I'm just

the ticket. Okay, small thing I'm just showing you demonstrating for that. So

this will again show you a details like that. So the moment when you go for that

that. So the moment when you go for that it will show you what ticket it has been generated what is the severity what is the ticket about. So all these things it will be done. So it's all automation in general if you want to do this you have

to depend on some tool you put some Excel do that you know collaborate it with some other people add details in the Excel again you track it lot of things you have to manually work on that at least two people will be involved in

it. So this is all end to end completely

it. So this is all end to end completely taken by SAP zool in in this scenarios.

Okay. So like this you can use the studio but the studio is not free trial right now is not there only the small instance is there in SAP BP okay this is completely whenever you want to use the

zool you should have the zoo license for that first of all so you have to create a SAP data application also if you want to build it you need to create a project you need complete zoo license for that

so without that because that license you have to integrate in the BTP then only the zool studio or other things will start working for you okay in the free trial SAP is providing but it is still

not active that's what I want to comment on that okay so yeah from this studio you can create lot of thing so there is build code build apps build workflows lot of things are there from SCP BTP you

can leverage that in the zool studio segment and you can create the agents and you can make your work easy for that so this is this is what complete thing about the zulu so if you can see this these are the things which you can get

the use cases on the process automation or either customer support maintenance or analytics and sides You can see that I just explained you a couple of things also on that which car this SAP is tool.

So there are a lot of things that you need to understand as part of the curriculum and everything. I just

explained you but yes the prerequisites will be whenever you want to install your zool you should have a zool license your SAP landscape should be a supported landscape for S4 HANA because you have

to confirm your solutions in running in a supported region and data center.

Okay. So that is one of the important thing and all your BTP you need your admins from your SAP BP global account not the trial or local accounts. So you

should be able to get admin permissions for your BP global account cloud editing and SAP line of business support. If you

see here in the practical part you can see this is my SAP trial account. See in

the trial account I cannot see if it is a see I using generally this is where the entitlement I can do it for the tool. This is a global account only but

tool. This is a global account only but still I don't have it because the license is not impacted in it. So you

should have a license for this to get into it. People who want to do SAP BP

into it. People who want to do SAP BP trail they can do but zu cannot be directly do into it. So this is where you have to enter you have to activate in your mobile account from your admin and then the license has to be incorporated then the jewels today can

be incorporated for you and you can start using that as well. So there is a integration for that where your admin only will do I think so you cannot do with the trial account that one where in which the cloud services as

authentication is there where you will register for the cloud product for your cloud or success factors and then it will confirm your attribute mapping for that and then you can run your zool

booster on top of that okay this is how generally will run in the segment okay the trial was about to come for us for zul I'm not sure it was really not available but SAP is forums are telling

that is available But yes, you have to do it through SAP build only. People who want to can try

build only. People who want to can try it. They can register SAP trial account

it. They can register SAP trial account and they can enable the build which includes studio also within the BTP trial cockpit. Okay. Once that is

trial cockpit. Okay. Once that is activated, you can use your jewel features as well including your custom agents or you know automation whatever you want in the trial account. But yes,

this also needs some of your admin help also for that. So you can take for that if that is really available on the global accounts perspective. Okay. So

that's about the zool for now. Today I'm

open to questions. Yeah, before

questions I just want to say like you know this is the course content on the SAP zool. So we'll be going for the

SAP zool. So we'll be going for the introductory part of the zool and I'll be showing you how you can set up the zool for that. And then there will be technical landscape integration security and data protection. How you use zool?

What are the zoo admin centers? How you

monitor and troubleshoot it and constraints and considerations of it.

And in addition to that we'll be learning lot of jewel things like we will be how to demonstrate this cross functional queries how you use it in the multiple step suggestions segments how

you add your UI how you create your sample datas you know how you make that charts coming into your way so a lot of things that whatever the industry specific that when you go for a job when someone expect you to do what have from

a jewels perspective so those are all thing you're going to learn as part of these training on that so this is a uh whole level that was been kept on this detailed course content will be SC know like sent to you in a while and then

that is what we'll be covering. So this

is for more of 30 hours training which are scheduled for that and the 30 hours this will be covered. So when and what the schedules will be there once the aminations have been you know locked for it. Yeah I'm open to questions then for

it. Yeah I'm open to questions then for that. Thank you.

that. Thank you.

Any questions?

So if we don't have a um like a June license in the trial trial account like how do we practice or like how can we is there anything like >> no this practice we will provide you the

server you know like that is what we're trying to do is for this training let me tell you it's not that there is no server so from zarant we'll be providing you the monthly server but someone from support team will right now you know

pitch in and they will tell you the server will be there for practice don't worry about that practical server will be there Yeah.

>> So in your first slide like you have mentioned about the layers like the data management layer.

>> So in the notepad like there are like a two data management layers like it's same data management one is for like it connects to your third party and then the SAP data on the top database

management layer you're saying something different like what is the difference between exactly these two database management layers >> right? So the top one is this is sorry

>> right? So the top one is this is sorry this says integration layer it's not completely data management I have written wrong it's it's completely deals with the integration can write for that this data management layer it will take

care of the integration >> okay got it thank you >> yeah yeah >> yeah any other question please >> yeah I wanted to understand there is

it's mandatory to have SAP B2P knowledge or a functional consultant can learn this with ease What's your thought on orient will take

care of basics understanding of no tech will not take care of that but yes this is not mandatory to have SAP's complete BP but we will be learning whatever I'll be showing going for you here right so

that will be enough for you to explore whatever you can do it it's not a separate BTP yeah BTP knowledge is mainly important because it's tightly integrated in BP just you have to understand some of these cons and cloud

services where you go and where you check you know kind of thing Okay.

>> Any coding experience required?

>> Sorry. What is that?

>> Any coding experience required.

>> Yes. Coding experience required means you know like yeah there are couple of things in us you know like you know for example if you see if you are using SAP build then the BTP then you need coding experience. If you are dealing with some

experience. If you are dealing with some of the because we have so many things I told you build is there work zone is there apps is there for work zone and apps you don't this is a complete no code kind of thing so no prior coding

experience strictly required to SAP zool because it's all business scenarios people who are developing and you know using the technical building on AI powered kind of things on the optimization tool only they need the

knowledge of it so others they are not required people who are at the business user level who are leveraging for cross domain functionalities who are looking for some other app creation kind of things they can really go with it to

build their application seamlessly without any code. But if you want to create something new on the Z that you want to make through Zava or APA or JavaScript then yes you have to famili familiar having some coding will be

required.

Okay. Basically, I'm asking in terms of a functional console.

>> No, functionality is not required. Not

required. Not required. Yeah.

>> Okay. Thank you.

>> Yeah. Hi. So, suppose you want to extend for that standard apps extensibility or custom application extensibility. So,

does we require to need to write for the NodeJS code over here?

>> Sorry, I'm not getting question. What is

that?

>> Yeah. Suppose example we want to explain for the standard applications or custom applications. Extensibility of the side

applications. Extensibility of the side by side. Okay. In that case, so does we

by side. Okay. In that case, so does we require to lend further to NodeJS or is that will be J copilot will be suggested to write further to copilot.

>> Yeah, you're right. So that is something you know like you might use this you will use the BTP here basically in such cases where you will you can leverage but other development al environments

also there. here from Zel side it will

also there. here from Zel side it will accelerate you for your um uh generating code suggestions so it's not a replacement of your sidebyside extension itself so you have to do the coding but

it will give you suggestions of it as an intelligent assistant to you as I told that innovation is still not there in the zool it will not write any code for you but it will tell you what can be done with your code

>> okay as a sideby section >> yeah yeah if we provide for the any prompt for that also by the even for the briefly explain about the prompt

because it basically functions as a copilot. It will help the developers you

copilot. It will help the developers you know by giving some code snippets. So it

will offer some assistance for you during your development of of such extensions what you said and uh it will not replace the need to use your NodeJS consulting or something you know in the runtime environment. Yeah for actual

runtime environment. Yeah for actual coding mode >> because all your side by side you have these are all custom applications what you're talking that run independently that are integrated with your main SAP stream. So these usually developed by

stream. So these usually developed by your technical consultants only through your Java or JS or whatever it might be.

Yeah.

If I compare to which no code and low code is different and the SAP job will be different. No or same in the same

be different. No or same in the same umbrella.

>> Yeah. Tell me what is that?

>> Yeah. If it is suppose we have SAP builder no code low code. Okay. Is that

the difference between the SAP zone or is it the same in that within the umbrella only? you know no different you

umbrella only? you know no different you know here it's completely uh what I want to say like zul can help you in the no code development basically you have to use your graphical drag and drop UI

builders all these things will be there where in which it will leverage that and it will show some data in your copilates as well here you have the flexibility to interact through your normal language prompts will be there there in which the

a generated code and workflows will take it automatically so here both developers and users can get benefited from your assisted coding but in the no code you will be most of your no programming

knowledge have to inbuilt it for getting the development landscapes or you know your apps to work on it that's what but here no mandatory coding for business users developers can use it to assist the coding that's the only tagline I

want to put it yeah >> yeah but in the case of SAP uh no code and low code there is a providing for the tested data for that one so yeah

will yeah there is a providing for the tested data by default itself only so that later as for the statement we can we need to change for that is there

way. So here in that in that saying in

way. So here in that in that saying in that same case here in the is there any job for that one?

>> No no no separate job for that but no no.

>> Oh okay. Okay. Thank you. Thank you.

>> So basically like you said like BT having BP knowledge is a little bit necessary. Mhm.

necessary. Mhm.

>> So let's say when you when you explain any application with respect to the BTP will you be able to cover like a kind of a briefing session on BTP so that we can proceed >> not completely yeah but I will show you right because as part of for example if

you want to up something I'll show you steps in the BTP so that will gives you some knowledge in BTP directly there is no briefing will be required but yes while going on only the briefing will be done you can assume like that yeah

>> okay so other question is on agettic AI part right like where we create the agents and all to do some basic stuff and So uh build some application. So

>> how many agents we can create or what is the limitation we have or how much and let's say during the course you said that you'll be providing the server for access right like is that extended for a

couple of more weeks or months or is it like only during the course content till that course content the servers will be given >> right that one will be answered by LMS

team as part of the agent I I'll explain you the technical part see agent in zu it's a new generation of air capability like you know the zoo moves beyond just answering the queries or providing

insights here. So where in which you can

insights here. So where in which you can do all your collaborative multi- aent architecturing and you know you can autonomous your workflow executions there will be all role based control will be there through your human

oversightes will be there like you know through this agentic AI you can demonstrate the like a kind of sales cache collection you know like we want to generate tickets suggest resolutions or you know make some communication

draft for the human approvers you know all these kind of things will be there as on totally you know like as it is J enabled at the organization level So how many agents means you know it starts of

the the moment when you create and deploy multi- custom agents like for tailored to your unique business needs it will will be having the studios agent builder which which will divide which will decide for that it's not that

specific to one or two I'm not cannot cannot say that right it all depends upon the moment when you create and deploy the AI agent will be automatically the limit will be leveraged there itself only so you can

operate the infra and governance practices will be there where in which the maximum um limit will be there as part of that it's not that I will set or system will set for that the moment you

do it it will be generally do there is no fixed cap that is the answer for that the dual legends >> okay so is it like kind of kubernetes container based or it's like uh the it's

SAP owned kind of container services how it is basically like >> right so yeah similarly it runs on the BP so SAP owned the the architecture has

SAP BP so it will be generally deployed and managed in the BT TP's cloud foundry but yes if you want rather than this one if you want to make it kubernates we have the ka environments also available

one as well so which means it will handles the containerization and orchestralization behind the scenes also end users generally do not interact with kubernets directly in the scenario

because these are all running behind your scenarios so if you want to understand more on the intra part of this particular thing you can go for the other accounts of the BTP as well so

because we have cloud quarry is there, we have identity services there rather than globber cluster operations. These

are all the most best ones which SAP B2B is already running for that. Yeah.

>> Okay. What what is the course uh fee for this? And

this? And >> look, we'll now come back to you on this.

>> We will I have a question.

>> Yeah.

>> So you you showed us that the AI core is not available on the trial version, right? So do you have a CPA EA or a PO

right? So do you have a CPA EA or a PO license that you want to provide us during the time of the training? Sorry,

which license you're asking?

>> For the BTP, if you need to have AI core enabled, we need to have either a pay go or BPA license.

>> Yes. Yes. Yes. Yes.

>> So, are you going to have offer us one of those?

>> Yeah. Yeah. A core only initially we taking because lot of costly thing in the SAP space. So, whatever is there for the training only those things we are getting into the uh license mode and we are just showcasing those ones as well.

Yeah. Not multi ones.

>> Okay. So, So like I think each license type has a restriction on how many apps we can develop. So do you have clarity on what you're going to offer us?

>> Means um I'm not understanding mean you how many apps you environment is cloud based it's completely cloud-based.

>> Yeah.

>> So it's not like an ID where you spin it up and then you give access to somebody right.

>> So which is completely controlled by SAP. So if you need access to a core,

SAP. So if you need access to a core, you have to either take up a go license with SAP or CBDA license.

>> Mhm.

>> Right. So

is one of these going to be offered or you just going to give us in a trial account?

>> No, no, no trial account. We're trying

we doing for the license only. No trial

account on this. Let me tell you >> which license type is is this going to be >> the dual studio license will be there in this which will be integrated to the SAP BP. No, I'm not talking about dual sh

BP. No, I'm not talking about dual sh dual sh is available for free also. It's

on the trial as well. I I need to understand the AI core entitlement >> on the business. Yeah, you're asking specifically >> core entitlement on BTP.

>> One second. Yeah, it it will be there.

So, we will be checking and get back to you on the AA core will be there.

Entitlement is also there. But the

licensed one or trial one I'm not sure because I have to check for the possibilities in where it will be according for that because as you know on the AI foundation services level we we include this core actually which is a

part of BTP as you said. So on the limits there is there is no publicly said there is no limit of number ofations in this as you said there is no such limit actually been kept on this.

However what I seen there are some practical limits are there for the subscription. Okay as you have outlined

subscription. Okay as you have outlined now there are some compute resource quotas are there. What I understand is suppose so that one at the service instance limits we might limit it that's not that these many applications not at

application level but at the kota level this will be restricted for user yeah >> so is it going to be one sub account shared with all the users on training >> preferably yeah because up to 10 active conversations is what we are taking for

simultaneously per user which is the limit on concurrency on a core usage itself only so that is what the limit we're taking um yeah sub account will be one one we should be sharing with it or else I'll try to have separate separate

segments also can be done with the admin. I'll just try to check with them.

admin. I'll just try to check with them.

Yeah.

>> Got you. So what are you going to cover on this the course right?

>> So is there going to be an integration integration with the back end S4 system as well?

>> Yes, it will be there >> through BTP.

>> Yes.

>> And Okay. And we're going to be doing a modeling and grounding as well. Is it?

>> Yes. Yes. Yes.

>> Okay.

>> I have a question. Correct me if I'm wrong. What I understand from the

wrong. What I understand from the session this product we need to configure based on the business requirement. Am I right?

requirement. Am I right?

>> Yes.

>> And if so what what I assume it is a co work c-ilot. Okay.

work c-ilot. Okay.

>> So business requirement is business is not aware right now in upront what they are going to use what queries they are going to ask during the during their

working practice. So how do we take the

working practice. So how do we take the requirement for the configuration up front?

Great. So see requirements will be seen this is all actually aligning with the business goals bits basically like you know if you can see for example as you said you know like how you take it. For

example, if you want to show business some ready innovations or if you want to show any industry benchmark that your current organization want is struggling to achieve like you know cutting some of

your cycle times enhance the current user experiences you know new automation opportunities that industry is now leveraging which are not there in the current organization. These are all the

current organization. These are all the ones which can be a requirement for you where you can go with it. There are as I said there are a lot of things that in a zoo that can actually put so it it might be your cost reductions risk compliance

or it might be your productivity gain or you know like completely opportunity specific where actually we can invest and we can grow like kind of things you know these are all things will be there this is this is where you can actually convince your business for SAP it's not

convincing it's actually been proving for the business to go for so if you have specifically asked how can I like give requirements and know take requirements I mean that means for the zu studio you're asking or from

Organization you are expecting that you know what requirements can be done.

>> Yeah. Organization requirement basically >> see or requirements will be completely based on the business as has been already discussed on this. So it might be a key challenges which your

organization is right now taking care of that like for example they said if you are in the ABAB part itself only if the ABers are taking lot of time in the unit testing and your red lines are crossing

for that. So SAP jewel is a solution

for that. So SAP jewel is a solution there right now which was showcasing and proving that or else if you have seen a lot of what I want to say the innovation that you want to put it in your organizational app for example it's a

healthcare or farmer manufacturing where you want to do it and make it done so say from SAP zool studio you can actually start giving the through SAP build where you can generate a no code low code kind of apps and you know get

this done through your single service platform kind of things you know these these are the things where you can organize can benefit they can actually you know integrate through the zool. So

specifically these are all you know on the licensing and you know on the BTP platform where you want to leverage there is a huge scope is there I cannot say there is a limit you can limit to itself only there is a very bigger huge

scope is there the provisioning and integration level the more you can start providing and integrating the more you can get it from the zool as well that's how it is going on right now

>> yeah got it thank you >> yeah I have a question so during this course as it is on the automation different things. Uh

different things. Uh >> will we able to go for the capstone kind of project or is it kind of just a learning?

>> No projects. It's a learning only. Yeah.

No project. Yeah. This is purely learning of 30 years training. Yeah.

Like like election trainings you have capstone kind of things. No. There is no such kind of thing here. Yeah.

>> Hey. Hi. Good morning. So actually like now is integrated with all applications seamlessly, right? So can we create uh

seamlessly, right? So can we create uh transactional data by just giving the required fields like you said it is linked with procurement and different

areas of SAP. So can we just give some mandatory fields in a PO and can we create directly P from the c-ilot

does can we leverage in that way also?

Yes. See not directly in all cases as of now SAP zool is mostly used is to assist, guide and automate decisions but not fully to create your transaction across all SAP modules on its own. So

some creation is possible like in the controlled workflows whenever you are doing ability to expand certain types of things there you can do for example in success factors jou can draft a requisition or job description a kind of

thing. So these type of things we can

thing. So these type of things we can expect from it right now. Yes as I said in the future renovation it might take it. Yeah but I'm not sure. This is

it. Yeah but I'm not sure. This is

recently launched right. So yeah this is what the limitations right now know but you cannot ask execute my post a journal entry create a material document you know create a sales order it will not do it it needs user confirmation or

redirection to standard apps for that it will do but it needs user interaction for certain time yeah >> what's your key call to action for all functional consultants because I

recently attended some SAP inside tracks where AI are very seamlessly coming so whatever it's like >> one small giveaway. Yeah.

>> Yeah. It was generally definitely beneficial for all the functional consultant like you know like when you are learning the zool for uh like specific industries are also focusing basically as I told as I told you. So

functional consultant can generally get lot of benefits you know when they do it because it will ease their work as part of that what I'm thinking because you can leverage your business process easily you can guide clients you can identify the use cases propose the

solutions also on top of that easily. So

like especially for success factors are you know like for manufacturing industries are mainly focusing. So you

can get lot of benefits this is the thing which I can say because if you say for fi side for example if you want to show over invoices by region or if you want to draft journal entries zul can easily do that for that. So if you are

doing manually I'm just giving simplices for functional level at the MM level also for example if you want to understand how many late deliveries happened if you want to suggest a PR creation a kind of thing it will help

you and SD also as I said sales orders and stuck in approvals what you have to do where approval STS are there what is the next flow it will take it automatically so because you asking someone hey approve approval so zulu

will take care of that so this is the benefit basically organization gets it will reduce the manual intervention it will reduce because every single day I cannot ask someone to approve it you know that part Z will take care of so I

can easily done and it will be easily the approvals also can be easily managed from that that's what I'm giving you have to think from the more broader perspective right now so it is where this is where the manual reduction is

coming on so see it's not that it is completely configuring it's not that completely doing something a manual job but it is automating some of the flows where manual intervention can be reduced more on it where the time will be saved

for it you're understanding that right so this is where the functional call whatever it will definitely help on that. If you start integrating to Z and

that. If you start integrating to Z and giving you the processes and automate the flows, it will seamlessly free the business roadblocks and the business flow easily to the customer in a more

brighter manner. So that's proved

brighter manner. So that's proved because many clients started that that they proving for the clients as well. So

that's what we are saying a proving statement not a expected or you know a K statement. Yes. Yeah.

statement. Yes. Yeah.

>> I have one question.

>> Yeah please. So who are all eligible to take up this training and then put it into implementation? Meaning a person

into implementation? Meaning a person who is working on SAP in SAP area and success factors. So does the person need

success factors. So does the person need to be an architect level or just a functional consultant also? All

functional contents consultants, FI, MM, SDPP, HRP mothers know they can easily understand how we interact with SAP applications like because Fiori or S400

people who know SAP who know SAP applications Fiori S400 cloud how to use it how how can define the business use case for Zuli they they know that and

they can understand of little bit very little bit of a based process automation because anyways we'll explain that so this is where for the I'm giving the for functional consultant this is the requirement criteria Yeah, for technical

consultants the requirement criteria will be they have to know little bit of they have to know ABAB completely and they have to know BTP integration for that and is the prerequisite and for

architects the prerequisite it's completely they have to understand the SAP build SAP data sphere and external data source integration okay and I am not in any of these buckets I a business

user but still I want to understand zo then the requirement will be they have to it should be a business analyst they where they can understand the process and then tell the process to the zoo.

That's it for all nonap users. Joel is a general purpose AI. So it's an embedded into SAP app. They need at least some knowledge of SAP and some knowledge of SAP BDP. That's it little bit which we

SAP BDP. That's it little bit which we will get you know get conquered in the training as well. So this is the stage bystage requirements for eligibilities for the people. So does Joel SAP Joel

involves any technicalities meaning you know like say compared to functional and technical >> so how far it'll be I mean we can leverage as a function consultant

>> right it's a good question as I said someone has already asked this question you can leverage extensively okay not by writing code but by shaping your business process in the AI mode that's

what I told someone has just asked very practical level you can do it They said uh lot of extensibilities there in this rather process optimization or we can say use case identification or workflow

designs insights or client communications testing validation collaboration lot of things zool can do so this is a functional consultant scope I'm telling on the SAP's zules

perspective these are all are proved in the SAP zool for the functional level yeah this will definitely an extensive benefit for you yeah >> right so this SAP zool came into existence since two years or more than

No no no no no no no not two years it's been last one one and a half year only but very recently from July 2025 only latest patches and upgrades are there in it's it's very just in this month only >> you know I mean what are the

possibilities of getting I mean landing into a job in SAP zul without experience meaning you know like so we all get trained and then how can we go and land

into a job >> yeah see it's not that these days now because zul is a new one everyone knows that we can't say 10 15 years of experience in zoo basically But yes what we generally Java market see is as a

business process expert or as a functional expert how come you leverage the new tool is what generally they look into it. So that's what if you know the

into it. So that's what if you know the tool if you already worked on tool little bit without experience is okay still but if you understand the best shot of it how can actually position myself you know as a process owner how

can I bring difference as a process owner to the organization by using or leveraging SAP zool is what the bold statement there so there it will gives you the job market that's what

>> I know I have even learned about it that there is no certification in zul right >> right now currently there is no certification yeah >> yeah but then how do clients you know like pick up the resume

if suppose you know if you claim say maybe not even experience without experience but just knowledge >> how how will it convince the client >> you won't have a traditional

certification but you can do SAP generative certification is that that can help you on this if you really are looking for a kind of certification it's it's a if you are saying the course has been completed means you know like it's

SAP is generally give you official digital badge for that a record of achievement a kind of thing like that you get from SAPs and from the Zarantech as well. So that is that is the thing if

as well. So that is that is the thing if you say you are in SAP Z that is the only thing and can resume can be easily picked up that's it yeah there is no >> after getting trained yeah after getting

trained from zarentech okay like the complete course >> so will will this knowledge help us in getting a job or applying >> definitely definitely

>> in what way meaning you know it is just a theoretical knowledge right >> no no no I'm showing practical right what theoretical you're going lot of practicals in this I'll So everything practical no PPT is nothing I won't run

any PPT here day 1 to day 30 everything practical no PPS >> but no certification and no project right >> certification in the sense means SAP is not giving that right so you can have

your course completion certification will be there which can be leveraged by you in this in this your in your profile as well that can be done yeah >> correct but you will be showing us all

the configuration and everything >> hands on also Basically I'll show whatever SAP zool is required in the content I'm going to show everything to you. So it will be that's what I'm

you. So it will be that's what I'm saying it's a job based training only it's not something we talk in PPTs and show that is that is not required you can you can read in the web as well so practically we will train you what is

required for zool what can be done in the zole the scenarios everything you will see that here then you will understand you will you will create something you will have something you'll understand you'll get complete knowledge of it and you'll get a confidence on

that so that's what I'm saying it's not only something you're learning out of the box on what you have in the web >> all right yeah thank Yeah.

>> Yeah. I have a question. Yeah. So I am the I am Ariba consultant and don't have any prior knowledge on BTP. How this

course will help me?

>> Definitely this will help you a lot.

It's not it doesn't mean that like don't have BTP knowledge as I said you know like um when you go for learning zool the initial things whatever the standard setup that will automatically take you

there because you can even without BTP knowledge also you can learn because because you're as you know aribba how you can design the zo to be used for your functional driven concept is what

you have to concentrate that's what you can more concentrate in this training because it's an embedded z is an embedded in sap like you know I I as it is for larby don't need to build BTP services here people who are I told you

that people who are completely on the technical part they have to more concentrate on that particular part so it's already integrated in many cloud apps also through this the whole Ariba integration also there so you will be

more concentrating on Aribba buying invoicing Ariba sourcing Aribba supplier management so you will be more focusing on that so BTP knowledge is not highly needed for you as of I know just only

for initial things to know on that yeah >> okay so means presenting the Ariba integration piece as well on Jules.

>> Yeah, we'll be showing that as well.

Yeah.

>> Okay. I have one more question.

>> Uh this product is on the cloud base, right? This is the cloud-based product,

right? This is the cloud-based product, correct?

>> So in case I'm I have onremise solution.

So how will it also coordinate with the on-premise data to give the better result?

>> Means you want to integrate to onremise.

>> Yeah, because we are using the onremise, right? We are not using the for example

right? We are not using the for example MMSD other part we are using on premise right arib we are using for the cloud >> so this product when it is a cloud how it will coordinate with the on-premise

data >> I'll tell you that you know like if you're using SAP onremise systems you can still leverage SAP zul directly or indirectly also because there is a hybrid integration is there by SAP BP

where you use SAP BP as a bridge between your onremise and SAP zoo so what you have to do is you have to keep your core ACC I mean or your SAP 400 onremise you

can connect it to SAP BP and then you can use your SAP AA core okay um the AA core and AP APIs will be there so they will it's completely prompt based you

have to enable those insights and then you can access your zul through your fury or BTP based apps so this is how this will be done your data should sit on the on-pre so like you know for whatever these integration things are

there so that needs to be done by your admin properly so if the connection s are mislabaged. So this cannot be done.

are mislabaged. So this cannot be done.

But yes, there is a solution for onremise as well.

>> Okay. Yeah. Thank you.

>> But you have only onremise no cloud then no z will not work. You should somehow jump >> in organization nowadays some application are on cloud-based and some application on onrem.

>> Right. Right. Right. If it is purely on like ECC6 or S4 HANA 2020 kind of thing without BTP zol is not a solution. It

should have something with BTP as per cloud then it will be easy for you to run your environments with with your on-premise.

>> Mhm. Yeah.

>> Directly Zol does not run on the on-prem. You have to understand that it

on-prem. You have to understand that it is a cloud where you integrating your on-prem for your data. That's it. That

will be possible.

>> Yeah. Only it will face the it will go and fetch the required data from the onremise and use.

>> Yeah. Front end will be again your cloud will be there as cloud. Yes. Yes.

>> Mhm.

>> Okay. Got it.

>> Yeah. Another question please. So how

long is the training meaning you know duration of the training?

>> This is for 30 hours training.

>> 30 hours training and you will cover everything meaning you know B2P access to B2B and everything.

>> Yeah. Yeah. Yeah. It will be covered.

We'll cover. Yeah.

>> So I mean just having undergone your training. So will we get that confidence

training. So will we get that confidence level that yes we can go and then start working?

>> Yes definitely you'll get it. Yeah.

No no questions about that.

Will you provide the recordings for us?

>> Yes, recordings will be available. Yeah.

>> Okay.

>> The LMS team will be there. They will

let you know there is LMS thing in Zerantic is there where in which you'll get access to it every day. I mean every training recording will be there on that every time whatever I am going to train you the recording will there so people

who are absent or not available one or such day they can refer the recording easily and we'll give you the materials also for that. The materials will be there in the online easily. Okay. And

this support will be there from 4x7 support will be there from the SAP Zantex LMS team. So when you say the materials right so bas basically it is related to the class only or like we

>> No no no no not class the additional materials for you to explore from SAP's standard best practice materials we provide >> say for example you just give some uh

like practice some examples and all do we get the solution documents also the way we >> stepby-step solution documents are there for every single module is there in SAP

Zarantech so for this we are also preparing for that we'll give you the step-bystep documented with screenshots also. So don't worry about that. Yeah,

also. So don't worry about that. Yeah,

that will be available. Yeah.

>> Okay.

>> But as of see if you can go with the training and recording that will be most enough for you. But yes, the documents will be there is what the answer I can give it for now.

>> Yeah. Because the problem is that like uh like considering like most of us are already working in some companies on and we'll have our own project priorities, right? So what happens sometimes we

right? So what happens sometimes we ignore doing the practicing and all. So

at least if we get the solution document we can just refer through it later and then we can start privacy.

>> Yep. Yep. Yeah. Yeah. That will be there. Yeah.

there. Yeah.

>> Yeah. Okay.

>> We all from the different backgrounds and different we're working in different modules. So how particularly you are

modules. So how particularly you are going to cover that? Suppose I need to know about the by mm and someone needs to know about the SAPSD. So how you will cover that?

>> See on the scenarios part I'll cover the rest all you have to explore. See one or two apps I'll show because I cannot cover every single instance. So Ariba

once one instance I'll cover because the core subject is same to all. How you

replicate and how you know like realign to your business process up to you. So

that is what you have to do it. So for

example if I show finance one scenario material management one scenario kind of bar success factors one one scenario I'll show you rest all you can explore on that easily. You'll get it easily on that

>> and if I if if if we need something that help from you on a on on a different scenario will you able to help?

>> Definitely. Yeah. Yep. Definitely the

core participants are having some we can just show you the scenarios on on that as well. Yep. That's not a problem right

as well. Yep. That's not a problem right a small disclaimer before I go before I go also like you know see guys before we dive in let me ask a question you know how many of we have tried really the

chart GPT or any tool in your personal life there might be a kind of people who might already use you know for certain reasons or certain scenarios where we need some help on chart GPT or any other

AA tools right now like Google chimney or some other things as well right so how many have actually used a inside your enterprise system. Has anyone

started using that? Anyone started using system enterprise system specifically right now?

>> Yes. Use no.

>> Okay. So what I'm saying is using means not for solutioning. Yeah. But for you know for your enterprise organizational initiatives or as part of the development of your project requirements

you integrated these things and you know also using them along with that not for only for your personal solution. We not

integrated this by way of agents but we have used RGB even to develop design and code and all that you know higher level design low level design proposals

project proposals but using the interface copy pasting and not using an integrated aentic model.

>> Okay. Okay. Okay. Yeah. Sounds good. See

AI has been hyped for years you know but in enterprises there's a small disclaimer you can listen to me and we can also read that so AI has been you know hyping for many years right but in

within enterprise level adoption level it's been slow we have seen that why because of three major problems why it was slow because the first important problem people or the society or even

the organizations were caring about is the data privacy and security is the main concern and second important thing is the business context It's awareness because whatever a human understand

whatever a machine understand it makes some difference and integration into the actual work. Okay. So if you want

actual work. Okay. So if you want something like a plus b is equal to c that is still okay but you want to go in details of any of an individual problem like what human thinks is different from what a machine think even still also if

you anyone have tried with sap's sorry no not saps the a the chart bot kind of a tools they will ask you a lot of questions on top of they won't give you the right answers you know they you won't land in right answer until you

give a right question to them so this this is called integration into the actual work because SAP jaw comes here is designed mind to solve whatever the

three important problems which I have mentioned right now. Okay. So SAP J. So

this is our agenda for now like as part of session one we're going for what is SAP Jaw, what is the architecture of it and what is the key use cases, what are the integration points and what is the UA navigation. So these are the things

UA navigation. So these are the things which we'll be covering as part of this.

So little we'll be having a theoretical thing and then I'll be showing you the practical part as because people have to know the server because I'll be showing that as well in a while. But yes, let me speak you about because a couple of new

new set of people have joined in this session. So I want to understand them

session. So I want to understand them what is jaw first of all so that they can understand they can you know like make things accordingly for the plan of this training as well. Okay. So yeah SAP

jaw as I said it is designed to solve all the important problems what I have just shown you like it's a more of uh the secure the contextually or directly in the SAP systems whatever you want to

already use. So this one is what SAP jaw

already use. So this one is what SAP jaw came into picture. So SOP jaw is not just another chart. Let me tell you people think if I say jaw it's like the the mindset will go like it will be a

chart for you. No it's not a chart it's a a copilot. Let me tell you the bold letters it's a AI co-pilot or you can say a powered copilot whatever it might be. So this is embedded across the SAP's

be. So this is embedded across the SAP's ecosystem. So this was basically

ecosystem. So this was basically designed to understand the business context or the data semantics and the workflows as well. Okay. So imagine an

assistant who already knows your company's data processes and your role and can you give answers or even take actions without you writing a single line in line of code no right so let's

compare that that's what I'm saying when I compare with chart GPT because people will generally think SAP jaw is alltogether different so don't compare that with any of the right now

tools which is going SAP's jaw is for SAP's ecosystem okay not for everyone right now Okay. So, chart JPT generally what it does it's a general knowledge

but no SAP context or security awareness. Even if you put questions on

awareness. Even if you put questions on regards to SAP in charge GPT you will not give the right answers because the database will connect the SAP's charge GPT's database you know the questioning

database or the NSL database will connect to the SAP's database again it will connect to different different SAP help sites from there it will pick the answers based on the keywords whatever you key in. So that is not a right one.

For example, if you want to if you have a problem, for example, people are on the finance if they have a problem in uh know like generating some exchange rates, you know, where they are not going to they're having some differences

kind of problem and they're migrating header and you know item level exchange rates. If this problem comes to you so

rates. If this problem comes to you so SAP can answer or you have a human human functional consultant from finance can answer but SAP's the charge GP cannot

directly answer. It might give you some

directly answer. It might give you some solutions which might or which might not work though no 100% solutioning you getting that so when you compare this

charge with Juul Juul understands SAP data models like it understand SAP tables like EKO BKP of whatever is there it respects all the SAP authorizations

and it will talks the language of business processes that are containerized in the SAP very very internally. Okay. So importantly, Zuul

internally. Okay. So importantly, Zuul is not a standalone app. You have to log log into it. It will show up in S4 HANA.

It will show up in SAP Ariba. It will

show you in SAP success factors, in build apps, in process automation, anywhere you work for them. So instead

of switching between the systems, Juul comes to you in the context. Clear? So

this is this is what about a short introduction which I want to give you on the SAP. All questions I'll answer at

the SAP. All questions I'll answer at the end of the session. I'll give you 20 minutes because a huge crown is there.

Today I'll be covering at at a high level. Okay. So this this is what we we

level. Okay. So this this is what we we have to know about the jewel. Okay. So

we have to understand one thing when you are speaking about jewel or when you are talking about jewel because you you have to always keep it in the mind because many of you in this crowd might have the

sales experience. They have to promote

sales experience. They have to promote zuel or they have to use the zoo or they have to integrate the zool. lot of lot of people come into the lot of different areas, different capacities will come.

That's what I'm saying all these things to everyone as a base platform. So it's

a one co-pilot for the SAP ecosystem. So

this will serve as a productivity tool to help customers to get their job easily done. Okay. So a any interference

easily done. Okay. So a any interference is coming why to get the convenience and for the customer right and the make things faster than human. These are the two important priorities why AI is

really fluttering high, right? Which

means we have in SAP you have a centralized framework for your cloud solutions that will allows the users to ask questions and interact with the zu

wherever they are natural language dependency is there whether they're an SAP S4 HANA you use Zul to ask about your open HR request SAP success factors when you want to go for SAP start

leveraging Zul to retrieve some information on SAP cloud solutions these are all it will do right now okay this means Means Zul has one consistent user

experience which makes the usage as as as better as possible. So we offer zool basically out of the box and natively integrated with a lot of cloud

solutions. So which means there is a lot

solutions. So which means there is a lot of pre preconfigured content which is active for your customers with all the limitation configuration efforts and all these things will be there. So, Juul is

available in your first SAP cloud applications today like your success factors, Aribba, cloud pro edition, cloud public and private editions and all these things are there. Okay. So, it

will not be offered any onremise. Let me

tell you that people might think that is the ZO having any on-premise solutions.

No, on-premise is really not offering as everything we are delivering with the SAP business, ZUL will provide all the things majority on the cloud-based

environments. Okay. So there is there is

environments. Okay. So there is there is no onromise as of now but is as relevant content for the users you can ensure jewel at at know at a product context

level for the reliability level you can see the using LLM know you can have responses that are grounded for SAP knowledge and business reality for the respective customers and Juul is

responsible to steer business partners under a strict prohibition where in which data is not used for training purposes or any other usages or any third parties but for the purpose of

your internal organizational work environments. Okay. So this is this is

environments. Okay. So this is this is what you know the basic introduction that I can go for you for the zool.

Okay. So now what makes the SAP zu in you have to know that what is that unique features that are really making this right because zu truly understands

customers business like you know in a different manners like it provides contextual greater responses. It will it it will know the responses based on the user what they're typing specifically

SAP transactions I'm talking about for the customer business data and all the things it will maintains the user context and cross applications across different SAP products. So no matter

whether your jewel is accessed from SAP start or the application UI or a mobile device or somewhere else everywhere jewel is accessible with your licensed uh what do you call the licensing is is

promoting that and if license is applicable to that it will be able to access that and the results on the business documents and the links that you want to refer here it has a lot of techniques like you know it will

retrieve your rag we call rag means retrieval augmented generation it is called okay so this is the technique which it will use it. Okay. And it will be extens it will be having the lot of extensibility for different sources for

your internal policies which are hosted on the Microsoft shared shareepoint environment and a lot of user authorizations and authentication rights are there to ensure the complaints and

specifically the safeguard against inappropriate use for know like by what do you want to say that hate spees by employing guards guard rails and all these things right so this will be

strictly prohibited so this is this is this is these are the important things that makes the zoo into a unique thing for the SAP's environment. Okay. Next.

So with Joel what are we offering? That

means we are offering more importantly four interaction patterns are there. So

these are the four interaction patterns.

If you can see here what are these patterns I'll tell you now. Okay. So

these are all important things that you have to know before you go something before you ground on the server as well.

So that is the reason we are giving you very detailed in introductional topics also here. So the transactional

also here. So the transactional interactions you're seeing this provides users a direct entry point to SAP. Okay,

that means SAP means the backend system.

So here the transactional interactions what we're seeing it will trigger and influence the business processes with

the power of the natural language. Okay.

And the generative A for example orders I have to review it. So I need to review it and I have to approve it.

Okay. So that is called what transactional interaction. So I have to

transactional interaction. So I have to see something and I have to review something and I have to finally approve something right which is a PO. Right?

Now it might be SO. So this is called transactional interaction. So I have to

transactional interaction. So I have to interact with the transaction. So this

kind of things can be done in this particular pattern. This is only at a

particular pattern. This is only at a function level I have talked but as you can talk when you talk about internally you can go for for HR level job positions which will be created right

for example if you're an abapper if you want to like write crude operations like create read update these kind of interactions you want to make you can make it out so all the cloud products

are currently developing such content packages because SAP is innovating like that keeping the future in the mind okay so whatever the things that you are

writing developing the content packages that will belong to zuul also because zu will access them. If you write something nonsense zul cannot like get that that doesn't make any sense. So that is how

SAP's backend software are working to get them enabled for the zool also for most relevant user interactions. Those

are all covered under your transactional interactions. When you come to your

interactions. When you come to your navigational interactions sometimes our users want to handle business processes by themselves. Right? There is no

by themselves. Right? There is no developer interference like if you can see people who know business objects the web reporting is there the web reporting is completely user based they can just drag and drop they they make their own

filters they make their own things right everything they can do ad hoc for own them they there there is no requirement of developers there you know kind of thing so it is also the navigational

interaction is also given to the SAP directly the user directly so that every business user whoever the every business user here. So they will connect to it

user here. So they will connect to it and they will make it. So not every business interaction is best served here via the natural language but yes they

will be allowed to navigate directly where they want to go. So this is helpful for the users who are not familiar with the navigating of SAP applications. Okay. So people who are

applications. Okay. So people who are new to it who want to understand all these things like this navigational interactions will help to them. And

coming to informationational interactions in the zone specifically so we are V in the sense means SAP here it will provide users specifically a

knowledge based results on that is called information. Okay. So for

called information. Okay. So for

example, HR policy related questions will be there or you might have questions regarding your uh travel policies, information content, SAP help documentation or OTP nodes different

different OTPs will be there because yeah you will be searching in Google and getting exhausted right for certain OTP nodes certain help nodes also those will be easily found no in this information

interactions okay and that is that is what about information interactions so which it will be provide you and analytical interactions No here you you will be getting more like you know

enabling of analytical interaction that are based completely on the just ask type thing because this will support the SAP analytical cloud. So here you'll get

enable customers to leverage the zule for analytical queries. So uh this is a very recent one in 2005 from March onwards SAP planned to integrate the ZO

into stack as well and further it was evolved the analytical capabilities of ZO also because you don't need to prepare dashboards you don't need to know like prepare a kind of what do you call the tables or something for the

customers if you give your data inputs and Z will take care of that is what they are doing in SAP sack because SAC is where the environment the recent environment where you will see completely front end where you'll do all

all the reporting kind of things. So

that is now also getting you know going into these all. So for for that you know people can easily get into it instead of humans doing that is where the lot of automation is coming. Okay. So these are your interaction patterns like these are

different different interactions patterns. You can these are what this is

patterns. You can these are what this is what I told you for the zo which it will help you like this in this screen. Okay.

There is another important point called document grounding. So what is document

document grounding. So what is document grounding? It's a capability basically

grounding? It's a capability basically in zool which can provide the comprehensive responses basically this responses will be on the drawing because from business users or business

documents that you are locating in your SAP and third party repositories whatever you want to get them connected so this document grounding will help you on that so you can so what happens with

the document grounding in zool means you can enable the customers to upload their human content like HR policies, travel policies or you know like um sales

documents or me or MMJ level finance level whatever the documents that you want to put it you can put it. So what

happens with this means this will enable the users to ask questions because this question just asking or questioning why they are specifically putting is

documentation is very important as every every SAP consultant or everyone knows that you know because you are working you might not work someone will come in place of you and there is a lot of time transition happening in the KDS or

something so basically that needs to be avoided and a quicker onboardings and quicker things need to happen so further The questions whatever you have that you ask to your peers or someone you can ask

to zul okay hey what is the structure of this what is this what is the earlier responses on this particular issue who has done that or what is the earlier solution what is the latest status on

that so these kind of questions you ask so these questions when they have to answer the document should be properly uploaded into it okay so jewel will find for it and get it to you okay a kind of

so jewel once you upload these documents you know when to Ask the question, receive answers based on these documents via Zuul. Zuul will find and considers

via Zuul. Zuul will find and considers document extracts relevant to the user request and responds with a concise natural language answer. So this include all the sources. Okay. So all your

documentation will be under the control of ZUL. Okay. This capability is depends

of ZUL. Okay. This capability is depends how the ZUL delivers answers grounded in your customer structured and structured business data as for example in success factors. If user leverage Zoho he can

factors. If user leverage Zoho he can get answers and questions relating to their organization HR policy organizations leave policy organizations you know what we call OT policy you know

like this will save time okay because you don't need to ask a human but you can ask a machine okay in enhancing the overall employee experience on top of this so this is called document grounding so specific specifically what

is this grounding you're doing is this is you are mixing or you're getting the LLMs your large lang language models whatever that are there. So whatever you

want to improve the quality and accuracy of these responses. Okay. So this will be done with this. So whatever the LLMs that you are going for to fine-tuning it, you can do that and you can make use of this. Okay. This will help in the

of this. Okay. This will help in the models you know for doing a lot of sourcing of a document level and you know it will you know it will minimizes the ambiguity and all these things will

be there for this. Okay. So how does this grounding work means you know like you can see this one here this grounding how this AI is thing you can see this the grounding environment here it was going entering equation a user is

entering a question you can see that so zuul is connecting the retrieval of the hana vector databases and through llms it is answering that you can see a customer can connect the document

repositories via there this is through Microsoft shareepoint right and creates embeddings which means you separate the text in different chunks and vectorize

them so that vectoring is happening in this HANA database. Okay. So embeddings

here this will refer to dense or I can say it's a continuous vectors representing text in a highdimensional spaces. Okay. So these vectors they

spaces. Okay. So these vectors they serve as a coordinate in your semantic space. So these will capture the

space. So these will capture the relationships and meanings between your words. Okay. So I can say leave leave

words. Okay. So I can say leave leave meaning will be two ways like for example leave policy if I'm saying so system has to understand leave means a person who will be absent not not going

from there because leave meaning will be two meanings will be there le e a v leave I'm giving a small example it might be a complete absent it is going away from a current location right we know that I'm leaving you or I'm having

a leave for so these two things make difference so this I understand but system has to understand this is called vectoring will help this the dimensional spaces these

When a user atterance comes in, you find the most similar vectors with the semantic searches. So that SAP HANA

semantic searches. So that SAP HANA vector database and embeddings enable much granular words, concepts, other things with the meaning what a user is

trying to say. So in the context of LLM okay, the embeddings play a very very very important role in a retrieving the right context of rag. Rag. I already

told you what is rag, right? So in this we we use this heavily in Zo basically this one to process very huge amount of data like if you can say SAP help

documentation with all available languages consists of millions of pages okay millions of pages you can see I need in Udu I need in Telugu I need in Hindi I need in English I need in Tamil

lot of lot of languages are across the globe right so many things will be there so these are all things that can be happen through this model okay which is

a documenting models okay so this is about complete thing about the ZO so I'll go to the architect simple architecture because there's a huge code and questions are there for so I'll be showing you the practical part so this

is the zole architecture guys if you can see here this is the zool architecture so zul provides an embedded co-pilot experience as I already told you across the solution areas so this is consistent

and with the memory of interactions across multiple products you can see zoo is a central point where It is having UX where it having rele management or your cloud applications or your front end levels whatever that things that you

want to make you can make everything here. So each income these are all

here. So each income these are all incoming requests. So each incoming

incoming requests. So each incoming request is processed and orchestrated based on what is available. Okay. So

Juul takes basically three categories into consideration. So let me tell you

into consideration. So let me tell you that. So it analyzes if user prompt is

that. So it analyzes if user prompt is relevant for the Jules scenarios catalog or not. Juul conducts an

or not. Juul conducts an informationational filtering based on the knowledge catalog. So that contains all the SAP knowledge base as well as customer own knowledge base as well

because if it is relevant to a client so that is processed in your rag that means the retrieval augmented generation for enterprise. Okay. And then your LLM will

enterprise. Okay. And then your LLM will generate an answer based on the dedicated text with whatever you have been previously asked. And third

important thing is Julie is aware of the users context and history. So that

includes all the information whatever you that information about which SAP cloud application and the respective user is using what additional applications of SAP that customer has

licensed and activated within the rule.

So these things will be taken. So yeah

this architecture and everything I'll be detailing in the session two. Yeah

session one. Let me show you before I go to the open to question and answers page. I'll show you the server here.

page. I'll show you the server here.

Give me a moment. I'm opening my server.

Okay. So this is the BTP cockpit. This

is the server. So before I talk about the server, hope everyone is seeing my screen here. Before I talk about the

screen here. Before I talk about the server, yes, so there is a questions about the ZU free tile and something. So

let me talk that and then I'll come back to you in this. I'll show you this one.

So this is the BTP jaw. This is not free. Let me tell you this is not free

free. Let me tell you this is not free server free guys. This is a licensed one which we have bought for this training.

Okay. Yes. So if you are referring to SA specifically on the breakdown of know like what do you call the free tire and one see free tire yeah it's no extra

cost for customers who are having the valid SAP cloud subscription like SAP success factors at sport but the two only limited features are there or free in free tri means not I'm talking about

free trial and free tire versus license there are three things are there there is a small trial version is also there you won't get anything in the trial version normally you can just explore the features but you cannot practice

anything on top of that that is v3 but there is a free tide one more concept is also called so that is common features you have like an NLP so the natural language navigations will be there so

where you can go to the zool and you can go to the settings of it and you can have the quick access to business object informations and everything and no explicit per message limit will be there in the free tile yeah but in the

licensed version like this one so in the licensed version you have paid add-on on that builds on SAP jaw based. We can see SAP jaw jaw a two things will be there here. This is your BTP cockpit. I'll

here. This is your BTP cockpit. I'll

show you that. So you have in the license version you have all the advanced AI features which are tailored to specific business domains like what I mean to say finance for deeper insights,

smart summaries and all these things for spend management like category segmentation spo description generations for supply chain equipment insights human capital AI assisted writing

developers specifically AAB developers know contextuals that they can help for coding process automation code explanations you know code fixes also and consultants who are new they can use

the a driving guidance for SAP deployments no so all these things are there so yeah so virtual virtually when your currency consumed per message or here here the pricing model what I want

to so there is a pricing model here which uses the a unit your pricing will be completely on the per message or interaction based example if you go for

rise with SAP esport HANA the cloud premium includes all 2500 messages per year additional usage consumes more on the UI units in The same way users can estimate consumptions with SAP's UI

estimated tool as well if it is on the pricing model. Okay, other than

pricing model. Okay, other than licensing and all these things, this messages also counts for the people who are on the pricing model. Okay, even

though Joel base generally provides unlimited usage, there are some mentions like free message limits in test environments. You know, there are some

environments. You know, there are some particularly trial purposes also there.

Those are also you can consider for that. Okay. So overall on the cost

that. Okay. So overall on the cost perspective for the free tile eligible SAP subscriptions have no additional cost for now okay for premium they have

lot of add-ons for using the AA units which they can use it and the usage limits is presently on the kota base so like on BTP how you release the kota

based on the kota like 1 GB 2 GB 3GB or per message you know this kota can be putting on on top of that okay so this is what the difference between your free

tire and the licensing type. And coming

to here, this is your environment guys.

So you can see the moment you open the cockpit, it is a jaw enabled cockpit.

This is not a normal BTP BTP with Jaw this one. So you can see the moment you

this one. So you can see the moment you go to the account in the subway account, you can see your jaw and SAP jaw AI. So

two things will be there. So if you go to the Joo directly, so you can see your information about the Joel and this is this one. So these are your entitlements

this one. So these are your entitlements for this. See you can now limit the Kota

for this. See you can now limit the Kota also here in this. So here you can see these are all your available entitlement services andments will be there under the BTP with all the services. So here

you basically should have the AI things automation pilots. People who are on the

automation pilots. People who are on the AOL they will get this automation pilot and then they will have this this one authorization man and management services. If you come down these are all

services. If you come down these are all different services. See content agent

different services. See content agent services connectivity. These are all the

services connectivity. These are all the services which people who are already in BDP they might see new services also in this which are relevant for John. See

continuous integration and delivery and then if you come down you will see more things on that. Yeah this is a jaw. So

if you are licensed in jaw you will see here this one this is a assigned one entity kota assignment one global kota one. So this is one which you can see

one. So this is one which you can see here. Okay the foundation application

here. Okay the foundation application here. So if joli is already there in a

here. So if joli is already there in a btp you have to access through bp. So in

bp in services you should have this one in this in the environment. If you come down and AA core, this is also one of the entity service you have to activate when you're going for Zo because this

will connects you with a lot of uh uh AA capabilities whatever that you want to use as part of the Joel's connectivity because this is a PTP service for

running, managing and scaling your AML models. Without a core, you cannot scale

models. Without a core, you cannot scale or manage your AML workloads or models.

Okay, it's like a AI engine room for you. You don't you don't need to try or

you. You don't you don't need to try or run a models directly in S4 HANA or success factors without this AA core.

Okay, this all handles the life cycle management and scaling of all the models. Okay, this is cloud native. This

models. Okay, this is cloud native. This

specifically runs on the kubernates in BTP. Okay. And and this a core

BTP. Okay. And and this a core specifically you know like it is a a agnostic which means it will support all the tensorflow spyarchch I mean the hugging phase lot of things are there

and specifically this is not tied to any UI it's API first which made for integration into SAP or all the customer app. So without this we cannot do

app. So without this we cannot do anything in the J okay and the similar way if you come to a launchpad. So this

is the a launchpad guys. So which is another important service that which we use as part of the jaw thing. So with

this it's it's like a management cockpit for you. Okay. Where in which all the

for you. Okay. Where in which all the SAP A core workloads will work out. So

with this you can deploy you can monitor you can govern all the AI models without needing to work on your API. So it's

like a centralized hub for you for your AI governance. Okay. And specifically

AI governance. Okay. And specifically

use all the other things like build process, build process automation also.

Let me come down. So build code, build as PP these are all will be used as part of the Joel uh app buildings or automations or you know making code for that for any application that you're doing for all these things these are all

comes under picture and they will help you for that. These are all the build work zones that all comes under that only. Okay. Yeah. Whatever the

only. Okay. Yeah. Whatever the

documenting I told you right now, right?

So that will be helped through the SAP documenting. This is one such service

documenting. This is one such service which will help you in the soul. These

are all you will see only when you are activating in the BTP jol not all the other one. We can see here datas also

other one. We can see here datas also people who are into BW and BW specific to business objects and all these things they can also because data sphere also leveraging zul now. So at that level

when they want to integrate over some of the models and all these things to connect and make it happen so they can use the ratas so that is also added here but this is a free t for you for now.

Okay. And you can see SAP document AS is a premium edition. This is not free.

It's a premium edition. Okay. We have

not tested anything right now for this.

I'll show you that when the training session two onwards and HANA cloud is also mandatory because all your back end cloud will be there. This is one of the important service which you will go through it. And this is the one of the

through it. And this is the one of the service which you connect with. And

coming down all the integration things will be there. See this is a is also there wherein people with a also now looking for Joel and automation. So this

is also needed for you. So this is one such service which will be assigned to you when you go for that. Yeah. And

coming down. Yeah. So these are all the common ones anyways. So so these are all the important services guys as part of your BTP z where you want to run it.

Okay. And when you go to these ones the security. Yeah. Now I'll I'll open

security. Yeah. Now I'll I'll open before I go to the the section tools things you know I'll open to the platform for the questions. Please

please pose the questions to me.

>> Yeah. So so you have showed four types of applications using right you can create.

>> Yes. Yes. Yes.

Will you cover all those four practically do throughout this course? I

mean with use case >> use cases uh see this is what we have know everything means you know let me show you that one also. Yeah it's a good question someone asking. Yeah please go

ahead.

>> Yeah so as I asked right like you you mentioned like there are four types of apps we can do with Joel. Okay.

Navigational transactional analytical and one more thing I forgot. Okay. So

>> yeah I'll show that I'll show that because see on the practical part as you have seen the content I'll be covering on the exploring of the dual environment the configuration and security scenarios I'll show you the realtime reporting

plus dashboards and then one app deployment and preview so in that it will be automatically covered in the app deployment and previewing you will see that how you do that >> all four types of apps you will cover

>> all four types mean it will automatically been done it's not separately being done yeah it will be done as a part of it yeah >> okay so so In this course, do you cover Joel content based and code based

variety?

>> See, as part of that, you know, like on the build code, I'll be showing you low code app creation and kind of visual builder and crude operations on that.

So, and then also on the API testing, you'll do some via postman on that something we can see that that's what I'm saying right on app SAP build you will see the app deployment on the build code only.

>> No, no, I'm asking about content based and code based both will you cover?

Yeah, I'll cover a scenario on that >> along with the custom skills. If you

mentioned about build, so you will cover the custom job skills also.

>> Yes. Yes. Whatever whatever that is applicable because few of the scenarios are there. I'll cover on that. Yeah.

are there. I'll cover on that. Yeah.

>> Hello.

>> Yeah. Tell me.

>> There's a random question from my side like I'm a basis consultant. Will this

course help me like learning SAP Juul because I think this is mostly for coders, Abers and BP developers. So as a basis consultant should I enroll into

this course or not?

>> Yeah good question. See even a basis can also get this helpful because see it's not you don't have to be a functional developer to benefit from this because Juul can act like an assistant for you

for all the system security and performance task as well like you know yeah basis is one of the important in SAP and it is extending to basis as well. So, so you you can easily get all

well. So, so you you can easily get all the system health monitoring, trouble assistance, you know, authorization checks, transports and know change logs, lot of things will be done by Joel. So,

if your company allows you to access Joel Studio, we can build the content based skills also for it and or code based one one also using that S3 within workload status and all these things we can do it. Yeah, it will be helpful for

you. Definitely we can learn it.

you. Definitely we can learn it.

>> A couple of questions actually. Number

one, you showed document grounding. So

document grounding is it simply just you know checking the documents and getting the information that is relevant or will it also check the code in the system and

try to you know get an answer based on that also.

>> See generally this is to connect it your generative way responses on the trusted enterprise sources like SAP nodes KB articles and all these things will be there. So if your document contains code

there. So if your document contains code like web app snippets or Python scripts or something so grounding can still use the text to answer your code questions answer but Juul does not execute or

debug the code by default. If you want to answer you have to read the code from the document because it has to understand it you have to explain it right. So for example, if you upload an

right. So for example, if you upload an A by PT program for a grounded document set, Joel can explain what the program does or where for example you're updating a table mara so it will tell

you where you're updating but it won't run the program to test it or make it for you. So that type of things are

for you. So that type of things are there in the >> right okay so that's good and another question like as part of the course like are you also going to show us like building an agent? Sorry, what agent?

any agent like you know is it part of the course like building the agent because we understand that there's >> no no no building agent they're not covering no no >> I mean Joel studio I mean is it like a

latest feature that they released around building the agents I mean is there any complexity behind that or >> so yeah I got your question in jewel studio generally one second yeah I will

show you the components I'll cover in the session like for example the agent definition you know like I can do at at a skill level how you can fetch data from the grounded docs and you know how you can run the API calls, trigger the

workflows. This will help you that you

workflows. This will help you that you can build it automatically for the content sources and all these things.

Yeah. So you can deploy the agent also.

While I'm showing you that you can I'll show you that agent building and agent deployment which is at the job level not on the different other agents that you want to put it into the it will not work but yes I can show you how you can

deploy the agent that is available in build work zone as part of this because you can deploy the agents in fury launchpad embedded S4 success factors ar these are enments are not there in my

training right away but yes in build work zone whatever you learned will be similar for you to like deploy the same in theory and embedded S4 as well so that will help you on Yeah, this is the answer for that.

>> And is it is it part of the I mean is the course having Joel studio? Is it

part of the course?

>> Yeah.

>> Would helpful you know to also show us the grounding as well. I like how to set up the grounding because it's very important isn't it?

>> Yes. Yes. Yes. Yes. Yes. Yeah. We'll try

to show you that. Yeah. Grounding is not into the content right now immediately but yes I'll try to show you that. Not

an issue. I'll I'll just make a mark on this. Yeah. So these are the five

this. Yeah. So these are the five modules in which Yeah. So the first module I started we covered this part right now. Yes. So these are the things

right now. Yes. So these are the things are there integration points and all these things and the configuration level you will see dual setup for SAP modules architecture AI security for this and then some of the connection testings and

all the so here you will see the configuration security scenarios on this. This is the hands-on that you'll

this. This is the hands-on that you'll get it on top of the module two. On the

module three you'll go with these business use cases with prompt engineering and all the things and workflow automation with zoo. So role

based journey will be there. So all

modules will not be covered as part of this you know role based journey you'll be seeing HR specifically. So you'll get it automatically when I say HR rest all you can practice on your own. So here

this is where you will see understand the realtime reporting plus dashboarding through jol. This is one such that you

through jol. This is one such that you can do this business gifts module and going for SAP build module plus app development. So some of the people are

development. So some of the people are asking questions on this only. So this

is where you will go for low code app creation. I'll show you the agents also

creation. I'll show you the agents also at this level only. So the builder and crude operations and how you integrate with cloud and capm and how you do the API testing. This is covering all your

API testing. This is covering all your app deployment and preview. So this will uh give you all answers of what you questioning right now. And in advanced features these are all the features are there which like you know like how do

you customize recommendations how you monitor and you know how to make the change management all this and all these things you can pass part of this.

>> Yep. when when you say about the role based journeys you will be covering only for the HR and not for the finance and SCM right >> your finance SCM means only app level

right all you can do it the process will be same right the role based journey is it's a very simple thing you can go with with your finance SEM apps also whatever are there I'll be covering as part of

the time restrictions if permit I'll just show you these two also okay >> okay >> sorry sorry kbo I'm still one one quick question on the agentic AI I mean so so

after what you're talking about you are again like talking about creating an agent right because I'm just fixated on this point because we know the future on the agent AI

>> and that has been the biggest question it can really agents work on enterprise applications okay so are we going to build something which is really agentic

here meaning like the system should be able to do the API calls and you know have the enough intelligence to actually take a decision actually so will we be at that level I mean or are we saying

that we're going to go like 80% 60% what level does this course cover actually >> see I'll be covering you specifically on the as I said you know right the instructions how you create agents with

instructions and personality and you know how you integrate that into build work zone and then how you chain them for your flow that's what it will be done so because we have to understand

that you know like in in jaw it only works inside the boundaries reset. So

which is for our regular enterprise kind of thing but it means it's not the same as like a open-ended AI agent framework you not expect in the result so that is not and do something is that what you're saying like

>> exactly exactly yeah yeah >> right right I mean even within SAP if we can really understand okay like maybe between like >> you can understand you can understand better >> yeah thank you

>> okay any other questions guys >> yeah see for the students I mean the candidates who have already enrolled So are we going to continue the course or it will be started from the from itself?

>> Yeah. This is what we are set. Yeah, we

are done. Yeah. One one information I want to share is an SAP is getting the certification for SAP zool also very soon. It will be available. Yeah. But

soon. It will be available. Yeah. But

not immediately but end of the 2025 or 2026 first quarter they're trying to do that. So it it will be available by the

that. So it it will be available by the time. Yeah.

time. Yeah.

>> Hey one question. So I think one gentleman asked about the agent in KA right?

>> Yeah.

So like so will you help us in like creating agent like or how currently other SAP customers are doing are they creating any agents for each client or something like that?

>> See the Jo's perspective the agent is an a persona for which you know have a specific goals and knowledge will be there. So we have to process the user

there. So we have to process the user queries in the natural language. So

where in which either he use your content based or code based both will be there while you're creating an agent like for example if you're going for code base you have to call an API you

have to run an SAP query and all these things will be there so that will be on the code base so with this you have to create your agent so you have to when you are doing this you have to follow

multi- kind of things in your chains as well and then that will be attached to your domain specific copilot in the SAP So that is part. So you can create

agents with your instructions with your content grounding or with your BTP APIs whatever you call it. Okay, that is how in SAP also right now it is getting

created to answer a question. So further

they integrate into which environment is up to their requirement as I said it will be a work zone or fury or S4 or bar success factors lot of things are there.

So but of agent will be same for all the environment. Integration is where the

environment. Integration is where the division factor will comes in there. So

accordingly this will go from there.

>> Sorry. Yeah. One more question like it could be an ignorant or dumb question.

So like what I understand is we are having like other configuration which we do for SAP implementation right like that SAP jewel jewel also comes like without any configuration from SAP out

of the box and then if we get trained in this then we can configure it based on the business needs is it or is it like out of the box itself will have all the integration already available. Yeah, see

to answer your question specifically configuration Zul does not come fully configured out of the box as you said you have to do some setup and

configuration before you go into the environment. So when you provision zu in

environment. So when you provision zu in BTP like in S4 HANA cloud or with zool embedded so you should have the zu runtime is which I have shown to you in the practical part right now today right

so you should have that services the basic conversational capabilities some build NL natural language content will be there so those you have to understand so basically what you will configure is

your connecting of data sources your skills your agents and integration of SAP apps these are the ones which you concentrate on configuration you have to configure these things this will not come to you

by default from the Azour the only studio and other capabilities will come to you rest all you have to do it on your own so as part of configuration you will learn these ones as well >> so is it like more technical because we

are functional >> that's what I'm saying so if you're going for build code it will be technical if it is not on build code build or something it's not technical

it's it's everyone can learn yeah but specifically if there are some developers who are really building bigger agents, bigger things they want to deploy, then it will be full technical.

>> Since you mentioned it's all integrated through within SAP, let's say if you have any data warehouse which is you know combination of SQL and any other databases or maybe a windows or a

shareepoint file server, can we do any kind of integration to pull the information?

>> Uh means all third party are asking >> yes besides SAP. Yeah, there are integrations for Zo as well.

Specifically, the database list is not then. Yes, you can integrate all the SQL

then. Yes, you can integrate all the SQL database Windows services. All non SAP apps are there. But this depends on whether you want the zool to read only

or read plus perform actions because why I'm saying this is if you're going for readonly integration, it needs content grounding. So where you have to export

grounding. So where you have to export data into readable format and connect your things via BTP destination. There

you upload docs into Zul's content based skill. Okay, for example, customer

skill. Okay, for example, customer orders from SQL is there to CSV. If you

want to do it, you have to upload to Z in the Z snippet. If you ask what is the last order for the customer XY Z, it has to answer. So that one you have to make

to answer. So that one you have to make it that is called containing what I'm say read only integration. But when you want code based scale for example that is called read plus write integration.

If you have zool query live data and it has to do the updation of records as well. Then you have to create a codebase

well. Then you have to create a codebase skill in the zool studio. You have to specifically is a complete technical you have to use completely JavaScript python to connect your SQL via JDPC. You

connect to Windows services and then you secure your B2B destination and you have to do it. So both of these are possible.

Yeah.

>> Yeah. I think that is a possible integration because otherwise we need to d the whole server itself on J if it will be taking the space. So if you can just make integration as a readable that would be the ideal solution I guess.

>> Yes. Yes. But but Zul itself does not natively browse a skill. You have to expose it by the API or skill code. That

is a yes you have. Yeah. Yeah. And right

back action should be also have role based control. So zulu does not

based control. So zulu does not accidentally delete data on that. Yeah.

That's what >> Okay.

>> All right. Let's test your knowledge.

Here's a question for you. What is SAP jewel? Option A. A traditional ERP

jewel? Option A. A traditional ERP module. Option B. SAP's AI powered

module. Option B. SAP's AI powered digital assistant. Option C, a data

digital assistant. Option C, a data visualization tool. Option D, a cloud

visualization tool. Option D, a cloud storage solution. Take a moment to think

storage solution. Take a moment to think and when you're ready, choose the correct option. Remember, each choice

correct option. Remember, each choice holds a key to unlocking the answer.

Good luck. Type the correct answer in the comment section. Hey there. Want to

get really good at using AI in SAP? Our

SAP Juul course is here to help. You can

take it at your own pace on our platform. In this course, you'll learn

platform. In this course, you'll learn all about SAP Jewel. It's like an AI helper for work. From asking smart questions to getting instant insights for faster decisions. Our course covers

everything you need to know from the basics to cool advanced features. It's

made by experts who really know their stuff. Your teachers are pros who've

stuff. Your teachers are pros who've worked with SAP tools for years. They're

here to guide you and answer all the questions you have. And don't just take our word for it. Our students love the course, too. People just like you have

course, too. People just like you have found this training super useful. Best

part, it won't cost too much. This

awesome chance to learn is really affordable. Ready to become a SAP Jewel

affordable. Ready to become a SAP Jewel Pro? Sign up on our page now. And for

Pro? Sign up on our page now. And for

more info, check out Zarentex website.

>> So, hi all. Hope everyone is seeing my screen. So, this is your LMS portal. So,

screen. So, this is your LMS portal. So,

this is where you get your server access. Okay. Okay, I think so this is

access. Okay. Okay, I think so this is the materials I think. So they have kept it this is and everything here and then here is your server details. So if you go to the server details you will see

this here. So with names everyone name

this here. So with names everyone name is there here bring the primary details also to me because I'm missing. Okay. So

here you can see here for everyone your zool ID your start date end date of the server is there clearly and this is your access. This is for web DRP and then

access. This is for web DRP and then this is for S4 HANA access for whatever the system that you're going to do that and this is for BTP zool whatever you are going to you know like connect for that and you know all these things you

can do it from here so this is your zool account um so these are three things that will be there for you so according to your name you can go and you know you can just take it accordingly okay as you know the password will be logged after

two to three lo login atoms so please be careful while you're using this passwords okay once you reset your password you can do it. Okay. So this is the one such thing and you all can

access this I think. So if you have any everyone please check this.

>> So how to login this uh web?

>> That's what that's what that's what I'm telling you the first day itself only.

So I'm just putting that in the chart page so everyone can see this. Okay.

Just make this link as a favorites in your system so that you know you can easily go every time whenever you want to go. So this one you can log in. Sunil

to go. So this one you can log in. Sunil

ask. So they might have already given you the details of logging here also. I

mean with your whoever registered with their Gmail accounts right so with their Gmail account they can login into this site directly in the LMS site from there he can actually go into it and they can do that you know whatever the registered

email id whatever you are given that will be allowed for this link automatically if you just click on your link from the Google that will automatically taken it will go to this link just check it out you will get this

okay this is one such thing yeah as everyone has displayed you in the demo so this is your video recording this is my demo First demo, this is my second training come demo both are there in this. So we

can refer this any time and whatever the classes that we are going to like conduct every every class when it is completed that day after 2 three hours the same session will be appeared here.

Okay. And yeah so this is what and this is your meeting links for whatever you want to get. If you go to the meeting links also you can see if you have any issue in joining the meeting link to find you can just go to this page and

you can just or you can just make a favorite of your meeting link. Okay. So

it will show you how much time I'm conducting the session also here completely. Okay. So this is 24-hour

completely. Okay. So this is 24-hour session completely. So yeah, so we have

session completely. So yeah, so we have already started last week this one.

Coming to the curriculum. Yes, I'm going to the curriculum. So yeah, I have last week you know explained Zoho and we gone for lot of questions and everything. So

I have to go for this this week. So let

me go one by one now. Yeah, thank you.

So everyone please just check out their links and if you have any questions please on the link whatever I have just shared to you just reach a support immediately. Okay. Okay. So let me go

immediately. Okay. Okay. So let me go into these topics now. So everyone clear with your LMS portal we start. Okay.

Then Zul let's start the a small introduction and then I'll go to the architecture directly then what is that we have to go for this right. So as

everyone knows and I already explained you a couple of times in the demos as well. So on the zool detailed things

well. So on the zool detailed things here. Okay. So what is the zule that

here. Okay. So what is the zule that what we can do with the zuul? We have

already gone through it but yes let me recap one more time. So it's an advanced generative a copilot. We have already seen that. So which is embedded through

seen that. So which is embedded through SAP cloud's enterprise portfolio within which it will help us to deliver help to deliver most proactively the

contextualized insights you know from different different I can say the breadth and depth of the SAP applications and third party sources kind of things is what thing so zool is

basically defined to help the people to get the work done faster and drive the better business outcomes in secure and complex complained way. Okay, complained

way in the sense widget will always follow the compliance. Okay. So as all everyone knows that you know like similarly like many SAS offerings Julie is a SAS offering on SAP BTP. It's a

simple statement. Okay. So how this customers can use SAP zool and what is the architecture you know we have to before going into server diving into something you have to know something. So

let me explain those things in the class then we will go to the server accordingly on that. Okay without

knowing those things it's there is no sense you know going directly to the server like that. Okay. So for for customers basically you know like this is a basic question that everyone you

know in initial mindset goes with you know how SAP customers can use this zuul how what can they leverage from it you know is it really that worth enough to go ahead into know like making zool

enablement in the organization yes zul as I said it's embedded into various various SAP applications like your majorly for S4 HANA or success factors

you know like your Ariba you know like lot things like data spears a lot of things are there so from HR to finance you know like supply chains procurement customer experiences especially into BTP

platform it was already there available so a lot of things that you can do as part of it so it will be it is like a well accomplished or well established right now for the and the BTP platform

right now with all the SAP business data and business processes so users can simply so what users can do that is the question even if you are know like going for any pre-sales calls or if you're going for Are you an architect or if you

are something because everyone has to answer this question. So every customer will ask you how it will help me. So

simple you know like users can ask questions or they can frame a problem in plain language and receive the intelligent answers which can drawn from

the business data or SAP business data across the SAP portfolio and third party sources. So which is retaining the

sources. So which is retaining the context. This is what they can do. So

context. This is what they can do. So

what is the benefit? I told you uh like we have some patterns and everything last week, right? I'll just show you some of the examples of patterns also.

So, Zool is infused across the SAP solutions. Okay. So, Zool is infused

solutions. Okay. So, Zool is infused with a sense means I mean I mean to say it is embedded across various SAP applications. I said right. So, as I

applications. I said right. So, as I said, Zuul offers many interaction patterns. In the last week, I told you

patterns. In the last week, I told you we have transactional interaction patterns. Okay. We have navigational

patterns. Okay. We have navigational interaction patterns. Okay. And then you

interaction patterns. Okay. And then you haveformational interactional patterns and then you have your analytical interaction patterns. So how this

interaction patterns. So how this interaction patterns also looks like you know it is what it will actually help you on this. Can you tell me like what is the deal breaker like compared to any

other AI tool right because you know these one question anyone can ask because Joel might be more expensive also compared to any other AI tool.

Again I'm not >> making I mean I don't know 100% but I'm just asking you. So if someone asks like why only Jaw right what is the edge it

brings maybe it's SAP 2 that that is totally fine but costwise or maybe some other points you want to drive please please add them as correct >> yeah I'll be coming that I'm coming that

plus there yeah right so so this is what you are seeing the interaction one of these interactional kind of thing what I'm just telling you here one second system was is my screen visible guys I

don't know something Yep.

>> Yes.

>> Right. So this is one of the interaction patterns what you have seen how Google generally know like works for you and how it actually gets the things for you on the interaction level basically you know like I told you on the patterns

level right. So these are the patterns.

level right. So these are the patterns.

So this provides entry point like you know this this is how generally this works for us you know this is what the final outputs also seeing on that. So

this is an entry point for you like you know the connecting your backend systems. So users can perform the crude operations directly from zuul like you know they can the same thing if you can

see this is the changing of address. So

when do you want to change the effect you know it is saying that what is the like home address you know if you want to select this as a home it is making this as home. So these are all called what transaction that you are making a

transaction. Okay. But ensure but always

transaction. Okay. But ensure but always remember that it is not impacting something on the database. Like for

example, if you say people who are in a app or something, if they're making a table, it won't create a table for you.

It won't change the data. But yes, it will get the data to it will get the data that you are struggling to get it into it. So it it might help you in that

into it. So it it might help you in that case. You have to think in that. Yes,

case. You have to think in that. Yes,

Zul might go into the text in the coming future. There are possibilities for

future. There are possibilities for that. But now it is in the as every

that. But now it is in the as every technology as you know in the initial in the crawling baby you know like age so it will be showcasing its initial effects only but later on stage when it

is getting matured you will see a lot of things on it similarly like you know if you're seeing a lot of things on that so here also right now you can see this is in the basic level and you know not basic more much more than that as well

but yes if you want to see lot of changes you know taking control on databases taking control on the accessing security authentication lot of things to do. It might happen in the next couple of years but not

immediately. So this is also in the road

immediately. So this is also in the road map of them. Okay, because we also don't know what actually the technology might well into when it is going into a different turn. Okay, so for now this is

different turn. Okay, so for now this is what you have to understand. This is

some of the transactional patterns.

Similarly for for the same kind of copilads we get the navigational patterns like you know you might ask what is your org details. Okay, you can see your org chart like from success factors how many for the HR specifically

success factors or aribba for processing and samplings all these guys you know they can get the data into it and they can put their questions through it so you can easily get the answers for that as well as you all know teams is also having copilot as anyone have seen that

or I don't know every organization is also using teams copilot now they they're naming something for that but yes whatever the organizational policies organizational data organizational like instructions are there they're

processing through to the team's co-pilot like similarly I'm just giving an example to you so where in which everyone can instead of going for multiple IT tickets you know if you just go through there give you to the co-pilot is answering you it is giving

you solutions it is it is logging ticket on behalf of you so a lot of things are happening there is no need to specially go and login ticket this is what happening in Microsoft teams as of I have seen it might go similar example I'm just you know putting a posture on

that you know like similar posture for you to understand more clearly so in similarly you have the information interactions also So like that you can do where you can get the results of policy related questions, sales orders,

no the finance related data whatever you want to understand. So these things you can go at this level and as I said for the analytical interactions in the similar pattern you will get analytical interactions also which you can enable

the just task kind of things in the sack. Okay. Now it is also recently been

sack. Okay. Now it is also recently been done. There are a lot of work is going

done. There are a lot of work is going on completely not done in the sack as well. So data spares sack have the

well. So data spares sack have the abilities to do that but still not complete abilabilities as of I have seen in the environment. Okay. So this is about your quite open introduction on

the SAP zole and how this works. Okay.

So coming to the architecture. So so

after explaining the architecture I I'll give you the differences how this generally works for you. So one second open this one. Yeah. So some important points what you have to understand from

the SAP ZO architecture is as this is the first thing is this will the ZO is a service it is not a software first of all is a service this is this will run

on BTP environment okay that two BTP in cloud foundry environment so you have two environments like the ka and this one so this is the cloud foundry environment this is one thing you have to understand first of all so whenever

you are recommending to anyone you have to understand that they should have a valid BTP licenses as well to do this.

Okay. And Zul is a and then you have to integrate into the cloud solutions for that. Whatever is it's integrated into

that. Whatever is it's integrated into cloud solution. So, Zuul you can I can

cloud solution. So, Zuul you can I can write like this know can integrate two cloud solutions where in which these

cloud solutions will have your success factors your SAP build work zone BWZ okay your Ariba okay and your CX or now

data spear or you can say the build build code SAP build code so these are all there to go through it and we can integrate and have to use it okay how after integration how this is click you

will see this in the server I'll show you in the class okay and then users can access because as you know there is always a diamond icon this is the standard icon for you for the zool wherever you see a diamond icon that is

for zool that has been reserved for zool actually so that is the one which you can go for the sap user interfaces and all the systems whatever you want to go you you might see this diamond icon zool

and then that one you can easily access from that and you can use your prompts and everything from there and as I said This specifically on the architecture

level zul uses a cloud identity services CAS. Okay. So this is for all the

CAS. Okay. So this is for all the standard SAP authorizations and authentications. Okay. Okay. So before I

authentications. Okay. Okay. So before I explain you how this generally works in a step-by-step manner. So let's see a small architecture as well. So this is how the general architecture of ZU will

be looks like. Let me draw it for you for a better understanding instead of I'm going and you know showing something which was irrelevant for you. So the

type of things I never do. So I'll draw it and show you. This is how generally the zu's capabilities will be generally been founded. So if you see on the

been founded. So if you see on the layered architecture level as I have already told you. So this is your first of all your a ecosystem will be there.

I'm giving an a ecosystem level. So then

I'll explain you on the SAP's BP platform level. Okay. So here it will be

platform level. Okay. So here it will be your basic A ecosystems will be there.

Okay. There are a lot of things are there. If I want to say partnerships and

there. If I want to say partnerships and investments with this including data bricks, Nvidia, Microsoft, you know lot of Google cloud these are comes a lot of things are in a ecosystem partnership

and investments this is one such thing.

So on top of that generally this is the layered systems on which generally all co-pilots will exist. This is AI foundation layer will be there for them.

So wherein which this foundation for us we have on the BP platform as a service as I told you now. Okay. So a foundation layer for all the foundational work that you want to do it on the AA that will be

done through a foundation on the BTP layer. Okay. And then it comes under to

layer. Okay. And then it comes under to your embedded capabilities because once you are on the foundation you have to embed whatever you want to do something for the that co-pilots or whatever

you're going for. So that embed capabilities will be there. So that one you will call it like there will be a lot of things are there as I said S4 success factors arball these things

comes under here. Okay, I'm just mentioning two three. Okay, and then along with along size with this you can have your customized copilot applications also here. Okay, or else I

can write a customized AI applications.

Okay. And then on top of this Z will be there that means as a complete serving here. So this is your thing that it will

here. So this is your thing that it will actually works on it like see as you see this is going towards you know like the moment when you when zo analyzes if the

user prompt is relevant for z scenario catalog that catalog contains metadata of all available scenario I'll come to that now so you have certain catalogs for that you know and then those catalogs you have to understand so based

on that the zo will start you know you know like producing the required details for you and you know whatever that you want to put it in the front end it will make it But yes, as you as Zuul is

providing out of the box and natively integrated in SAP's cloud applications, it will preconfigured with certain content that is always active right away for the customers. Okay, with all the

configuration efforts that they wanted.

So, so this is one such thing which how this will generally been scoped up when you're doing that. But in SAP BP internally how this look like? Let me

put it for you also so that you'll get a complete idea how this generally works for you. Give

for you. Give >> yeah one second one second I'll open to the question just give me let me complete this yeah so if you go to this so this is the one you go to so this is

your basic SAP HANA cloud okay so at this layer even datas also now existing in the new recent innovations because for people who are on the business warehousing and all these things if they

want to make it out for the zulu they are actually you know embedding like this so this is one such thing where in which you will be having your underlin arch Arcture I'm telling first of all so

you'll be as I already out quoted in the last session we have two things will be there vector engine and knowledge graphs will be there so these ones will be there in your system like this you know

this is in the hana cloud under underlin database you'll have these two things this is your vector engine and this will be your knowledge graph okay so this is

the your basic architecture under which under on on top of that you'll be having the generative a hub this is your generative AI hub okay where in which you'll be having all this in the

generative AA hub you will be having all the trust your orchestration because a lot of orchestration you will do as part of that and access access and access

controls will be there these will be there so these will be continuously talking with your data layer this is your data layer wherein which this is

your data layer that's a middle layer another data layer will be there so in this data layer What it will contains is all your cloud ERP data. Okay. Your CRM

data, your spend data for Ariba, spend analysis, HRM data. So all these data will be there in this. So there will be a continuous interactions for the system like both ways. You can see here this is

a both way directional things will be there. So like this it will continuously

there. So like this it will continuously get the data and put the data kind of things here. Okay. So this is where

things here. Okay. So this is where generative ahub will help you on this.

So once generative a hub you know like start doing this. So again this generative ahub will be on where it will be under the BTP platform. If you can see this is again a bigger picture. So

this is again under BTP platform. This

is BTP under that only this generative aub will be there. So this generative AI hub will have two things. One is I'll draw internally. So this is your A core.

draw internally. So this is your A core.

Okay. And second one will be your development tooling agents or dev tooling agents. Okay. So this will have

tooling agents. Okay. So this will have continuous interactions with the BTP system here. What happens here in the

system here. What happens here in the dev tooling agent? You'll be having all your generative ahub in SAPI launchpad all the libraries you know these things will be there and it will continuously

go through this thing and it will go through trust the trust will be there wherein which you can see this one the trust will be there and through the security access and all these things it

will go ahead and again this will just communicate with the AA core as well.

Okay. So in the AA core you'll be having all the SAP build foundation models will be there the third party language models open source models you know remote foundation models these will be available for that. So whatever you want

to generate that you can generate that you know as part of the customization or standard ones and all these things and after once you are done with this then you can deploy them. So for deploying models and all these things you'll have

this one which is your ZO service for the SAP B2P level. These are all SAP applications. Okay. So these

applications. Okay. So these

applications again have separate layers will be there at the application layer for as I said as I explained for the data layer you have cloud ERP CRM data spend data HR and data like this you have separate separate things which you have to make it for the application

layer. Okay. So customer will be always

layer. Okay. So customer will be always having access from where customer will be always having access for this layer directly because it is it is the secure layer where he will interact. So this is

where user or customer or partner apps will get into this is where user will comes into picture. he will directly go to the BTP platform. From there he'll get all the relevant information for this. Okay. So this is a more enhanced

this. Okay. So this is a more enhanced one whatever I have just told you because as part of copilot this is accessible across the entire SAP cloud

solutions portfolio right so including your S4 HANA etc etc. So you can easily spot this ZO everywhere. So it will be if you're using the latest version of

SAP solution with ZO integrated so you are really good to go because you don't need to update anything but you but if you have not you have to update that. So

SAP has extensively analyze all the user interactions you know for the mostly most frequently performing task and has optimized this for the task management.

Okay. So 80% of all these commonly used task now can be achievable by zone directly embedded with the cloud applications. Okay. So this is the

applications. Okay. So this is the architecture where generally it will help you. I want to understand so that

help you. I want to understand so that you can understand this clearly. It's a

very very still more digger and deeper we can go it lot of things will come but on a top Hawkeye view I've just given you for a better understanding so that you can understand you can visualize as okay this is how the Z wheel works on.

Okay. Yeah. Someone is asking question please go ahead. Yeah.

>> SAP and HANA cloud is it the same as the SAP you know business data cloud and as it's called in these days.

>> Sorry what is the question? Sorry I'm

not getting can pass again. the the SAP and HANA cloud is it the same as the SAP you know business data cloud I think it's called the business you know data cloud if you

>> that is DWC that is different that is for >> oh is it >> oh it's a DW different >> yeah that is for different operations where for the data spear and yeah BDC all these things comes into picture yeah

data cloud is all together yeah that's a customer data platform wherever you generally go for all the data management so HANA cloud basically you do for data Databasing analytics for all the

enterprising data level whereas in data cloud you specialize for the customer experience you know for all the customer privacy personalizations you put it there these two are different >> okay so the sack you know comes from there

>> stacks come from there only yes yes yes yes >> stack and comes from the BDC is it >> not BDC specifically it is for the data warehousing cloud layer not not stack

not BDC's BDC are great separate >> okay okay >> okay now another one also I want to just put a comparison guys someone has also asked me so yeah so why zo is productive and different from other co-pilots is

what I want to explain you because this is one of the question everyone in this crowd has to answer if they're going out for the any customers also because customer will ask like why Zo is productive and why it is different from

other a copilots yes I can put I have already kept a comparison in my demo also on that but yes I just want to tell you few things see first of all zo is let me write few points that can help you on this the first important Same

thing in this as I already mentioned every time mentioning this this is the native to SAP ecosystem okay so other co-pilots if you see Microsoft service now assist is there Salesforce is there

okay people who are on there because they are powerful but they are generic assistants okay so zul is built directly

into SAP BP and SAP applications okay and so when it is saying when I'm saying this door is directly between SAP BP no extra connectors or Middleware is needed

which will eliminate lot of complex hierarchy needles there. Okay. And it is a out ofthe-box things I have told to you because SAP data models are there like you say CDS views, universal

journals, HR data structures, procurement objects. I can give the list

procurement objects. I can give the list big because this is all out ofbox awareness office there for all these data models. Okay. So now if you can see

data models. Okay. So now if you can see zero setup for SAP customers instantly usable where business process can happen. This is the one of the highlight

happen. This is the one of the highlight that you can do because of native to SAP system that is the productive element that you can make it out. So another

important thing is this is you might see when you see the co-pilot you might ask hey this is just a chart chart kind of thing right you know what is that business process I can get this is a business process enabled as well it's

not just a chart aware of kind of thing okay because other co-pilots they mostly knowledge question and answers or document assistance if you can see that

clearly but juel here I can write a a formula kind of thing here a jewel is transactional plus analytical plus I can write decision support. These

are all combiningly together. Oh this

name okay let me write this. Okay so

zulu is this one transactional plus analytical predecession support is what it can do. So it can create a purchase requisition. It can approve a leave

requisition. It can approve a leave request. It can fetch your overdue

request. It can fetch your overdue invoices. It can ask you can ask in any

invoices. It can ask you can ask in any language of it for whatever the language supported. These are all it can do.

supported. These are all it can do.

Okay. I'm not sure whether other co-pilots can do this or not. As of I know they can't do it but they just give you the answers for that. So you have to understand that your work is getting

done on Zo also at some aspects at some things also wherever other co-pilots just can answer you what they can what someone can do on something they can just guide you. This is the very thick

line difference you have to understand because it is embedded in SAP workflow context. It knows the company code

context. It knows the company code concept. It know cost centers. It know

concept. It know cost centers. It know

approvals. it no argu units a lot of things are there so jewel doesn't just answer things it actually executes your business transactions this is one of the

very important different thing other co-pilots can't do where Juul can do okay and always remember that is into the SAP environment if you ask something hey zu go and write my python code no it

won't do okay into SAP because you are working for SAP in SAP it will do yeah might be as I said in the next coming years it might do for certain other things as well but currently not right now. So this is one such difference you

now. So this is one such difference you have to understand to compare the co-pilots and most co-pilots are app specific. If you consider your Excel or

specific. If you consider your Excel or your Salesforce Einstein or some other cooperates who are considering in the current market those are all completely

application specific only but Joel is crosslication specific okay so you can start in finance you can switch to HR you can jump to procurement all in one

conversation you can do it you don't need to open multiple conversations for multiple charts for this okay and it will always maintain context okay for example Hey now filter my report for

Asia Pacific only it will do across all the apps it will do that okay so because of this is cross app specific it eliminates lot of application hopping

and what happens you know it's it's like a it will provide a single conversation layer for all the enterprise process okay that is one of the very good difference that you can find in zoo

compared to other co-pilots in the existing market okay And very importantly you have embedded a recommendations are there in this. This

is also one such thing which you can see. Okay. So as Zulu is integrated into

see. Okay. So as Zulu is integrated into SAP's trained A models. You can get all the supplier recommendations. Okay. You

can get the cash flow predictions in the finance for current year for the next year for planning purposes. You can get the attrition predictions for success factors. How many can leave the company

factors. How many can leave the company in the next couple of months or next couple of years. how much you have to know like recruit kind of things you know these kind of predictions based on

your existing data and you know evaluating the past trends Zulu can recommend you okay because the same thing you have to do it on your own

manually or if you remember if you go for any other kind of dashboarding softwares they also need the data without data they cannot predict because it is internal to a SAP it we easily can

you know do the predictions and it will always happen to make some productive or worthful predictions to you to make believe it or to make trust on it. Okay,

because the data is our own. So you

don't need to go for any third party soft. So the copilot can help you out.

soft. So the copilot can help you out.

So other copilot generally what they do they rely on the generic LLM reasoning let me tell you. So because of this what happens they have the predictions that will be on based on pure only on the

data but not on the other factors that consider in the environment. So that

might not be 100% that might not be 80 to 100% true but yes they might be true for 60 to 70% only but zu is 90 to 95% specific when compared with some other like what are the surveys that has been

done it has given the predictions also properly in the in the areas of finance you know like success factors and other uh uh areas where predictions are needed

for planning purposes okay because by Juul uses domain specific AI along with the hybrid let me this is very important for Whereas other other copilot the

general they they use general generic LLM reasoning only. Okay. So this is how the business grade a tuned for enterprise KPIs will be happening not just text summarization always remember

guys there is nothing called text summarization here it will go beyond to that zu okay and then very importantly compared to other co-pilots what is that I have is security and compliance in the

zoo. Okay. So as you other co-pilots

zoo. Okay. So as you other co-pilots they rely on external cloud ALMs. Okay, LLMs because because whenever you are depending on the external cloud LLMs,

there is always the higher risk for getting a regulation in the industries as well. Okay, that is always been

as well. Okay, that is always been there. But yes, forever we have a strict

there. But yes, forever we have a strict SAP BTP governance is there because it's on on that layer. Okay, so your data will always stays within the SAP tenant

not sent to external by default. Okay.

And the compliance whatever we follow as you know in SAP DTP we all follow ZDPR sock to industry regulations all these things are there. So it will be automatically followed. So you are

automatically followed. So you are strictly under the security and compliance layer following the international security guidelines as well. Okay. So enterprises can adopt

well. Okay. So enterprises can adopt Zuul without compliance blockers. I can

say this statement so openly. Okay. That

is what we have in this. And other

important difference, last important difference when compared to other copilots, what Zuul have is Zuul have the extensibility within the SAP build.

Okay, so extensibility within the SAP build means what is this? So Zul is not a closed assistant, right? So developers

can extend whatever they may want. For

example, I want custom application triggers, I can go for build apps. I

want workflow approvals, I can go for business process automation. I want

custom business logics, I can go for CAPM services or APIs. So all these things are there. So other copilads what they are they are having limited extensions or they might require third

party platform integrations. It's not

that they can't do they can do but yeah they require the third party platforms but yes Zul is an enterprise edition completely having the extensibility which is directly tied to all SAP

development tools as I said no. So it

has extensibility with the SAP build platform as I said build code is there, build apps is there, build work zone is there, we have all these things in BP which has already been done. Okay. So as

a whole as someone has asked me or I want to drop these differences to you.

So other a copilots they are yes they are great at knowledge great at giving the good chart interferences or inferences to us and they can give you

documents but SAP zol while doing the same it is great at running your business which is very important running your business is what everyone looks at okay when I'm saying running your

business what is that it will query it will automate it will recommend it will execute directly inside SAP these are the important things it will do for you as part of the other co-pilots whatever

it can't do clear everyone the differences for the co-pilots >> so yeah please >> sorry go ahead please >> yeah okay so you say like a SAP jewel is

more like SAP native specific right for example I'm going to ask a a question so maybe I don't know whether this can be possible or not I have a sales data for example in my system right so to has

definitely an access for the sales data >> so and my I have multiple customers. One

specific customer always like ordering that like a one two three parts like in some specific month maybe like in some specific intervals. Right? So if we can

specific intervals. Right? So if we can ask the question to Jude hey can you tell me that if this what this customer

a can buy this product maybe in month of 2026 September that's that uh jul can answer for that question based on the existing data

>> predictions are happening it it can do it can do this >> you have any specific models we it will models are available >> that's what I'm saying jewel is not just this is what I told you jewel is not

chartboard. It leverages your AA models

chartboard. It leverages your AA models in SAP data. So in S4, HANA sales or CA system, Zulu can look at your historical order data for a customer. It will

identify your patterns in the interval.

For example, you said every 3 months customer orders 100 units or something.

So it will generate a a based recommendation like you know based on the past when you ask something question like this, it will answer like this. So

based on your past year of purchase frequency this customer can order this this this in November or he can put this if he's already ordering something you want to make something on that he can do

that one as well so you can ask directly z it will response because I said it is quirying applying and showing you these these three things it will show you >> okay >> yeah it will happen >> okay yeah thanks

>> okay uh ko one question right so maybe if you want to take this question later it's totally fine but see what I understand by Joel right the brain behind the Joel will obviously be an LLM

am I right or wrong >> yes yes yes >> like again there are different types of LLMs right like you know Google as Gemini and all and AI launchpad I I believe you can also select whatever LLM

you want to use and SAP will charge in forms of tokens and all of that so my question is when you say Joel understands SAP right Joles understands

and it is basically trained on the data uh of SAP right so are we saying that it is it is again like LLM understanding it >> no that's what I'm saying this is not

just completely correct whatever you have just it's not only LLM you will use LLMs but not only LLM let me tell you

that it relies on LLM for what for your NLP kind of things like converting your user prompt into SAP queries and then keep your flow across the apps but as I

said Zul is a hybrid architecture It is not only LLM I told you now also here LLM plus it has all the BA business a core with services plus SAP data model

this is what the combination of Zul brain is as you have as the brain I'm just giving brain so zul brain is a combination of your llm plus business AI

plus data models so your LLM will only gives you the language skills similar to your open a gpt and all these things but where when I'm when I'm combining this

with PI business A and SAP data model it will do additional things like time the time series forecasting or the recommendations or you know like risk an analysis demand forecasting these are

all can be done because I am making the true business failure and whereas if I have to because zul doesn't hallucinate data it will query it so where it query because we already have the standard S4

HANA database we have success factors you have HANA cloud so all these things It will uses it will uses that and it will put you in in the like a right information format other than other LMS

too. Okay. So it won't rely only on LM

too. Okay. So it won't rely only on LM is the answer. Pure LM is prone to hallucinations. They can make up

hallucinations. They can make up numbers. But yes, SAP can't risk wrong

numbers. But yes, SAP can't risk wrong invoices, wrong financials because it is we are dealing with data directly. So

you should be made more careful when you're doing such thing. It's not some kind of play here. So you will always combine along with your SAP guardrails as I said you know all this AI ethics data privacy all these things as well

accordingly it will put your data into the system for what you are going for querying on that okay >> okay that's great and one other point actually when you sorry I'll just complete this one so when you said

security right >> so does Joel also understand who are you as a user look at your user profile and give back the data only as per your user

profile Yeah, why not?

>> Meaning meaning like for example, I am like a sales rep. So maybe they don't want to show me the financial GL tables and all of that. So can Joel really understand my user role and do that?

>> This is the one of the biggest difference buddy you know like between SAP zu and general copilots like charg does juel doesn't just respond to user it actually knows who you are inside the

SAP system and it enforces the security personalization. For example, for

personalization. For example, for certain tables where you are not relevant for to see the data, if you're asking, it will simply say no for you.

That is where that's what I'm saying.

Identity and authentication where it will works. It will works there. Zool

will works. It will works there. Zool

runs inside the SAP BP. It inherits your user identity from your IAS. Okay. So,

because of your company when you open ZO, it already knows your username, your employee ID, your roles, your authorizations across the systems. So if you're a sales manager for example, Zuul won't show payroll HR data because you

don't have access. It will stop it.

That's how it works.

>> Okay. Thanks.

>> So you said like some Jul is also using LLM for like a to make it like as a natural language or something right. So

the Juul uses like any open LLMs or meta LLMs like they are using their own LLMs >> means I'm not understanding that means SAP LM you're asking >> like is it how the JL like does SAP has

any they have their own LLMs or like like we have LLM like a meta LLM something so is that SAP June is using

third party LLM to process these data to converting into a natural language first or like they are using their own LLM Right SAP no actually see does SAP have

its own elements no I can say simply answer is no it's it's not a J GP step element instead SAP is providing domain specific modeling here as I said in the BTP that is the reason we are getting

the A model integration there so and yes it might use the external ALM like open AI you know like safely inside the BP okay as I said this is LLM agnostic

which is a combination with your SAP data grounding and all the enterprise guard is there on that. So SAP don't have any know like acquired or you know like own LLMs there. So they're working

on any different AI layer concepts. That

is how this is working on.

>> Yeah. The reason I'm asking this question right. Okay, I'm going to put

question right. Okay, I'm going to put in the chart >> as a company like okay give me Apple can purchase this product on like

maybe in previous history right >> so we are exposing my customer name to Juul if Juul can send that information

to third party LLMs so then you you know that right then the third party LLM know that okay this customer is is taking the product from this company So right that's like a a sensitive data right

that's what I'm asking >> I got it that will not happen because that's what I'm saying all the third party interactions or integrations are happened they will be taken more comp

know like importantly most enterprise customers ask exactly you know like what if my SAP goes to open a other ALM providers that is what you are saying your your question is also like that >> yeah like yeah the main thing like the

question can be converting into an SAP line >> no no no by default by default zul does not expose SAP data third parties. If as

you said if external LLMs are used like open AI only intent level info or I can say a more technical term like sanitized queries they may go out never raw

business data never your raw business data will be always secured. So

customers have full control to restrict that as well as part of that. So that is where SAP is ensuring no data is used for training or storage by the third party. they will completely restrict it

party. they will completely restrict it only internal to SAP that will be happen. So your third party will remain

happen. So your third party will remain closed. So never it will get shared for

closed. So never it will get shared for the any other things as like you can see the charging right away. It will not be the case. This is internally to SAP. So

the case. This is internally to SAP. So

it will be in SAP only. The third party will never be shared for that.

>> Okay. One question here. Yeah.

>> Yeah.

>> You said that you know Joel is ready to go you know without any setup. However,

we still need to do the grounding isn't it? the knowledge you know grounding you

it? the knowledge you know grounding you know once we activate the jaw isn't it for it you know to be able to understand the business and context and the processes and things like that you know

of the business >> correct and that's the most important part isn't it so we have to re still have to expose it you know to our shareepoint you know processes you know

through signavio or whatever >> it's an internal SAP you're exposing right you're not exporting this third party what is that I'm not I'm not getting a question here >> yeah Yeah. So we still have to you know do some setup is it before we can use the jaw.

>> Oh that is a very limited it's very simple setup. Okay.

simple setup. Okay.

>> Okay. Okay.

>> That is not a huge configuration. Very

simple setup.

>> And for the jaw lab you can use you know from several LLMs isn't it? You

mentioned here you know hybrid in LLM.

Does that mean that it can use you know several available LMS?

>> Yes. One of the jaws design principle is unlike other corporalates these are it is it is like LLM agnostic as I said okay so it is non-lock to one LLM so you can or that is what in the architecture

if you remember I have given orchestration that is what I'm saying that is where the block will use for you this will orchestrate across multiple LLMs depending on your tenant setup >> again your customer choice will be also

there these all things will be there okay so how this works is your Joel orchestration layer decides which model to call always in SAP BP specifically

for a language understanding you might use open GPT for summarization you might go for Azour open AI or Google Jimny for SAP specific again you have to go for bypassing all these things you know

these all things are there so like you know you have to think the jeuler that chooses the right brain for the right job that kind of thing okay it's always

a customer choice multilm is always useful so so you can work with several LM As I said it's agnostic. So through

SAP BTP orchestrilation layer you can do it that's what the answer I can give it to you. Okay clear guys everyone

to you. Okay clear guys everyone >> I have two questions please go >> first thing is that you told me you told us that uh it won't has hallucinate. So

is it like like we can say to the management that it's a 100% accurate it's like generating a report out of your SAP or using SA like SAC

>> because when it comes to any you know AI systems >> somewhere on the around they you know they get stuck and they give you some wrong answers.

>> So we can tell to the management that it is 100% accurate.

>> Is it correct?

>> It is correct. Juul does not hallucinate raw data because it always pulls from SAP trusted back end but it's not 100% let me be open and frank here it's not

100% perfect because interpretation can go wrong if queries are vague that is also there because I don't know whether what if query is 100% good your data

100% good so predict predictions here are probabilistic and not certain so as accurate as your SCP STM data but not as crystal ball for your future insights

like that I can where accuracy 100% data retrieval transactions where accuracy is there you can trust in zone less than 100% because your forecast intent understanding is always unpredictable so

it can be 95 to 100 in that case okay I'm not saying it is not perfect or 100% accurate it is but it all depends but yes as you ask me good question there are some things where it is not 100%

perfect where means in the language interpretation if you phrase something ambiguously jou might misinterpret intent for example I might ask hey show

me top customers it does does it mean by revenue by order count by profit margin what is that you have to tell it to zol if not it will show something top customers and if you go the same data

with your management that might go wrong so you have to give clear that is what I'm saying language interpretations are not 100% perfect and yeah >> that's understood yeah that's very clear because when it comes to hallucination

though the question or the car is correct but the answer will be ambiguous so that was my question I think you clear the point. Second thing is that when it comes to integration part is

there any advantage if you have like you know or difference between onromises landscape and also like comparing with the private cloud I >> mean on onrem means on-pre zel you're asking

>> no I'm saying if you have landscape your SAP structure architecture you have it on promises on your office in at your desk I mean in the office and in other case if you are having you're using SAP

or AW or any other I mean the public cloud to make the hosting of the whole landscape. So is there any difference in

landscape. So is there any difference in integration point accuracy point I mean response or there are something which will be additional or here we'll be avoiding like if it comes to integration

part >> right let me ask you first question onrem versus cloud if your enterprise if your enterprise wants modern a features

quickly with low overhead cloud z is always best as we said the s400 cloud SAP bp and all these things zul is still available onrem kind of scenarios where you can integrate for S4 HANA on-prem

kind of things but all the limited limitations are there where it requires the BTP if it is on-prem I'm saying for you it requires the BTP integration to connect your on-prime system to data to

Zo and realtime scenarios will not work because APIs cannot be exposed properly if APIs are exposing only few can work that to having some problems with it this is what the practical problem I

have seen and you only get Zol for your connected use cases if you're on primment because it It is not full suit of cloud AI enhancements. You will have some problems in accessing finance, HR

operations as well. Okay. This is what you'll get in the on-pre when compared to cloud. Cloud has all the advantages

to cloud. Cloud has all the advantages as you already know that I don't want to reiterate that. Yes, on hyperscalers

reiterate that. Yes, on hyperscalers like you have asked me on the AWS Azour and everything. Yes, SAP BP can run on

and everything. Yes, SAP BP can run on hyperscalers like so your Zul tenant lives in the cloud region also and you can still control the a orchestration and security things for that. So no

difference in accuracy whether your tenant is on AWS or GCP or Azour whatever it might be your jaw accuracy will always depends upon your SAP backend data quality and your provider

configuration whatever it might be open a or anything whatever it might be so these are the two factors it will affect but not your tenant that is going to affect clear >> yeah clear clear thank you

>> I was told that hosting on Azure is you know cheaper compared to you know hosting on the SAP you know p you know private cloud. Is that correct?

private cloud. Is that correct?

Especially >> posting on >> hosting. Hosting

>> hosting. Hosting >> ah hosting. Okay. Okay.

>> Hosting B2, you know, I mean B2P on Azure is cheaper compared to you know SAP private cloud especially you know from a you know from a B2P you know perspective. Is that a correct

perspective. Is that a correct assumption?

>> This is a statement you have >> from a cost perspective. Yeah.

>> Yeah. I I saw in my career you know in my recent interactions so many customers bring this up during migration discussions because SAP private cloud you call rise with SAP and hyperscalers

like whatever you said Azour uh they sound similar but yes the hosting cost when you're specifically asking raw hosting on Azour is cheaper than SAP correct >> okay but SAP

>> especially if you're a beginner business you know >> yeah but you if you self-host on Azour you must arrange again all these things will be there but for zone there is no functional difference just TC1 support will

difference should be there yeah >> no >> yeah yeah because if you want some TCO customiz TCO tables or something for that you know when you go into it I'll tell you simple thing also because as

you have asked me in your SAP private cloud which have higher monthly cost which is predictable billing in Azour whatever I have seen is your lower infra cost but there are many hidden ops and manage services are there which can add

up that you might see in the building that you know in the Azour you can see that I I can say for customers who want one contract SAP can takes care of everything that that kind of scenarios

you can go for SAP but customers having with strong IT and SAP basis teams who can have a cost sensitive strategies we can make it out then they can go for direct hosting on this is the hosting

difference I can do as for uh current theme right all right guys so >> okay Jo use domain specific AI means is this something in the B2P platform you

are saying or is this something integrated with the other copilots and all this? So when I you when I said that

all this? So when I you when I said that Joel used domain specific AI it it I I mean that it's not a just generic like like GPT but it includes the AI models

that are trying for SAP business use cases like you know where your jaw uses all the domain AI for analytics procurement HR all these things will be there so that is the answer nothing but

>> okay one last question so we have I don't know like is it appropriate like you'll be able to answer it if not we have a setup which is you know we went with SAP private cloud

>> so everything is with SAP and you know when it comes to administration basis it's all taken by them we just you know it's like a office 65 setup basically so

when it comes to jaw so like when you want to make integration fine tuning or anything will it be done from our side or it will be from their side because SAP did not say anything yet so if you

have any experience or any kind if you can add any value that will really help Their side means you mean SAP you're saying hello >> can you please repeat I I missed the point

>> you said their side you are you just told me there means what SAP or third party >> SAP SAP yeah since since it's completely taken care by SAP it's a private cloud >> okay fine

>> it's it's a private r right setup it's a private right set setup >> yeah many customers ask this also see when you see SAP for this kind of things you have it will maintain your jo

service up times and down times it pushes your features and it will ensures the complaints when you go for private code on these things from you. What you

have to do is you have to decide which modules you have to access. You have to make the management of your roles and authentications and your extension of Joel use cases. You have to do it on your own because since you are on

private load SAP manages the platform and Joel service itself because you still need to configure some roles and role specific API CDS views. This is

your part integrations to your apps.

Other than that rest all will be taken by private cloud.

>> Okay. Got it. Okay. Thank you.

>> Yeah.

>> So, so cable so we have to let them know what all modules we'll be using.

>> Yeah. Yeah. Yeah. You have to decide right because many modules are there. It

can't do for every module right. So you

have to mention to the IT you know you have to you it will do it not you it team will come into the picture they will help you in this integration. You

don't need anything. People who are functional, people who are pure technical, people who are at business or consulting there nothing to do with the integration part they can just use this.

How to know how to use it? What can they can make out of it? Other than that who can the IT team integration is not your part guys. If people who are already in

part guys. If people who are already in basis they can do this but other than that they are not required. Integration

is their part.

>> So the more the let them know >> yes you have to let them know that simple integration will be there. There

is integration document which was given by SAP. They have to follow it and they

by SAP. They have to follow it and they have to integrate it. That's it. So rest

all you can do it. Yeah.

>> Uh sorry yes or how it is how does it goes?

>> Sorry. Sorry your question is fast. I'm

sorry. What is that?

>> Yeah I'm saying the more the module integrating so the licensing and the payment will be depending on that or it is how the costing goes with the with the you know when we integrate the zone.

>> Yes costing will work accordingly with the integrations but not on the module specific here. I'm as I'm as I'm seeing

specific here. I'm as I'm as I'm seeing right now because Zo itself is a base licensing. So you need a base ZO

licensing. So you need a base ZO subscription no matter which modules you integrate first thing. So if you only use S4 HANA plus ZO you don't pay for Aribba Z unless you integrate for Aribba. If you are integrating Aribba

Aribba. If you are integrating Aribba yes you are going to pay for that. That

is the block statement. So if you are adding success factors or something then the pay might increases but yes the consumption you have to understand the consumption is based on the Joel queries

per month will be there the consumption billing will applies there because if your jo queries involve LM usage LLM usage so SAP will charge per interaction

per API call per bundle like this so how many because on as of I have seen 10,000 Joel queries per month is included in one bucket so if you cross that your billing will start so there are some

plans for that. So yeah that is there you have to understand >> exactly and that's you know very important name you know to understand because you know that's what I have heard as well if you are a large in a

business and if you you know processing several you know you know when large data volumes and things like that the costs can you know 10x I have heard you know you know from you know I mean

businesses that the B2P costs you know have 10xed you know their plan you know costs and that was a disaster. So we

have to be very specific you know when we are discussing >> right I'll tell you that cost I'll tell you that >> especially when it comes to the end users yeah >> yeah let me give because everyone has to know this let me let me explain this

here also this one see this says SAP Zul has a base subscription okay so base subscription means zul is licensed as an add-on service in the SAP BTP so it

covers your tenant setup orchestration layer security and everything so it is included in rice contracts as optional add-on also okay this is So next what comes is your key cost

drivers. What is this key cost drivers

drivers. What is this key cost drivers you have to see is your user licenses.

I'm just giving a breakout for you. So

user licenses and number of employees you are assigning to the zool access for the zool user role. That is one such thing. And the query volume this is one

thing. And the query volume this is one of the important because all the NLP things each request comes from the BTP credit. Okay. So let me write this also.

credit. Okay. So let me write this also.

NLL your each request comes from BTP credits you have to be very careful this if you exhaust your credit you have to buy it again and then another driving

factor for your cost is your integration footprint where in which see when you connect S4 when you connect Ariba doesn't have a separate per module fee

okay that is not there when you connect not there but you will have a cost when you start doing the API calls and other queries That is where when your data

volume is increasing in this your cost might increase but to that too if you are in a hybrid plans or some plans you have already some calls which have been automatically created but yes if it is

crossing that you might have it okay and one of the other key factor in the cost in Zo is extensions if you train or if you deploy the custom AI model as a core

or launchpad they will automatically consume the additional credits so there also your cost factor will be there these are all the key cost factors For example, let's say what do we call the small setup. I'm giving you small

small setup. I'm giving you small example for here. A small setup here.

I'll give you for example my my bucket is finance. Let's say I'm in finance

is finance. Let's say I'm in finance now. I have 200 users. Let's say okay.

now. I have 200 users. Let's say okay.

And I do 10,000 queries a month. I'm just giving an estimate for you. So here you will be having your base jaw subscription. Okay.

Plus you have your limited credits.

Okay. And whatever the additional will be there this comes under your predict predictable subscription. Okay. So this

predictable subscription. Okay. So this

is what you can do for a small setup.

For larger enterprises you might increase your users. You might increase your queries per month. Then you have to go for larger credit pools. There will

be possible volume discounts also that time if you're going for large. Okay.

And rise bundling is one bundling. I

know that in SAP jaw. So in rise bundling what happens? some Joel

capabilities may come as a starter pack for you but the scaling beyond that will have requiring the additional crates for that that's what I'm saying there are some plans for this yes key cost drivers

are there I'm not denying the statement but yes there are some plans based on your business setup your plans will change okay and if you are using in limited then it is always like under the

billing zone so you don't need to worry about so you can control always cost here by you know like your roles unne Unnecessary jol you have to not create and quiry usage in BTP corporate you have to monitor it that is very

important even for labor board zone in BTP when we are you know handling the BTP customers also unnecessary lot of piring will happen so because of that the BTP volume will increase and they have additional billings for that like

$50 $100 like this so always a BTP administrator have to monitor the BTP cockpit the usage removing the unnecessary users roles all these things might help you know this monitoring is one such thing which you have to do for

the cost control Okay. So these are the things which have to consider while going for the costing in the zone.

>> So did you include the cost in the limited credits?

>> That also comes. Yeah. Yeah. The in the integration AP call that comes auto automatically.

>> Okay. Thank you.

>> Okay. Because as someone has asked the the basic question we started with cost is not per module cost is but it is per tenant plus usage. That is the answer.

Someone has asked me that right. Is it

for per module the cost increases.

>> Thank you. Thank you very much. Yeah.

>> Yeah.

>> Thank you.

>> Thank you.

>> All right guys. Yeah. All right.

>> Last question.

>> Yeah. Please.

>> Now when you mention the integration will be done by the IT and basis. What

exactly our role AJ when you're running this? What will be our role in the

this? What will be our role in the system?

>> Right. See this is your role means you know it generally they enable your subscription they set up the connectivity they configure roles they expose the API and whatever they want all these things will be there. But as

our in the sense I I hope you're a functional guy. So functional people

functional guy. So functional people have to define the use case. They can

prompt uh they can they can design the prompt uh and validation like functional team can you know like test the queries like you know like for example show me the revenue by company code on this year

kind of uh things you have to validate and you have to define which role basically to get access to which Joel capability like you know if I ask show global revenue it will show to everyone

it's a sensy data to everyone right so it is that you know where sales rep only can see the own customers so like this kind of things functional has to concentrate basically very importantly

use case definition and prompt design and validation of it and business user authentications and validations these are what you have to do as part of the functional

>> so who will do this query in the back end like suppose you are putting the query like give me the revenue right in the back end they will run some some of the process right we like in just saw

somewhere that key they in dual studio they make AJ like what exactly they use where I have to go and where I have to query. No, no, yeah. No one will do no

query. No, no, yeah. No one will do no like this is all automation you know like uh query execution is all automation by zool. When user types a prompt in zool this what I'm saying the llm layer interprets there the intent

the orchestration layer will map the intent and your execution will be done through query automatically this is what it will do. Yeah.

>> Okay. Okay.

>> Yeah. From my perspective, you know, from a functional perspective, you know, what we could do is, you know, probably design, >> you know, I mean processes, the agent

and processes, you know, through the use of J and the LL and the models and things like that for each of the capability in areas like procurement,

the supply chain, logistics, BM and things like that. And that's large you know transformation you know that's a business in transformation you know through the function >> right so this is very simple I'll tell you you know like you define queries

right you know like for example show overdue receivables okay in theory we are doing show overdue receivables we're going for aging buckets and everything we are seeing that we have an app also that so like this if you go for overdue

receivables it will you have to define that query you have to validate that is jewel uses correct reconcilation accounts and reporting currency you have to check it and then you have to try users in finance department and how to

ask zulu for this that is these are what functional has to do I'm giving a limited set of uh you know like prediction to you how you can do for this okay but it is all different job you know they do all the backend jobs this is nothing something but yes

functional you don't you should not think that functional has nothing to do yeah functional has to do a lot of things on this as well so all this querying is very very important that is what you have to do majorly in zone

because who you have to train the system right what questions have to be asked what answers has to be collected So that is how we have to work on functional part.

>> Thanks. Yeah.

>> All right guys. So I'm done for it's already 8:30. Yeah. We will discuss on

already 8:30. Yeah. We will discuss on the rest of the topics and I will be starting some of these practical simulations also. I'll show you. Yep. So

simulations also. I'll show you. Yep. So

as you know we have started this. So we

have seen these ones. So the key use cases all these things you know we have discussed and we have gained the differences also on that. Yeah. And now

as for the like you know we will see the integration points and the navigation basically. So these are the two

basically. So these are the two important things that we are going to discuss. Okay because we have modules I

discuss. Okay because we have modules I have already kept something. So I will not run too much fast because you have to discuss in detail as I said earlier.

So every point I have to cover a lot of things into it. So I request everyone to please be on patient. So everything

single thing I cannot run practically practically wherever is there and I'll be showing you everything on that. So it

will take some time for you. Okay. So

it's not that I'll be anyways you know experiencing the environment. So you'll

understand these ones as well. Okay. So

yes on the Java integration and API documentation this is specifically we have to discuss a lot on this because the same thing you will see more deep dive into the architecture deep dive as well. Okay. when you're going for the

well. Okay. when you're going for the configuration integration level also because these points where it will be giving you a greater insight is the moment when you starting with zool you have to understand from your capability

like as you are a manager or as you are a functional consultant or an IT person or a kind of normal user or end user perspective there are there are many perspectives that generally goes into

the line when you are when we are discussing about these things okay so accordingly you have to understand what is going to be done on this and then you have to make things progressively on

that from that point as well because being your role considers that okay and it is not only that at time at times you have to give give in the blueprinting phase or you know have to understand the solutioning phase also whether where

actually you can fit this jewel also okay so these are the things you have to always understand when I'm saying that yeah now we I covered these three things so I'm starting it here which is the integration points for this okay and then I'll show you the EA navigation and

know exploring the zone environment This is the schedule for >> okay you can please mute okay any questions please be on the last part I'll give some time on that >> okay

>> yeah so yes on the integration points you have seen S4 HANA band success factors right so let me open this all right so when I'm saying the integration

points for SAP zol here so give me a moment yeah there is some zoom control which is you know not allowing me here yeah fine

Right. So awesome. So let's let's make

Right. So awesome. So let's let's make these things to here. So yeah. So on the integration point we have this S4 HANA success factors. What are the different

success factors. What are the different integration points I discussed? So you

have to always remember when you're going for SAP HANA I mean S4 HANA. SAP HANA means you will

be having two integration points. Okay.

So one is your S4 HANA I can say as uh cloud to cloud. Okay, this is one such integration you might have to talk to and another one is your private cloud.

Okay, so in S4 HANA specifically private cloud or you can say because it is a kind of a similar configuration for on-prem as well. Okay, so this is also will be there this through cloud

connector in BTP. Okay, these two things will be there and yeah, so whenever you are talking about this the first part in the integration point I am doing for S4 HANA, right? I'm talking about S4 HANA

HANA, right? I'm talking about S4 HANA right now. So in S4 HANA cloud we have

right now. So in S4 HANA cloud we have to create a communication system users basically when you're going for this cloud to cloud when I'm saying cloud to cloud you have to always remember one

thing this is for public cloud edition as you all know that now public cloud is know like booming so fast in all the SAP functional module especially for finance

you know and the sales and all the other modules okay because public cloud is all all the preconfigured setup you don't need to configure a lot of time and you have already seen that lot of projects can be easily executed in public cloud

rather than private onrem which will take some time in public cloud you know it will be going in 3 to four months of time the people the projects are getting executed easily that is one such thing you know like the business is looking

for public cloud and you know these things are progressing so fast in the the cloud arena okay so here in the public cloud basically for zool we have to create a communication systems users for this and then you have to create a

communication arrangements for the targets as well so basically what is the ma base point that we start with here is we will create a destination. So in BTP you will create a destination first of

all.

>> So are you saying that you should have two communi you you you will create two communication users?

>> Yes you'll create a communication user.

>> Did you say one or two or two?

>> It depends. It depends you know it's not one or two. It depends. First of all you have to create one user plus one arrangement for the target API.

>> Okay.

>> Okay. I'll be writing it here also. In

cloud you have to create one communication user and one communication arrangement. Okay. Then in the same BTP

arrangement. Okay. Then in the same BTP you'll create a destination for this destination also everyone you have to create a >> communication arrangement.

>> Hello.

>> What is a communication arrangement?

Maybe I should I just type my questions?

>> No this is disturbing the session you know you have to wait for that you know I I'll tell you that. Yeah. Yeah. You

have some questions please let me know.

Yeah, because it is it is considered know like continuously disturbing the session. Please please hold your

session. Please please hold your questions in a while. I'll just uh explain you what is that as well. Okay,

I'll let you know what is communication arrangement. I'll just show you now.

arrangement. I'll just show you now.

Okay, see as you said I just complete that you know that it's like your inbound this particular thing is inbound communication to whatever the S4 HANA tenant you make it right that is your communication the communication name

itself indicates communicate to which it will communicate to the S4 HANA tenant.

So you have to first create this arrangement. So that arrangement will

arrangement. So that arrangement will help you to create these users and other destinations on top of this particular channel. Okay, that is the communication

channel. Okay, that is the communication arrangement. Okay. Now coming back here

arrangement. Okay. Now coming back here I am just your okay I'm in the destination right. Right. So here this

destination right. Right. So here this destination we will be creating the type of HTTP that is which is one of the important thing and whenever you create the SAP BTP destinations for Zul this

with HTTP specifically as these things should be like enabled with O2 credentials okay so this is the standard

for your connections okay and then you can see you can you can verify that in the zool that you're calling the business partners whatever the support apps that you want in SAP case for Hana cloud you can verify them in the SAP

build apps it you can verify I'll just show you now how you can do this this is one such thing but let me let me complete this part I'll go to there and then in the private cloud through cloud connector you have to expose first of

all because you're doing through on-prem so you have to expose this S4 whatever you're working explore this through your cloud connector is the first important

thing you have to do it okay once you expose this in BTP again you have to configure a destination Same similar like what you have above above you have done this you have to configure the

destination okay again this is also with your O2 credentials you have to create okay and then you'll be having some user mapping and connections will be that you have to do it and on after you do this

you have to do Joel integration enablement so these you won't do your IT will do but as part of training we are telling you this this is not your job your IT will do this so don't worry about I told you what you have to do it

also so you have to enable this jo enablement for your S4 HANA cloud tenant. Okay. So this is how the two

tenant. Okay. So this is how the two integration points for S4 HANA cloud which you will do it. This is for S4 HANA cloud basically. Okay. And coming

to success factors people who are working for success factors it is also simple. So in your success factors admin

simple. So in your success factors admin okay that is will be there. So in that you have to register a service with O data API. This service you have to

data API. This service you have to register okay and then this things will be same. This is the common steps you

be same. This is the common steps you have to continue wherever is there in BTP again you have to create a destination. So whatever you do the

destination. So whatever you do the destination in BTP is the end line for you. From there only the Joel skills

you. From there only the Joel skills will be picked up. Okay. So here also you have to create the BTP destination for oath too. Okay. And then your Joel for success factors will ships all your

transactional navigation informationational capabilities whatever I told you right. You have to confirm for the t tenant. So you have to confirm tenant for all the success factor

capabilities. This is for success factor

capabilities. This is for success factor integrations whatever you have to do it.

Coming to for people who are in Aribba.

Okay. So here again the same important step is for Aribba people they have to go for Aribba developer portal. So in

that they have to register the application. Okay. And here they have to

application. Okay. And here they have to request the API access because this is all spend management right. So they have to request the API access and here they

have to obtain the API key there. Okay.

And then along with this when they are obtaining the API key they have to get this WH client ID as well. Right? This

is the one important thing. And once you are done with this you have to get your oath access token as well. Okay. So this

will gives you API gateway numbers and all these things configuration. Okay. So

this will typically call your required authorization bearer tokens API key headers all these things for you to access the arenment for this role. Then

again the same thing you will again put the BTP create destinations with this credentials for whatever the endpoints that you want that these APIs you will configure here and then you are all set

for Ariba to use as for the Zo environment. Okay. So these are the

environment. Okay. So these are the three important integration points whatever you have to do for your zool environment. Okay. Yes. Now let me show

environment. Okay. Yes. Now let me show you and let me explore you the zool environment. Now clear everyone these

environment. Now clear everyone these three any questions on this? I'll just

show you anyways. I just showed three important things will be there. These

are the three important buckets. This is

how you have to. So one important thing you have to understand is whatever the environment you are going first of all you have to make it ready for your environment along with oath tokens and then you have to configure the

destination with the oath tokens or APIs for the zool in for the zool integration that's it this is what the common point you have to understand okay because if you are functional but still you have to tell because your it might ask you so

what is that you have to know you have to tell this that is the reason I'm covering this part also in this class so that you will be ready for your IT to explain what you need as well. Clear

everyone >> do you have any pictorial diagram and then you can point exactly what I mean like I understand like you put everything here it it's okay

>> no I have it I'll show it I'll practically I'll show it also these ones >> yeah so if you can show us exactly one where is it one right I'll show you that

honestly right now I got zero basically >> okay fine let me show you then yeah I'll go with the practical point also you'll understand clearly >> question you say something like Don't worry about it. On the configuration

integration part, you said do not worry about it. Your admin will do it for you.

about it. Your admin will do it for you.

What if you're the admin and I expect you to show me how to do that integration configuration?

>> So, so sorry. What is that in SF admin?

You're asking >> in all of this. You says do not worry your IT.

>> Oh, yeah. Yeah. Yeah. It

>> what if I'm the IT admin? I'm supposed

to do this stuff.

>> You have to do it then. You have to learn it. Yeah. Yeah. Are you going to

learn it. Yeah. Yeah. Are you going to show it or you just >> No, I'm not showing all these things. So

I'm not going to show because systems are not there to support for me on this.

So I can give you I can show you how you can do this step. This one is there which I can show for the BTP configuration of this. This is

important. So I can show you this but all these integrations I don't have any B of success factors. Okay. So these

things I cannot but this one I can try to show the public load thing I have it.

I can try to show this one. This is what I can actually explain on this. But

based on this you can pick up from there and you can do for your configuration for other modules as well. Yeah. Okay.

Yeah. Let me go into the server. So here

so in your page everyone can go to this.

This is a remote name app going for this. Oh this is not required basically.

this. Oh this is not required basically.

I don't know I sorry for this anyways I have to go this I know this is was wrongly given to you. You don't need this environment to login. So everyone

please skip this step. So in the materials you have the server details right everyone. So in that you have BTP

right everyone. So in that you have BTP only that one is enough for you. Why

that was given is if someone has any that the IT team has thought that they need something for uh RDP you know something people can have to lo like check it in the ECC kind of thing. So

they have thought that but that is not required. So in the BTP third tab is

required. So in the BTP third tab is there this link is enough for us to drive this training. Okay. So don't go for other things. It's not required. I

also forgot I just logged in. So go to the BTP copy directly. So you will see SAP Z here. So you will see all these entitlements here. You can see you have

entitlements here. You can see you have to confirm your entitlements here. So

this is your domain. This is your provider. Okay. And as I said this is

provider. Okay. And as I said this is this will be only 1 hour 1 month only the server will be there till 17th of September. Okay. And then this is the

September. Okay. And then this is the region where it has been placed in AWS.

I have already seen this. Okay. The

provider is also AWS here. And the

tenants you can see here everything.

This is a multi-enment. I told you that multi-tenant and multi-enment based. So

these are the things. So if you come down you will see all the entitlements.

So in the entitlements you will see these ones. If you go to this one. Yeah.

these ones. If you go to this one. Yeah.

Now go into this one in the cloud foundry environment.

So these are all your entitlements for which see the cloud fun which is standard is there and then your destinations which is on light and one.

These are the ones which will helpful for you to land your destinations and yeah these are all the other services which will help you. This is by default these will come. You don't need to remember anything but yes you have to

understand whether it's on cloud foundry or not is one such thing and this is the build work zone standard. This should be there in your system that you have to make things to deploy on this one. Okay.

Whenever you are doing something on the zool okay along with this we can see these two also a launchpad a core also these will be also there on the environment. Okay. What is the important

environment. Okay. What is the important S4?

>> Sorry, sorry. 2 three questions one please go ahead.

>> Sorry I was just asking where is S4 Hana here. So in this B

here. So in this B >> cloud will be there. You can see this once S4 HANA launchpad will be there.

This is in back end. It is working. This

is the launchpad they have given here.

Here >> so here is where we do an integration with Joe.

>> Yes. Yes. It's already integrated. This

is integrated and whatever I'm showing you is now someone else is asking something. What is that?

something. What is that?

>> Yeah. What is the importance of cloud foundry then? What what is the what is

foundry then? What what is the what is it with that? I mean you you are saying that it's kind of important right? What

is it for?

>> Yeah because this is where all your environment will be like integrated and picked up right on the environment. So

that is what I'm saying cloud foundry here because in BTP when you see there are two environments will be there basically. So that is cloud foundry one

basically. So that is cloud foundry one is cloud foundry and there is ka environment. So on the cloud foundry

environment. So on the cloud foundry it's it's kind of in a BTP it's a open platform for you like for the like it's a kind of pass kind of this a platform platform as a service. So wherever I told you right when whenever you de

develop something you want to manage something you want to deploy something so cloud fun is required for you. So

whatever it's like a base for you for whatever you do for zool to put it here and deploy it. So that is where it collects and you know it's take it it's like a abstraction layer for you okay between your applications and you know

infra what you're going for that. So

that is what whenever you go for zool also you will see that on which environment it is actually been deployed in it. You can see this see this is a

in it. You can see this see this is a cloud foundry environment. If it is ka it will be in this ka environment. There

are two environments are there. Yeah.

Any other question? Someone is asking something. Okay I'm going for

something. Okay I'm going for substantials. So here you will be having

substantials. So here you will be having instances and subscriptions. So these

are the subscriptions guys. Here is how your instances will be there. You don't

need to worry about is all it thing.

Okay they they put the environment everything. So you just and have you

everything. So you just and have you have to you know confirm that the environment is running on the cloud foundry runtime here. This is the runtime of cloud foundry and all your cloud management services managers will

be there when you integrate or make something these will comes into picture.

So they will do it. Okay. So as I told you right the service is just created in cloud foundry. Okay. If it is ka

cloud foundry. Okay. If it is ka kubernates it will be showing you there directly. Okay. Now this is on cloud

directly. Okay. Now this is on cloud foundry. No coming back you were

foundry. No coming back you were >> sorry you'll be showing the integration with S4 or success factor with Joel here.

>> No no no integration.

>> How does that how does that >> no I will show you how you can actually how we are doing you know while the part of the jewel skills are getting created that time I'll show you how you can create these things but deeper

integration is a completely a basic structure that is not required for us in this training. Okay, maybe like if it is

this training. Okay, maybe like if it is like just to see like where how does that >> I'll help on that definitely show that yeah I'll show the so here these are the subscriptions that you have to

understand when for the zoo is coming on that is one is your a launchpad zool your task center these are the important ones BPA build apps build application

work studio build work zone so basically 95 90 95% of work is done in this particular part only so whatever the build apps BP are there here is where

you are In these two apps only all your zo skills will be developed, created you know implemented and everything will be there. So once they added you can deploy

there. So once they added you can deploy them in the work zone and you can make them enabled know the later point of stage. This is how we generally do. So

stage. This is how we generally do. So

this is currently this is a skill that was added but this will not have nothing because the name might attract us you know like hey what is this but if you click there something it will not show this is this is a service it is running

behind your things. Okay, even though if I give if you can see here, see the server the service up. This is a service. So don't go for this but you

service. So don't go for this but you have to check it. Just check it with the service which will run for you to because once it is integrated the services will run along with these apps only. Okay. So primarily you have to go

only. Okay. So primarily you have to go to the build process automation. So if

you go to that system will ask you for authentication. So for the first time it

authentication. So for the first time it will be I have already authenticated. So

it was not getting me. So this is the SAP build either you go for build PA or build apps the same this these two are same only the only thing is you know you have to make something difference from

the screen itself only. Okay. So either

you go here here this will leads to a same screen. See here same screen right.

same screen. See here same screen right.

So here you have to create your applications or whatever it might be.

The moment when you go for the right hand here create this create. So here

you will see these one. See you can create an application. You can create an automated process. You can create a Joel

automated process. You can create a Joel skill. This is what I told you. Diamond

skill. This is what I told you. Diamond

icon I told you, right? This is where we create our jewel skills here. Okay. And

this is a business suit. Okay. So these

are all the different things are there.

But yeah, we will ma majorly we will deal with the jewel skills only here. So

here if you go to the jewel skills, I just explore you the environment for so if you go here let's say. So before

doing this we have to do some setup also in the environment back end of the BTP.

So that I will that once you complete then only you have to come to here.

Okay. But I'm just showing you to make the environment you know explode to you.

So jewel demo something can just review this and then create this. These all

completely kind of wizard based. So if

your backend queries backend data backend destinations all ready here it is very easy to link it and you know make them enabled.

>> The same screen actually. No, no, no. It

is coming. So this is where your jewel project things will be there. So

basically here you can see all these artifacts and everything. So even the sourcing agents whatever you want to create that agents also the agents all these things we'll create from here only. I'll just show you when we are

only. I'll just show you when we are maturing our sessions. So you can see this is what see here diamond icon whenever you see see wherever the integration goes like your aribba or your success factors I told you in the

data spear or sack if the integration of this jol is happened or it was been done. Okay. Or it is getting completed

done. Okay. Or it is getting completed then you will see this diamond icon which means that from there you can actually pick this up. That means you can do the Joel kind of like whatever the questioning I told you more than

that chart bot you know whatever you want to explore all these skills everything you can do from this. This

icon will be there in the top notch here whenever you go here. Okay. In some data sphere kind of things. So there you can just click this diamond icon. Diamond

icon is J. You have to always remember that. And here is where actually you

that. And here is where actually you build your agents. You build your define the agent identities and all these things here itself only. Okay. And from

here only you will make all the AA model selections or tool configurations you know whatever that you want to deploy to tool which tool agent you have deployed for the other work work build agents. So

all these things you will do. So

commonly for build you will see this one. If

one. If integrated properly there is no separate jewel studio. So people confuse that

jewel studio. So people confuse that there is another tool called jewel studio. No, no, Juul studio SAP build

studio. No, no, Juul studio SAP build apps is your jewel studio. So the moment when you go for your build apps like this if you create your if you have your jewel skill directly here that is

nothing but your jewel studio. The

moment when you enter it, it will show you the jewel studio. Clear? So this is one such thing. Here you will create the jewel skill. See for example, I'm just

jewel skill. See for example, I'm just going to the jewel skill. I'm just

giving HR task. Now I'm not creating any HR task. I'm just showing you because

HR task. I'm just showing you because you should have the basic backend query for that directly. Go and put something will not work. You have to make a query for that. How to get it? What to get it?

for that. How to get it? What to get it?

We will learn in the coming sessions.

Okay. But I'm just exploring you the environment how this works. So here you have to give the identifier the description of it. The moment when you create it, you'll get this one. See here

this is your workflow kind of scenario.

When a scenario is called and these are the start and stop. So in between you have to add what might be your scenario.

Okay. Like if you have a uh if you are making ready for your project for a kind of a set of HR things like you know someone from your user might ask hey how many employees are there in my

organization or else hey how many uh what is my current year compensation or what is my let's say you know like what is my or laptop policy I'm giving some examples to you so you have to trigger

that you have to answer that you should have a ready query so this plus symbol will get all these things in it stomach so if We can see here. See what happens next. See now here in this you will add

next. See now here in this you will add all these things like you will run a process like you will call an action, you will run an automation, you will send a message, you will launch the

jewel skill or you will make this many a times you will call the action sorry many times we will call these actions.

Okay. So in call action what happened?

Basically you have to retrieve a business partner data from the S4 HANA piece and then you have to browse certain queries and everything you have to add that and you have to perfectly

align that into it. Okay. So let me show you something on this. So which can help you if this if this data is inbuilt on this completely so you will understand something. Yes is this is how this works

something. Yes is this is how this works and then I'll come back to the BTP destinations. Okay. So here if you go to

destinations. Okay. So here if you go to the call action create call action. So

it will all you it will produce some if you have RFC actions and all action to actions will be there. These are remote function calls like browse all actions if you go to the library like this.

Okay. So there are no actions here. So

these actions should be there because no data is there. We have to create if you want to retrieve a business partner general master data or if you want to get a sales organization. So there is no data that we have to create. Now this

all fresh system. If the S4 HANA integration is there, there is data in the S4 HANA integration in the S4 HANA box. So can it not pull from there?

box. So can it not pull from there?

>> It will pull. I have to keep a destination for this first of all basically. So the destination is not

basically. So the destination is not done right. That is an it's not getting

done right. That is an it's not getting that's what I've told to you. It's a

fresh system for you. Okay fine. I'll

tell you what is this. This is how I'll just put the destination. Come back

here. So yeah, I thought something was inbuilt already in this. It was not there. Yeah. So here you will just call

there. Yeah. So here you will just call an action. So in the call action it will

an action. So in the call action it will ask you from which destination that is what you have to give the S4 HANA and whatever it might be and then it will get the data and you will put this flow

here and that will be taken by the S this one what is this zul skill and your zool skill will be activated there from there you can ask that question. So let

me show you that a simple thing how you create destination now so this is how first of all you have to this is an exploring so you just this is how you will come and explore the zool project.

Okay, clear this one. I'm coming back to destination now. Go back to SAP's BTP

destination now. Go back to SAP's BTP destination. In the connectivity, you'll

destination. In the connectivity, you'll see the destinations. Let me open the destination. 1 second. Still loading for

destination. 1 second. Still loading for this. One second. It's locked for me.

this. One second. It's locked for me.

Okay. Yeah. So, while going for the destinations here first of all, so let me tell you as someone has also asked me know like on this. So, I'll show that on the p pictorial way. I'll just draw for

you. So but before that when you're

you. So but before that when you're going for any like you know for this dual studio for this build so this that you have to understand that we are addressing the challenges or you know

business challenges will be there for any jewel that we are going for like you know the fragmenting of user experiences will be there the manual processes will be there so these things will be there wherein you have to parallely address in

the BTP those things right because BTP is secure and more reliable for access control and all these things. So

whatever whenever you're using in the jewel studio you have certain quotas will be there that you have to understand before going for destination.

So here what I'm saying the kota kota means it will represent your numer quantity for your maximum allow consumption of a resource that is a kota right. So here your connection timeouts

right. So here your connection timeouts will take into consideration. Your

socket timeouts will be there. Your

total execution time will be there. Your

request for body size will be there.

Your response content size these are all will be there in this. Okay. So these

are all work from your the moment when you initiate a zool skill to execute a zool skill. It will have some time to

zool skill. It will have some time to establish a connection to time to execute your task on. So these are all will be there as part of that. But yes

when using dual studio you have to you have to know that there are some limitations also on that like you know the authorizations that are defining at environment level they support users and

groups okay when you are supporting with projects that are sharing with maximum like 10 user groups or you know like with some execution rights all these things so it cannot do more than that

because a combination of user groups and users are limited in this not more than 10. So if you're doing for more than 10

10. So if you're doing for more than 10 there is a limitation for now for now it is going on as I said it is still nurturing every single day for now this is the authorization part level but I I don't think so we will not share more

than for 10 groups or something like that okay and the deploying Joel skill also in the shared environment in production tenants it will take up to 30 minutes that the time is now for 30 minutes because I'm taking the

production environment not in your regular module the training and the develop environments it will not take that much time but in production Jewel skills will take time. Please take

it in the mind. Okay. Now yeah when you come to here on the services. So this in this we have this one. So you can see this one. This is under environment. So

this one. This is under environment. So

this plan will be there. You have to always ensure that your BPA will be under build default plan. Okay. And it

should have a standard subscription like this. You have to see the service plan

this. You have to see the service plan and application plan properly. You can

see this one. This should be under build default plan. Okay. And your IAS tenant

default plan. Okay. And your IAS tenant should be like automatically discover in your system landscape of BTP global account. So when you go to the systems

account. So when you go to the systems here. So yeah your connectivity

here. So yeah your connectivity services. So you have to ensure that

services. So you have to ensure that these services should be there first of all. Okay. And your destination

all. Okay. And your destination services. This is light is there. Not

services. This is light is there. Not

light something is also there. No

worries. But this should be there. This

should be discovered in your system landscape. Okay. This is one such thing.

landscape. Okay. This is one such thing.

In case if if you find something is not added, you can ask your admin to add the services. they can add that from here.

services. they can add that from here.

Okay, because there are different plan names will be there. They can add these services in whatever they want. So this

is a standard plan in which we are getting added because ours is a licensed version here. Okay, so this is one such

version here. Okay, so this is one such thing. And then coming back to here in

thing. And then coming back to here in the trust configuration in the security when you go there is a thing called trust configuration. So here if you go

trust configuration. So here if you go to the trust configuration so you will see you have to enable the trust for cloud identity provider for your applications. Say this is your default

applications. Say this is your default ID provider. This is your custom ID

ID provider. This is your custom ID provider. If you go to this, so you can

provider. If you go to this, so you can see here add identity providers for applications to enable users to log on to applications consumed in sub account.

So also shown are identity providers are for platform users used by administrators. Okay, this is a common

administrators. Okay, this is a common account that is already been enabled in the global account users. So what I why I'm showing you all these things is if your users are not or if your

applications are not under this global account you cannot perform task in the zool skills. That's what I'm saying that

zool skills. That's what I'm saying that you have to see all these things before you are going for zool skills creation or something. Okay. So these are your

or something. Okay. So these are your user groups. There are no groups

user groups. There are no groups attached here as of now. Okay. So no

problem that we can create later point of time also in the users in the user panel. Here this is a user panel will be

panel. Here this is a user panel will be there. So here you will add the users

there. So here you will add the users whoever you want on this. Okay this is all the users anyways. Now we got added if you want further you can add it on your own if you have admin skills. If

you don't have you can ask your administration but ensure on the trust configuration you have the common identity providers that are trusted. See

the origin key and the BTP cockpit. This

is open for this. Okay. If you go to the open cockpit for this also you can see that like this. This is what the initial page that I have shown to you. This is

the service where you can see the trust configuration is reing for that. Okay.

Now if you go to this boosters go back to the overview page again. Okay. Now

let me go into the boosters here. Okay.

If you go to this boosters in the main account this is all the initial check part guys. Whatever I'm just showing you

part guys. Whatever I'm just showing you here you have to check for these ones.

Okay. So whenever for setting up of Juul also this boosters will help you to set up your thing. If your admin is doing that that is much and good. If you have to do setup on your own, I'm just showing you for that. So here you can

see this one. See set up your uh workflow management setup build prom.

These are all already done but I'm showing you you have to come to booster when when you have called to configure your zool you have to come to this booster and here your jewel will be you can configure from here from this

environment like all these studios whatever I'm just showing you here right can check for that and do this one setup zool. So like this you can start the

zool. So like this you can start the zool setup here. This is a BTP environment. So here you will pre your

environment. So here you will pre your prerequisites will be analyzed by system. So authorizations failed

system. So authorizations failed checking entailment skipped skipped.

Okay. So because yeah we don't have authorization to do this. I told you right. So this prerequisites they have

right. So this prerequisites they have already kept it. So that is just failed.

I'll just read for you again. Yeah this

is not there.

>> As part of this course are you not going to show like setting this up because that's one of the main thing right?

Yeah, this is this is a setup only.

Whatever I'm trying to show here, I'll ask the admin to open this access because he already set up for me for all of us.

>> He just kept it know like these ones in lock manner. I mean that means it's been

lock manner. I mean that means it's been locked. That is the reason I cannot run

locked. That is the reason I cannot run rerun one new ones. But yes, this one I'll show I'll ask him to unlock this one so that you will set up this one also zu for your side. It's a very simple thing but anyway I'll show you

this one. Okay, I'll get you have a

this one. Okay, I'll get you have a document also right? If you can share the document >> documents will be shared. Don't worry

that will be done. Your your materials will be always there. I have a step-by-step documentation where I prepared that. So I can give it to you.

prepared that. So I can give it to you.

No worries. So you can have it also handy for you. Okay. First understand

these ones. So this is where you will I'm not doing anything guys. See this is what I'm exploring the environment curriculum is also set. I'm following

the curriculum strictly here. See UA

navigation hands on exploring zool enment. I'm just exploring it. I'm not

enment. I'm just exploring it. I'm not

doing anything here. Okay. In the in the schedule we have zu setup. Okay. in that

I'll just show you in anyways I just found that I don't have authorization now I'll ask him to get this done and then you know I'll show you the setup also okay so this is one such thing once you do all the setup and everything

right then only you can do anything in the zool environment okay and specifically creation of destinations just closing this so everyone is okay right so only boosters only you'll get

these environments whatever the environment you want for example I'm showed the zool the same thing if you have to do for your build apps also if you can start the build app there also it will ask you the same thing so it

will it will ask you for sub account and everything like this so it'll create your sub account for build apps also see your sub account wherever you integrate I'll just show you tomorrow these ones you will add these organizations tools

and spaces for this and then once you add these things you can actually you know like create the configuration for this so this configuration thing you need to have security admin rights to access the sub account trust configuration I don't have it I'll get

that and then I'll show you okay these Okay. So,

Okay. So, so with Juul studio like as you have seen that you know like we have Jules AA capabilities are there to address all the unique operational needs wherever

that you want to do it. So for all to do that first important point is landing into this individual environment BTP checking for your entitlements one

thing. Second thing enable that you have

thing. Second thing enable that you have a proper trust configuration we have seen that third thing destinations. So

we open the destinations and the fourth important thing in the build that has to we have a zul skill should be enabled.

So these are the four things you have to check as part of the initial configuration setup. Okay these are all

configuration setup. Okay these are all your destinations if you can see here because in BTP a lot of destinations are there. So here we have Ariba you have a

there. So here we have Ariba you have a lot of destinations has been someone has asked me S4 HANA cloud see in the cloud also they create the destination cloud private edition S4 HANA and S4 HANA cloud sample test disk uh center

edition. Okay, for back end also I

edition. Okay, for back end also I created onremise S4 HANA here. It has

already been there. Okay, these are all been enabled in your destinations. So

which means that you can add them and you can use them. Okay, in case if you want to create a destination because in general you have to create you can create from file or from scratch or service instance usually you go from

service instance. So if you create from

service instance. So if you create from here the destination so it will ask you like this. So you have to just sec check

like this. So you have to just sec check the sub account in which sub account you have to create this one like for us is a service manager sub account admin. So

let's go for that and then just put next. So you have to give a servicing

next. So you have to give a servicing key or you have to generate new one. If

you want to generate new one you have to write the binding parameters for that.

Okay. If you want to choose the existing one you can choose the existing one which is already there like this. Yeah

because I don't have permission. You can

see it has been locked because you might be surprised why this is locked because yes we are all the developers. We are

not administrators. I'm not from B. I'm

not from IT. If I touch anything, this might hamper the other integration environments. That is why they kept it

environments. That is why they kept it safe and locked for that. Yeah, I'll try to uno uncheck for it for then, you know, I'll just show a few of the scenarios to you for this setup and then you understand more clearly. Okay. So,

this is about for destination creations and all these things. So, and

what is the destination here? Basically,

you have if you have a destination, then you have some source here. What is the destination here? why you wanted to

destination here? why you wanted to create a destination and what information you are sending to the destination and what information you are retrieving from the source what is your source system here so it is you are

telling about the dots but I don't see the connectivity here actually can you give us like a a pictorial picture of like a connectivity okay this is my source system and this is my destination

this is the configuration I'm creating so that will help us like even though I don't have an admin or something but >> when you want to talk about like a after this source right somebody can come and

ask what is the destin I'm just putting my eyes rolling then it doesn't make any sense right >> yeah yeah definitely I'm just coming to that only so in SAP this destination

yeah because earlier what we thought you know everyone who has know some have information on BTP so that is why I am not rename I'm not defining these ones but yes if if specific questions on that

you can ask me I'm happy to help on that so in SAP BP this destination this is a configuration that in which you can define on how an application connect to

report remote system basically when I'm saying this for example you have this one is there aribba is there your aribba should connect to btp so your source is

what here now btp your aribba is your destination your source is what here btp and your zool is your destination okay so you are creating a platform here by

using this destination your source is nothing but your btp always here but your Remote system is something where you want to create like your zoo, Ariba, success factors or something something

whatever it might be. So destinations

here are for your communication that you want to pass to a system where you want to establish an application and you say use that external resources to create

that application. Okay, that is why we

that application. Okay, that is why we call this in the BTP cockpit. Cockpit is

nothing but where you land them. So this

destination will land here and then this will talk to that particular system which we call a destination through a destination service. Okay, that is why I

destination service. Okay, that is why I have shown you list of services there in the initial start of the so here if you can see let me draw this for you as you have asked for me.

>> So in this destination area basically you are providing the any other systems right outside of the BTP. Let me clear let me clear let me clear let me clear

you have asked me let me show you that.

So this is this is an entire let's say you are in the BP environment. Let me

draw a bigger picture for you for your understanding. This is your SAP BTP. Let

understanding. This is your SAP BTP. Let

me clear a question. Let's say this is your SAP BP entire environment. So in

this you will have your let's say you have this one. I'll write this as a onremise system. Can you also go a

onremise system. Can you also go a little bit one level deep like you know okay BTP global account and from their sub account like that? Yeah sure sure definitely why not I'll just I'll tell

you that yeah you can ask questions no worries I'll but give me some time let me answer one by one I'm happy to clear every u bigity that you have on the

subject okay so this is a web application like this okay so basically this is where your system will talk okay

on the BTP environment let's say your system you have your onremise you're getting remote onremise systems let's say a remote systems I'll say okay so these have to talk to what in your BTP

to an application right so this is your application that you want to create so your application when it is getting created it has to understand what it has

to understand on what environment it is getting created on to which environment it is getting the communication and on

on what variables with the environment that it has to check it while it is connecting this application to talk with right so that is where I told you this

will be leveraged with your environment initially called cloud foundry environment this is your cloud foundry environment in the BTP it will help this

application okay to talk with your base applications whatever are there that they're getting data here so to get it enabled it will read the credentials it

will use the values it has to make the destination for all these things. It

will use few of the other things in the BTP like it will have few more other services like this. If you see it will have some environment variable services.

Okay. So with this what it will do it will read the variables of your application. Okay. It will use one more

application. Okay. It will use one more service called what authentication services. I told you that this service

services. I told you that this service it will use y to use the values to request your application information. So

here application is like a success factor Ariba.

>> Yes. Yes. Yes. Anything it will be anything it will be. Okay. Anything.

>> What is remote onprint system here on the bottom and the web?

>> Any system that you are connecting with your S4 HANA remote systems you know what you're connecting for that. No we

didn't get it actually the applications we are actually expecting that what is the basically the application you're saying that it can be like a S4 kana and Ariba or something >> but again the application

>> application yeah application in the sense means you are creating something in the BTP by by you know like getting that source system into BTP environment

like for example I am connecting success factors like success factors I'm connecting directly I can I can I'm when I'm connecting success factors with BTP what happens in your the application

will be on the BTP right the application will be generally on the BTP so what I'm saying what I'm trying to say here is when you are let's see the to manage

your or to consume your success factors you you have to bind some destination service in this application the application you create here the moment see for the moment when I'm going to

create a zul service what I did it I have gone through BTP only so BTP is holding that application right but you are talking to what you're talking to a service other than where in your other

system kind of thing build app is a separate service you're talking to that so talking to that you need a destination service okay because that is your destination jul is a destination so

to consume the destination service from an application from here like this you have to create that service instances to bind that application because it has to understand so that is what you will

create all the binding or whatever the internal binding through like your web tokens, award tokens, you know, all these things comes into picture. So that

will now communicate with your destination and these services will help you to create that to use the data here and there and you will create application seamlessly. The moment if I

application seamlessly. The moment if I use for example if you see here see here if I directly go without know like integrating this build in BTP I won't

use skill directly here never. So what

is the application in this PTP cockpit actually you are talking about really like you have a you draw that application layer right what is exactly here in this PTP cockpit >> I'm not getting what is what exactly

>> so you you write that you you define that like application right application services right >> application yeah so where is this the application exactly the service in the

BP cockpit whatever in the screen here exactly where is that one that component >> that will hold in your TTP only >> exactly can we see that here in this system >> that's but I don't have you can see the

moment in your creating you will see in the build zone when you deploy that you will see that that particular application the first question you have to clarify your question the destination

you asked me I cleared that if this application is coming to landing in your BTP's environment only whatever you're doing see this is all goes now again if

I do something here this will again retract back to BTP only it is the BTP is the mother for again it have to go for there and you have to get it and it will post something it on it because BTP

is connecting it here this is separate environment this is your platform environment okay don't get confused >> so okay let me ask one question right maybe you can help with an example like

for example if you go back to your flow right let us talk about the HR example what what you said >> where you have to like let's just say get all the employees who are there in

company for 10 years okay >> so in that example What is the application? What is the the external application and what are you mentioned in the flow, right? Can you

clearly tell what are all those and then maybe that will help us actually because we're not able to relate because see I think a lot of folks here we're not from BTP.

>> Oh >> yeah see we are we are expecting these fundamentals actually and we understand now that a lot of Joel is actually BTP right. So maybe that is what is

right. So maybe that is what is confusing. I mean, at least for me, I

confusing. I mean, at least for me, I hope everyone is also >> maybe a term that he's using. It will

make a whole lot of sense if he just if when he's doing it, the way he's explaining is kind of confusing and I kind of I do understand your point of

view. The way he's saying application in

view. The way he's saying application in terms of BTP, the application is going to be let's say your your back end and how is connecting over here. I don't

know how is confusing with the application. Maybe it's just the way

application. Maybe it's just the way that he's explaining it, but when he start do it, when he actually shows one example of how this is done, >> it will make more sense.

>> Yeah. Yeah. I mean, definitely. But but

again, KBO, I mean, if you want to go back to your flow, if you want to just take that one example where you have to have success factors from success factors, you want to get the employees

with certain years or something, right?

So, what is application? What is the external destination and all of that? I

think that that might make sense but I'll leave it to you. You got my point?

>> Yeah. Yeah. Yeah. No worries. Yeah. I

see. Okay. Fine. Yeah. I thought you know like people having some BTP knowledge I have just gone through it you know as per the content. So if BTP refresh session is also needed. I'll

just do it. Not an issue. We can do this. Just give me a moment. So what is

this. Just give me a moment. So what is the basic question here? You want a complete BTP refresh now or what? What

is this? So my question is basically when you go back to the flowchart whatever you have put right in the word what is the application if you can help with an example that be clear that's

where I'm coming from I think the previous server is asking the question right I'm having the same thing we are not able to correlate exactly what you're talking about when you say application because we thought that when

you saying application there I thought you will say Joel skills actually okay can you can you go back to the flow chart actually please >> one second yeah the system is stuck for me. I just give a second.

me. I just give a second.

>> Okay. In the word document, whatever you had. I mean, if you can help with an

had. I mean, if you can help with an example, I think that'll clear out and whenever you're going through some terms, right? If you can just wait a

terms, right? If you can just wait a minute and maybe explain them more, I think that'll definitely help for all of us. But yeah, please don't get us wrong.

us. But yeah, please don't get us wrong.

I mean, you're doing a great job. It is

just that some of us are like trying to understand. See? Yeah. Yeah. I

understand. See? Yeah. Yeah. I

understand. There will be some ambiguity for the people who are new into it. I

completely understand and I it's my responsibility to clear your ambiguity also that is the reason I'm asking what is the what is the correct question so that I can answer it exactly for you. So

>> yeah just give an example clear example like what would be like you know like the example I was saying right if you if you have to build something in >> I think if you have some diagram that

would be easy for them to understand.

>> Okay. If you go back to the not you had where you draw that board that application in cloud foundry and the uh and the and the connections you not I

think that's what he said go back to that and try to draw a chart and tell him what is the application and give him an example just to clarify I

think that's what he's coming from >> no I got it what he's coming from because see there are a lot of questions coming from different different things on this so I want to clear on the BTP's part. So I'm just trying to cover that

part. So I'm just trying to cover that first of all then then I'll go with it.

Okay. Because multiple people have multiple questions. I am not denying

multiple questions. I am not denying that you know but when I started with some destination when he asked destination and then when I showed something it was being asked from that level as well. So I don't want to

confuse everything. Let me give a clear

confuse everything. Let me give a clear setup on this. One second. Me open my notepad. So consider this now go for the

notepad. So consider this now go for the new one here. See yeah BTP global account someone as I'll come to that later part you know like see coming to first of all in the BTP cockpit we have

destinations I told you because we create a destination uh whenever you want to connect with your zu also or whenever you want to create application so destination is what I told it's a

configur configurable object or a configuration object you can tell that that it will store all the connection details of your remote system I told you right destin service for example

whatever the build system SAP build build apps is there for that certain services are there right so that services will be stored in your destination okay clear whatever

destination so right >> how it is used that means the question the other person asked me how it is used so when you create in BTP that means the BTP cockpit when I have shown you the

destinations remember that applications don't directly know the backend URL That is why they are asking because they have multiple URLs. They can connect

with multiple destination sources. So

it's responsibility of a system to ask us what is the back end URL that you want to connect. That is where they ask the destination service at runtime.

Let's say for the success factor data used there for example an application is there. Give me the destination you

there. Give me the destination you called for success factors HR success factors payroll something something like that. So your destination service will

that. So your destination service will resolve it when you uh link it. It will

return the URL with all the authorization tokens and everything and then app will execute the call whatever that you have make it out. So here

admins who can have the responsibility of it they will only connect this one.

So how it is used? It will used for the backend URL connection destination service. Okay. Now come to the next

service. Okay. Now come to the next question. Someone asked how does this

question. Someone asked how does this application retrieve the destination.

Okay. So if you go to this we have a destination service in the BTP. Let me

draw this for you in simple thing I just want to show you. So this is your the security BTP security this topic for your understanding I'm showing you. So

this is your front end. Okay. So this is your back end in simple terms I'm telling you for understanding. Okay.

Okay. Now you have to uh the end user will log in from where? From the front end right here the end user will be there. Okay. Now the moment when he log

there. Okay. Now the moment when he log in the in the front end your applications will be showcased where in the front end right. So here is your application. Okay. So this please please

application. Okay. So this please please let me complete. Okay. And then you ask me the questions. This application will be there in the front end where you will get this data from the back end. Anyways

that is a different point. So but when you are logging in here the moment when you say when the end user will login or starting you know to know like hit some icon from here that means there's a

login. So here internally in the login

login. So here internally in the login for BTP here is where your destination will work the destination or destination service

here is whatever you configure in BTP the destination whatever is there. So

this as I told you the destinations will be with have a type HTTP or some other request will be there. So that

destinations will connect there is a core app service that will run here that will talk to your front end this core app. Okay. So this will talk to your

app. Okay. So this will talk to your front end like this. Okay. The moment it will talk the destination will check this. Okay. And it will be okay. This

this. Okay. And it will be okay. This

particular service is okay. Now I can get the data from the backend endpoints.

It will now retract back to it here like this. And it will have this end point

this. And it will have this end point which will connect your back end to front end. Okay. Through your common

front end. Okay. Through your common validation things like JWT or access your tokens whatever it might be there it will get it from there. So this is how a simple service definition or

service binding or you say the application retrieval will happen in it.

So during this process only the authentication will be done through your oath authentication accessive authentication whatever I told right that will happen in this login scenario.

While login only this will happen and whatever this services whatever that you are feeling that so that will be automatically been done through this access your authentications which your users are already been done or

configured in your back end. So this is a simple thing how system will run in the BTP. Okay app send request

the BTP. Okay app send request destination service and receive destination information in part of exchanging of the data any any individual point you connect with it.

Okay. So into that as I as I so as I told that this is how an application will retrieve a destination. Okay. So

how we connect to system is whether you do any setup success factor arba etc etc. So in that setup you have to as I as I said in the backend setup whatever

you have to your admin has to enable all these O data APIs O clients everything to get this connected then only system will recognize this destinations and then it will make this environment

enable for you to run on it clear everyone >> so in any workload when you deploy to BTP because someone asked me what is an application first of all okay in the zoo

context or in BTP here because I'm talking about zool you whenever you deploy this to BTP cloud foundry or either ka or either ab that exposing the

APIs or actions that zulu can call. So

that action that you are making will be is your application. Typical example I can say a java service that is talking to your back end using destination like whatever I have just told you with some

security or something it results some results from zu which can show to the user. For example, in the front end I

user. For example, in the front end I asked, hey, I want my compensation package. You're asking this. So you're

package. You're asking this. So you're

asking this means that is what is binded in your application. So whatever you are asking in that is an application. Okay.

How your destination are used by the application when you configure a destination in BTP with the backend URL plus O details like whatever I showed to you. Your BTP app will resolve the

you. Your BTP app will resolve the destination and that app call from the back end like this what I've showed to you and then it will get the data to zul front end like this. This is your front

end right now. So that is your application. That is where your

application. That is where your application layers generally exist.

Clear >> right? So previously we just saw the

>> right? So previously we just saw the Joel skills you try to do and there the action did not work. So maybe the destination and all were not configured properly or something like that. Right.

So basically the Joel skill app is the application in that example.

>> H okay.

>> So this is how someone has asked me. So

I'll have already I draw this sometime because I'm just trying to find it this environment. This is how this simply

environment. This is how this simply looks like. Let me show you this a

looks like. Let me show you this a highle thing. One second. One second.

highle thing. One second. One second.

I'll come to you one. Give me a minute.

I'll come to you. I draw this. I just

get from my library here. Yeah. I just

get this figure for you which I have drawn in my last session. Yeah, you can see this is similarly looks like this.

Let me complete these ones. Yeah, this

is how your total architecture of BTP high level overview. Yeah, someone as Yeah, someone asked me global. I'll tell

you that what it is. Yeah, this is how people who are just listen. Yeah, please

go ahead. Someone is questioning me.

>> Yeah. So on the previous image right picture, what is the front end you know for a user >> in user right?

>> Yeah, front end zool is always the front end. when it comes to the analytics

end. when it comes to the analytics right so if they want to look at the reports and you know what's happening across my supply chain and things like that

>> so how or you know what can we use for such a analytics is it IBP front end or do you have some idea like the front end I'm more you know concerned about the

front end other than the jaw you know jol is already in the embedded isn't it but is there dedicated front end as well that we can use.

>> No, from the little picture.

>> No, no, from build apps only you used it. That is the main front end for you.

it. That is the main front end for you.

Yeah. Other than Yeah. Build work zone.

You'll deploy it. I'll show you the application. That is your main front

application. That is your main front end. But not in Yeah. Yeah. Build web

end. But not in Yeah. Yeah. Build web

zone is your main front end. Yeah.

>> Build web.

>> Build work zone.

>> Work zone. Okay.

>> That is where you deploy and see this whole thing.

>> Perfect. Perfect. Okay. Okay. Good.

Good. Thanks.

>> Okay. Yeah. Now, someone asked me what is global account? What is sub account?

Right. See global account uh I'll just tell you this. Let me open this one. So

the menu and go to this one.

This is main server admin. Yeah. See

this is the global account explorer.

That means on which that is nothing but on the the main admin account or the main top level account that is holding in BTP will be called as global account.

See if you are this is in sub accounts right now. If you go to switch global

right now. If you go to switch global account see this is your global account.

Global account is nothing but the main account on which on your entire BTP stack is laid on. It is a top level container you get when you subscribe to

BTP or when you license to BTP from SAP.

It represents your complete account for BTP. Within this account only you will

BTP. Within this account only you will have all your entitlements what I showed you the regions you know all these things everything. And the sub account

things everything. And the sub account means you can see sub account here. This

is a subway account on which I created.

This is a it is a simple subdivision under your global account. Okay, you use these sub accounts to separate the environments, projects etc etc. For

example, me I use ZOL. So someone from the team has used they can use SAP other services or bash bash studio they can use it or someone can use for NodeJS. So

everyone can't come in the same sub account. So they can create different

account. So they can create different different sub accounts like subfolders in our normal layman terms to create that individual applications or individual environments whatever you are

being entitled for it. Okay. And region

is which nothing but whenever you connect to this whatever the available nearest region is there that will be given for the global account to connect with. So on that this sub accounts also

with. So on that this sub accounts also get created automatically whenever you are creating for it. Okay. So your

global account is the topmost container.

Sub account is a child container and for global account you will use it for your main entitlements your quotas your billing everything will be handled from the global account only okay your sub

accounts will have your technical setups technical environments and all these things okay clear everyone all these things any questions still >> yep all good thanks >> okay >> no just one quick question so the let's

say I have HANA is for HANA so have Aribbar right so can it be in the same sub account or does it have to be different sub accounts for each one of them.

>> Uh when you're specifically digging with sariba or success factors, it will be in separate sub account. If you're not integrating with uh zu, if zool is also integrated with that, that will be in the same account.

>> Everything will be no not jewel but like >> it will be a sub account separate for you as the direct direct question. Yes.

Yes.

>> Okay. And then Juul will be s jewel will go and sit on top of each of the sub accounts.

>> Exactly.

>> Okay. Thank you.

>> And what else? Any questions guys? Clear

everything. Any any any BTP questions here? Anything still you want to clear?

here? Anything still you want to clear?

>> So within the sub account you you basically put all the destinations which you want to connect. Am I right?

>> So it's more like if at all I don't want Ariba to really have Joel in my scenario then I don't even want to put the destination in the Joel sub account. Am

I right?

>> H exactly. All destinations in BTP are defined in the sub account level only not on the global equity because it's a it's the destinations are relevant to your applications individually. So if

you define global it's no more useful for everyone like that you know it has to be mandatorily. So that is the reason these destinations will live in the sub account for a connection configuration or for to ensure the different sub accounts and different connection

settings all these things to happen right that is the reason they stay in the sub accounts only. Yeah, like for example as you said the HR analytics is the sub account. that you have to maintain here and then the destinations you can configure for success factors or

on-premise for that diary for that whatever you have to make it for the sub accounts you have to make separately for that and then you can call destinations you can make something so all your backend configurations can put in the

sub account simple answer >> so so within like for example S4ana right I want to access only SD and not HR or maybe only finance and not HR or

something like that so that sort of control will it be there or no >> it will for the global users it will have it not for everyone the control will be there but for the limited users

>> so you're saying that control is based on the users and not by destination right destination will still be S4ANA cloud >> exactly >> but maybe we can control using users and user groups >> exactly exactly exactly that is where

your trust configuration comes into picture >> got it thank you >> okay guys for whatever I have been done I have done I have shown you the integration points and explored the

environment so we will see the jaw setup and architecture deep dive I will make it out okay yes and one one request from my side is yes questions are always welcome because we a lot of chant can

happen on this but yes I'll give you because many people are new into this I'll give you 20 minutes for question and our session so first 1 hour 15 minutes or 10 minutes I'll continue my subject and then you can ask all the questions

>> all right let's test your knowledge here's a question for you which technology primarily powers SAP jewels capabilities option A machine learning only. Option B, blockchain technology.

only. Option B, blockchain technology.

Option C, generative AI and large language models. Option D, traditional

language models. Option D, traditional rule-based systems. Take a moment to think and when you're ready, choose the correct option. Remember, each choice

correct option. Remember, each choice holds a key to unlocking the answer.

Good luck. Type the correct answer in the comment section. Hey there. Want to

get really good at using AI in SAP? Our

SAP Jewel course is here to help. You

can take it at your own pace on our platform. In this course, you'll learn

platform. In this course, you'll learn all about SAP Juul. It's like an AI helper for work. From asking smart questions to getting instant insights for faster decisions, our course covers

everything you need to know from the basics to cool advanced features. It's

made by experts who really know their stuff. Your teachers are pros who've

stuff. Your teachers are pros who've worked with SAP tools for years. They're

here to guide you and answer all the questions you have. And don't just take our word for it. Our students love the course, too. People just like you have

course, too. People just like you have found this training super useful. Best

part, it won't cost too much. This

awesome chance to learn is really affordable. Ready to become a SAP Jewel

affordable. Ready to become a SAP Jewel Pro? Sign up on our page now. And for

Pro? Sign up on our page now. And for

more info, check out Zarentex website.

>> Let me share my screen guys. Yeah. So,

this is the PPT that we already have in our portal. So, I'm covering about

our portal. So, I'm covering about configuration integration. So, you guys

configuration integration. So, you guys can relevantly know like look into this.

So all this content was already been trained here here but whatever I explained because if I go through it it might be a read mode for you. So I'll

explain everything on this right. So we

are covering the topics are of considering these ones as I told you like we will be covering the dual setup for SAP modules and architecture deep dive and if possible I'll go for the AI

security also. So this is what I'm going

security also. So this is what I'm going to cover for okay. So I'll be showing you some of these configuration setups also. Okay. But all configurations

also. Okay. But all configurations whatever I'll be showing you are with know with not complete because I'll be showing the process but I will not be uh completing them because if I complete they will hamper the current setup which

was already been set up that is what the admin has told to me. So he given me rights when I asked to him. So I'll show you that configuration also. So that is what so let me go into this now right.

So yeah specifically configuration and integration guides configuration integration basically you know we are discussing as part of all SAP modules

that we want to discuss on this. So SAP

ZO you know we have understood what the ZO generally work and how this will work and everything right. So I framed few of the other things also for our better understanding so that you know like you

guys can understand because yesterday there was a request that you know to be kept some of the slides before itself only to not to draw. So I just kept this

ready handy for us. Okay. So so four important architectures are there which I have to discuss with you now. Okay. So

before I go with the architecture you know like for the understanding how know like how this zulu works is one of the important thing that we have to understand. So whenever user starts know

understand. So whenever user starts know like the moment whenever user starts there will be particularly five to six important things will be there whenever

you start with zu like if you can see I have to go with my pad. Okay. So first

you have to understand before going for zool architecture how zool works right.

We already got some knowledge how this generally been going on and what is this this is getting on and all these things we have understood from the last 2 three days like so how zulu works you know

like user generally in the front end generally user enters the prompt right and then the request will be taken by the system right on the zool's scenario catalog I'll show you now in the

architecture this one I'm just telling you with an example how this generally works so here the request whatever you send the prompt, it will be treated as a

request. Okay. So this request, this

request. Okay. So this request, this will be processed and orchestrated.

Okay. Okay. This orchestration will be done, I'll I'll explain you how this will be done. Okay. As part of that once that is done, once it is orchestrated,

now Zul will sends an enhanced query.

That means whatever that we have been asking that will be converted as en enhancement query. The information will

enhancement query. The information will be provided with a rich query to the LLM. Okay. Like it will be an enhanced

LLM. Okay. Like it will be an enhanced query will send to LLM and then LLM will start working in the back. Okay. So in

the step four what happens? LLM will

start working. Okay. And it will respond back to the zool whatever the question that we ask. Okay. Now whenever it is responding back to Google the zool. So

here Zuul leverages some functions to call the backend system because it has to connect to backend system for certain call. So Zul calls the functions for

call. So Zul calls the functions for backend system. Okay. And it will

backend system. Okay. And it will deliver the response to user. So this is what generally whenever the moment when you enter it will the request will be initially first the request will be

processed and orchested internally and it will send to the LLM. LLM will work on it and it will back to give the response back to Juul. while that is happening it will have the take the functions and know all the backend

system calls there and and then it will deliver the response to the final user right this is what I'm just know explaining you in the scenario like so user when starts with their queries

whatever the queries relevant to cloud success factors are whatever it might be so they will start with the query so here at this level there is nothing that we can explore more the more thing that

we'll explore is the when the request will be processed and orchestrated right if you can see here okay fine this is not getting yeah you can understand this

one yeah so this is your zu I said the moment when the prompt comes here okay so now it will goes to what the zu will goes to here this is your orchestration

that means it will check processing and orchestration does what okay it's nothing but it will check for the available scenarios it will check for the functions it will check for the

skills across your cloud applications uh when it will check for the the way that question was posted you know a lot of things it will internally do okay that is what it generally do in the

orchestration okay so in the orchestration basically three catalogs will come into picture I already told you told about this but I'm just reiterating so scenario catalogs will be there knowledge catalogs will be there

context catalogs will be there okay so when zool interacts whenever a question comes a prompt comes to zool so it will does what it will check for on these catalog

Okay. So on scenario catalog on scenario

Okay. So on scenario catalog on scenario based mode that means the prompt will be analyzed for the relevant scenario like it is for HR scenario in HR scenario if it is per payroll scenario or it is for

some other time timestamp scenario like this it will analyze that scenario for the catalog. Okay then whenever that

the catalog. Okay then whenever that user interacts with the ZO with their first input is analyzed for for certain predefined scenarios or functionalities.

So this process ensures that zuul can provide some accurate and contextually relevant responses. So to do that these

relevant responses. So to do that these catalog will help you there. Okay.

Because further to the scenario zulu also conducts someformational filtering.

So based on the knowledge catalogs what I told you initially in the architecture when I told I told about the rag right.

So it will let the LLM to generate certain answers which can attach contextually that can relevant and precise for the response. So here in

this repository these three are like repositories only you can understand.

Okay. So in this repository what happens SAP's what I can say best practice documents SAP's best practice proprietary knowledge or you know like customer own documents all these

grounding documents will be kept in this knowledge catalog so from there it will also as an information filtering it will do from there also and again there is one more thing which is called context.

So here whatever the information about the SAP cloud applications will be there with respect to the user which whom is asking for additional things that means

for example if I am a power user I'm not a power user but I'm asking some report where I am not able to access so that context will be filtered here okay based on the history and role it will filter

here so these three cataloges that is called processing and orchestration that will help that will be happened through these three individual catalogs. Okay.

Once this information whatever I ask for example I want HR I want paylip of this current month like a very simple thing the prompt I have given. So zul will check what is the paylip for the my what

is the pay slip it comes under HR. So

the scenario catalog is cleared okay it don't need any knowledge catalog. So

from context it will see whether I'm able to get that information or not. If

I'm asking for mine it will get if I'm asking for some others it will stop it.

Okay, that is where the context. So

because as I said zool is always aware of user's role and permissions and this means a user cannot access information or any adj any adjacent business

processes that he is unable to do. Okay.

So this is where it will do. So once it is done for example the HR things are every everything ready. So it will keep it ready for you. Okay. Now Juul sends what this information to the advanced

LLM. Now this will the enhanced query.

LLM. Now this will the enhanced query.

Okay. Fine. It will send it will take all the details and it will send to the BTP LLM. Okay. In LLM what it will be

BTP LLM. Okay. In LLM what it will be this is the step three. This is step three where your generative a hub will be there. That means where your LLM will

be there. That means where your LLM will be there. So these LLM that means Juul

be there. So these LLM that means Juul takes all the information here and provides a enhanced query. This is what I told in the step three. This is the

step three I told Juul sends an enhanced query to LLM. So this is the enhanced query to the LLM. So what is this these LLMs here these will be available

directly in our BTP platform like our generative ahub you are seeing this here okay so Juul follows general multi-partner strategy for generative way I told you in the beginning also so

it will it will employ foundational models and you know so it will deliver certain performances for different different use cases for whatever you go so customers also get the most relevant

information what they're getting so here It will leverage this LLM for in in generating a hub block where in which all the AA foundation and BTP will be

available in this block. So from this it will take the help of the LLM and it will get the necessary information back to the ZUL. Okay. So now directly back

to ZUL it will go to here directly to the SAP cloud applications because the necessary information will be there in your cloud applications for this. Okay.

That's what I told you Juul take the backend system calls and it will then respond back to your response right so for this what happens in this level that

means in the step five jewel sends the request to the relevant SAP back end like success factors arbar whatever it might be it will send it so the respective scenario information will be

retrieved so it will be retrieved via through what through O data calls okay or sometimes it will be through some LLM dialog management will be also there internally but that is separate thing

but many of the time we'll go with the O data that is what I told you we should have oath authentication right so for this what happens the war data call will

help us to to get the to retrieve the respective information okay by which it was been called and then whatever the specific question that you are posting it will be the data will be

automatically fetched now Juul gets the required information to process it okay now Once the zool get the required information to process it, it will sends

back to the user. Okay, the response which is filtered, which is validated, which is uh security appropriate, whatever the response that will be there after checking all these things, it will

respond back to the jewel AI process for the prompt whatever been asked. Okay,

this is the total way how generally the jewel works. Okay. Now after you know

jewel works. Okay. Now after you know now now the jewel has worked right from questioning to your orchestration of information then to BTPLM and then to cloud application for back end and then

to back to zu and then finally given to the response to the user. This is done.

Now this particular thing whatever this process whatever I have told you this will have certain architecture behind that. Okay. So what is the architecture

that. Okay. So what is the architecture is what now we do in the architecture deep dive. Okay. So here if you

deep dive. Okay. So here if you understand this is the simple architecture I have told you. I am going level by level. This is the second level architecture I'll show you. This is the very deeper architecture I'm showing

you. These are the three architectures

you. These are the three architectures I'm going step by step to you to explain all that. Okay. So if you see the first

all that. Okay. So if you see the first one this is your >> can you make it full screen please? I'm

not able to see some of the elements here.

>> When I am making full screen this is 1 second. This will be a slideshow here.

second. This will be a slideshow here.

I'm trying that but this is showing in a different way.

>> Yeah, thank you.

>> One second. I know this is getting clammed here. I don't know why this one

clammed here. I don't know why this one is behaving this way. One sec. Let me

big it furthers or else. Is it clear now?

>> Much better. Actually, I'm able to read some of the elements now. Yeah, thank

you.

>> Yeah, fine. So here this is the basic architecture you have just you can understand that. So this is for

understand that. So this is for developer at level. The developer will always be into the design time environment. Okay. So in which this

environment. Okay. So in which this resent time this is bass. Now in instead of bass you will go with build apps here because bass is per other development environments as zo is integrating

everywhere you can see that. So let's

say it is build apps. So build apps will be in generally context in in general very what I can say it will be in continuous touchup with the zool where in which that is where we are building

the applications right for administration console you can see all the tools are there. There will be three environments internally working in this sub account. The moment when you create

sub account. The moment when you create a sub account. Okay, you will have these three environments. Your admin runtime

three environments. Your admin runtime or admin environment, your design time environment and runtime. Okay, runtime.

Runtime is nothing but whatever you design in this applications mean design your applications in the in here you will deploy them here. Okay. So you will deploy them through your build work zone

and then you know these will be available to the end users generally.

This is the general architecture I'm telling. Okay. So whenever you create a

telling. Okay. So whenever you create a subway account you in subway account these three run uh run environments will work one is your admin design and runtime and all your admin capabilities

or functionalities that are relevant for runtimes and designs will be internally all services will be configured certain time preconfigured certain time you have to configure on your own based on your

thing. So basically you have to develop

thing. So basically you have to develop the when you want to develop the full stack applications based on SAP cloud programming model like CAPM or if you want to develop front-end applications

based on fury elements or when you want to develop mobile applications. So these

are all run natively on the web web app browsers in your BTP. Okay. SAP build

code is there. So other than you when you see I have shown you also we have build apps build code build work zone.

Build work zone is where you finally deploy them in in your environments and then build code or build apps where you develop them. In build code people who

develop them. In build code people who want more customized zool skills and all these things they have to write it through your NodeJS or you know other applications whatever they want they can do it. If there is more customization is

do it. If there is more customization is there where in which the applications cannot stand for that. So, so these are some environments you know like this is the turnkey environments for you where

in which for all your coding, testing, integrating, managing applications will all happen through this. Okay. So this

is a very simple architecture. Okay. So

you have to understand at this level at sub account level you'll be having admin design runtime environment and runtime environment. Sorry design time

environment. Sorry design time environment and runtime environment.

Okay. And coming to here the sub account the next level of architecture for zool thing here basically how this works and I have I have told to you right now. So

this one on the architecture level.

Technically you have to remember a few points before this. Technically this zuul is a service

this. Technically this zuul is a service running on BTP. As you already know that I have already showed you also the moment when you add to the global account in the services the zuul service

is also there. Okay. Which means zool is integrated into your cloud solutions like your s4 hana success factors or your build zone build apps. I've seen

that right many more. So it is integrated to different different cloud applications. Users can access Zuul okay

applications. Users can access Zuul okay through this individual build apps environment which I have already told to you once you integrated you can see that and Juul also uses certain cloud

identity services for all authentication and authorizations whenever you are using that. Okay. Now let's say this is

using that. Okay. Now let's say this is a very simple thing you can understand but I'll explain you with a small example also this architecture then I'll go with the bigger architecture. Okay.

So here if you can see we have solutions are there you have zu is there your btp it's going from right to left okay and as I said the zool always checks for the destinations and connectivity here and

you whatever you prepare on that it will go to the landing on building block zone okay and these will be constantly being taken care by your identity services for authentication and authorization and

these are your external solutions or SAP solutions like sporthana success factors by which the database is getting connected for zool it's very simple so if you Can when you can see internally

into this more when user say and for example your manager or someone when they enter a prompt in the this is your let's say this is your user console okay

when user enter a prompt in zool UI so that will be embedded inside what inside your SAP cloud solution like this one he

entering here means it is go to here a cloud solution right for example let's say you might ask Hey, show my total number of leaves or show my how many

leave request I have done in a month.

That is the question you are asking to zu. Okay. Now zul what it does? It

zu. Okay. Now zul what it does? It

forwards this user request to the service that is hosted in BTP. So this

is your BTP. Okay. So the moment when you ask it, it will be send this request to BTP. As I have explained in the how

to BTP. As I have explained in the how Zul works scenario right now. Zuul sends

your prompt to LLM and get a response.

Okay. To access the SAP cloud application. Okay. In this case also

application. Okay. In this case also Juul recognizes that leave request will be stored where in the success factors, right? We will not tell to Zul. Zu will

right? We will not tell to Zul. Zu will

recognize it. Okay. Leave system is will be there in the success factor system.

So it will automatically think and it will go back to success factors and to retrieve what to retrieve the data of this leave request from the success factors. Okay. While going to success

factors. Okay. While going to success factors like this. Okay. That means

zool. So what it does it will it will establish a connection through O data API. So you might you might ask me also

API. So you might you might ask me also how it will go and talk to success factors that is through your O data API.

Okay. So then Zulu uses your preconfigured destinations in BTP here to securely establish these connections.

Okay. In this case, Juul calls the destination to access your success factors like this. If you can see here, the connectivity is passing through success factors from BTP. See in this,

it has gone to here. The destination is landed. It has checked for the

landed. It has checked for the connectivity from here. The connectivity

has been checked for your success factors as well. It is what I I told preconfigured destinations in BTP will securely establish your connections in

the SAP cloud applications. Okay. Now

once this is done the request flow through the connectivity service from your BTP okay through your success factors to your success factors if it is an on-premise system the connectivity

will create a secure tunnel again you might get it out that if it is mine is onremise how we'll do again we have used a cloud connector there right? So it

will create a secure tunnel there and it will use it from there if it is onre.

Now what happens? Juul calls the O data API to fetch the required data. In this

case what happens? Zuul makes an O data API request to success factors and get all the pending leave request to here to back to here. Once it gets the data,

Juul formats the response send it back to the Zula. This is how this is your zoolis. Okay. So then the zool a will

zoolis. Okay. So then the zool a will display this to the customer. This is

like 1 month in 1 month you have five leaves 10 leaves something whatever it might be. Okay. So this is how your

might be. Okay. So this is how your internal architecture will work when a when a individual request is getting passed into your system. Okay. Now you

might be surprised what is this cloud entity services doing in between. Okay.

Throughout the process the security is handled by these ones only. Okay.

Identification will verifies the user before accessing the zone. You can see here this is getting to total BTP global account. It is not going for sub

account. It is not going for sub account. I'm putting this arrow to

account. I'm putting this arrow to global account. So this identification

global account. So this identification services first one it will check for the user before using this zo access and identity provision is going through your work zone. Okay. So it ensures that the

work zone. Okay. So it ensures that the user has the correct permission in zo and success factors to able to access or not. Okay. So this is how your identity

not. Okay. So this is how your identity authentication for global account provisioning for your local systems whatever going to access for the retrieving of data. So this is how your

total architecture will work for this.

Okay. So now going for the one more level up on this.

>> Question you want hold on hold on hold please let me complete this I'll question. No problem.

question. No problem.

>> Let me complete this.

>> No I'm saying make it big only. I'm

saying make it big if possible.

>> I'll go one by one. I'm going here.

Don't worry about this. Try to make it big clear.

>> Yes. Yes. Maybe go in presentation mode.

Okay. Bush.

>> I am going it but it is trucking here. I

don't know why I'm not getting full screen for here. You people are getting but I don't know. I'm getting a half cluttered screen here in my system. That

is why I'm just using this. I have to check what are this. What is this bug? I

don't know.

>> I mine is Mac. I don't know. Sometimes

problem is there in this Mac. Yeah. So

this is the this is a very extended zool architecture. Okay. Whatever I'm just

architecture. Okay. Whatever I'm just showing you here. So that you can I'll just drag and drop it here also for you for your easy convention here. Don't

worry about this. Okay. So as you know the zool studio we have seen yesterday in build apps. Let's say it's a comprehensive platform for developing

and enhancing your AI capabilities for all the futurerrich user experience right so that because it is powering with business users and technologist

whoever both they are to become this next level of a citizens or a developers or a consultants you call me for that.

So here this is a deep dive architecture which will help us to understand the zu studio can be leveraged to integrate or

if you want to extend SAP and nonAP solutions across different different landscapes. Okay. So if you can see here

landscapes. Okay. So if you can see here this is the first important thing. So

you have your experts your desktops your end users your application client your SL everything is there. So this is you have to understand one thing that the

complete architecture is under this SAP BTP. If you can see nothing is there.

BTP. If you can see nothing is there.

This is the main BTP console and on on BTP console is there. Everything is been architected and at the network level you have other things are there like your third parties or your cloud solutions or

your on-premise blah blah blah whatever it might be. So the network I'm just you know hiding for this now for now because anyways we can think that the network is there when it's going on there. So on

initially the first phase is the end user. You can say the end user he is

user. You can say the end user he is connecting or he is talking to this cloud environment. Okay that means the

cloud environment. Okay that means the build environment whatever you call the so-called build environment here SAP build is your next important layer. That

is what I'm doing right whenever I'm logging into SAP BTP I'm going to the build. Okay. And then I'm going for the

build. Okay. And then I'm going for the Java application client there. There I

am using the Juul studio. Right. This is

what we are doing right. So while using the jewel studio you already saw that we have jewel skill. I showed you how to I mean how to create a jewel skill. Okay

there we have this a agents also. So

these ones we will first of all create right the moment when you gone for this one. Let me parally show you this one

one. Let me parally show you this one also. See the moment when I landed here

also. See the moment when I landed here as a user what I'm going I'm going for the build apps. Right. Right. And here

what we are doing we are creating a jewel skill. Right. This is what I'm

jewel skill. Right. This is what I'm saying. when you create a jewel skill to

saying. when you create a jewel skill to correlate with the PPT this is what see the jewel skill I creating so when I create I'll creep it like that no I will deploy them right through buildwork zone

or something I'll deploy them right so this is called deploying so that deployment will happen here okay that means the deployment will happen here but yes it will take other direction

I'll tell you later point just understand that you will deploy it here and here whatever the delivery and custom skills are that will be there in this deployment platform. Okay. And

there is no link directly to here in the AI core if you can see and after deployment it is here itself only but there is a separate arrow that was integrated to your SAP AA core that

means if you want to that means your Joel is not directly linked to a core but your studio is linked to a core that means your deployment platform is not linked your application platform like

your SAP build apps is linked to your AOE that is why you can whenever you create AI agent and agentic a someone talked about that whenever they want to make a models or document grounding then

they have to use this AA code this will not work then okay so this is your step four this is your step five okay that means here the deployment will be the

last part but you have to understand in case if you are using agentic AI if you want to get the A models you'll get that here this is integrated here so once you

create that a aentic or some other skills also So that will be integrated to where here to your BPA which is business process automation. Okay.

Nothing but your all this build apps, build code, build work zone all these things comes under that only. Okay. So

once that is done then you will deploy this. Okay. So when you deploy this

this. Okay. So when you deploy this again the deployment will take here and then this will be again passed to your destination and connectivity and it will

reaches to your end service partners I mean sorry this that will checks the data for your end service partner for the connectivities. So you can see here

the connectivities. So you can see here the connectivity is multimodel here for onremise for third party for cloud applications okay multi multi connections are there right so these

will check the connectivity parallely on this this is a more detail architecture I'm telling you see the first important point is the central point for consuming

this zulu skills and a agents will be created in the zoo only okay this is available both in desktop and in mobile

client also So this Zul studio okay so zool studio is what it is nothing but your conversational interface okay you will converse with it right you are getting something you're talking to it

so it has some conversational interface patterns will be there so which it will leverage from the SAP cloud applications okay so wherein which whatever the out

ofbox capabilities and custom jewel skills you want significantly enhance the key business process you can do it still because it is significantly interface it there. Okay. And this is

part of SAP build. This is completely build environment only. Whatever you're

doing here, the BPA or everything whatever this is a part of build only because build apps whatever I showed you now here this one in our architecture this build apps. Okay. The moment when

you go for Joel skill you will see the prompt there. Then you will see the main

prompt there. Then you will see the main menu there for the zool. See BPA is showing as BPA under build apps. Right?

This is what I'm telling. Build SAP

build is a main platform for you to include all your apps, build code, build work zone, bring uh build process automation, whatever you want to bring it. This is the main platform. Okay. So

it. This is the main platform. Okay. So

it leverages this builds user experience and life life cycle management capabilities. So even to provision this

capabilities. So even to provision this jewel studio also we can see here this is a jewel studio where in which this one also it will be provided in your that means this build should be in your

target landscape along with your BPA and all these things and that is the reason if you can see I have added all these applications here even though this is my major one all these ones are internally

work for build apps the application studio sorry this BP and build apps are common on the work zone again this is separate application separate I'll show you that So like this build is your main

environment to access all these internal things. See now the app has created a

things. See now the app has created a zool studio right. So once you have configured once you have been you know like into this environment I mean coming

back to my PPT here. So, Zu Studio will enables all your new capabilities that can be deployed alongside your capabilities that has been configured by

SAP like what are the capabilities nothing but the ZUS call is your capability I mean zulk is your capability a agent is your capability like this these capabilities will be automatically configured so these will

do what these will automate your rulebased task using APIs and you can start integrating into your SAP for productivity enhancements. Okay, dual

productivity enhancements. Okay, dual skills. Whereas AA agents, I told you

skills. Whereas AA agents, I told you whenever you want to handle more complex things, more complex challenges with very advanced or complex planning,

reasoning kind of things where you have to integrate a kind of SAP nonSAP kind of things are there and then you have to go for agent age and all these things.

Okay. Both you can extend Juul by adding your automation optimization capabilities which are already existing in your Zulu studio. Okay. Now you might

ask hey what this AA core is doing. So a

core here it is as I said it will extend the dual capabilities it provides basically one second just one second.

Yeah so going to here. Yeah this a core here whatever the llms that I have talked that large language models. LLM

means large language models whatever the AA core it will provide that LLMs those can be leveraged to configure your A

agents here this model will leveraged to configure your A agent that is the that is why I am integrating this two here okay not only that customers can also

provision their own document grounding I told you the initial day about document grounding right so that document grounding capabilities will be also inherited in this a code. Okay. So

whatever the for example you are doing a banking operations or something when you want because you have your own set of banking documents. So whenever customer

banking documents. So whenever customer ask it so they have to do a document grounding on that right. So for that customers can also provision their own document grounding not only agentic models and all these things. So like

this a core can leverage your rag services. Rag means retrieval augmented

services. Rag means retrieval augmented generation that we call rag. Okay. So

this will be leveraged and this service through this service and then it can integrate them through this models into agents and you can ground them whatever the specific data that is why in the

studio if you have seen that I have shown you these ones you have I'll just show you one more time so the moment when you create a jewel skill here I'm just putting something here the moment when you get it so even it's agent K

also this is now an app now here you can create agent also I show you that little later I mean in our sessions now here when you go here for The connection you're asking this is asking right call

action run automation okay run process send message these are all so to do in between only you will add this whatever the agentic a things whatever are there

you will add here only that is where you do the document grounding will be done that through okay so this will integrate them and make the specific grounding

will be happen on top of this okay so specifically a core is your BTP's runtime to execute your MI sorry AI ML

workloads. So why it was integrating

workloads. So why it was integrating like this? because it will train it will

like this? because it will train it will let you to train your fine-tune models or scheduled jobs or whatever you are deploying through here you know like these are all standard APIs you know it

will be get trained in your a launchpad okay so it will run a workflows it will expose your secure secure endpoints it will standardize your operations so lot

of things it will do okay but now you understand that this is a developer runtime in AA core to build and host your models and pipelines Okay, at JA

level the end user assistant can call your a core endpoints here and then they can use their develop your score this zulu skills and a agents. Okay, that is what this is in deep. I can explain

there is a much more if you want to talk about AI code, it will take three, four to three to five classes very bigger generation AI is there but not required for us. This is enough for us in the

for us. This is enough for us in the ZU's perspective. Okay. And then the

ZU's perspective. Okay. And then the next one is the BTP connectivity. Here

you are seeing this whatever the connectivity. Okay. So it integrates all

connectivity. Okay. So it integrates all your existing workflows as you can see here either the AI agents or the automated execution for SAP nonSAP systems, network systems. You can see

these are all being integrated to BTP's connection through destinations. Okay,

different different destinations I told you. So with this connectivity what

you. So with this connectivity what happens? You have a greater efficiency

happens? You have a greater efficiency and you can leverage all the different connections in automation. Okay. So once

customers create their jewel skill whatever the custom jewel skill or either a agent whatever they can use this particular skill in SAP's builds

life cycle capabilities to whatever they want to compile and deploy this along with your jewels instance. So what on once they do this deployment what happen

this will grant the business users to access the functionalities to help their prompts whatever they wanted and whatever they can switch for between SAP non SAP applications also these are also

happen through this destinations and connectivity when you integrate them okay so this is once this is what if you can see the entire block is given to connection not the individual blocks the

entire block so it will check for that So your jewel studio here it will integrates via the connection services and BTP services external services also this integration is based on all the

APIs I told you. So it provides through various channels and various things will be there even your web app restful programming w and capam as you have already heard that these will also be

there in that and jewel studio it's continuously as I show as I showed in the last picture this is one I showed you so this is a more advanced picture for this so this will continuously rely

on your this one which is your cloud IT services okay so for authentication and identity management where in which this is a central console for all the

identity access management. So it will offer uh secure authentications, federations, you know, whatever you want. So SAP cloud identity directory we

want. So SAP cloud identity directory we call this one is identity directory.

This is the one which identifies all your services that can serve as a proxy for your customer own identifying pro providers. So for this this one used

providers. So for this this one used authentication provisioning. I already

authentication provisioning. I already told these are all leveraged through SAML and OADC authentications. You can

see here everything is internally compod integrated even through your uh if you go to the uh towards right you can see for your backend systems also whatever

it is connecting through this sample authentication only. Okay. So this is

authentication only. Okay. So this is one such thing which you can understand.

So other than that as when I have showed to you so let me come back to this for the configuration I have took the permission for. So he will again lock

permission for. So he will again lock it. So let me show you the book. So I

it. So let me show you the book. So I

will not execute completely. I told you I already so but yes I'll show you that how you can do this things. So whenever

you come okay let me go into the first part the practical part if you go to your account this is your sub account first of all people who are new they might they have asked the sub account so I want to show sub account creation also

a global account will be provided to you will not create that a global account will be provided to you while you have been licensed okay you'll get an ID and password that is your global account that's it there is no separate thing

that you do on the global account okay this is my global account if you can see tech private limited is my global account. So in that nothing will come.

account. So in that nothing will come.

See here the sub accounts what are there? Only those will come. Now what

there? Only those will come. Now what

you have to do you have to create a sub account initially whenever you are leveraging for your zool skills. Okay.

So these are all admin activities but as people asked me to show the configuration setup and everything I'm just showing you to you right now. So

just understand that I will not execute complete task. This is my instruction

complete task. This is my instruction from my admin. Okay, this is also I'm just giving you a note point but I'll show you this once. So now once you create a destination here let me show

here. So if you create see this is a

here. So if you create see this is a switch global account will be there. You

can create a sub account sub account from existing subway account directory.

You can do like this. So when you create a sub account you have to put a name here. So let's say for example I'll give

here. So let's say for example I'll give demo azole something I'm creating like this.

So you have to give the region as I told you there will be multiple cloud platforms will be there. You can see here SAP Neo is there my our cloud and

we have Microsoft Azour we have our Google cloud platform Amazon web service all clouds are there in this okay so what is the nearest one that you can

choose okay based on this choosing also sometimes your rate parts might get changed so be very careful when you're doing that let's say for example what is the nearest because I'm in Indian time

zone I'll select the nearest one is India Mumbai okay the region for I'm going for GCP. So the subdomain it will be automatically configured and given to you. If you have any subdomains, you can

you. If you have any subdomains, you can also get that. Okay, this will be a part of URL for your accessing it will automatically giving to you. So the

parent one will be this one. If you have multiple global accounts, you can select that one also. But in general there will not be any multiple global account. One

global account where you have to retrieve or you have to you know like go through it. So this is one such thing.

through it. So this is one such thing.

There are some advanced options also there. This same subway account you can

there. This same subway account you can use for production also. What is this use for production means I'll tell you the because in terms of budgeting what

people are using because I have seen in my last project also the same tenant you can the same account or same tenant you can use it as your testing tenant and

later you can use it as production also or else that means you can remove the directories everything you can back up the data and you can go for the production also they're using for the budget perspective that's happening like

that but if you Now specifically you're creating a sub account for bigger environments MNC kind of architectures or banking architectures you should always have a separate production sub

account. So for them this will be again

account. So for them this will be again used for production. The moment when you mark it as production this will be gone under to complete production controls.

Okay because your development come testing have liberality but whereas in production have complete locking features will be enabled for it. So

where in which your admin will do it but I'm telling you a point and that is the reason it was not showed it was on advanced options. Okay, if you want to

advanced options. Okay, if you want to go for a beta feature that means more advanced features in this all things will be there but you cannot disable the setting in subway code once you have enabled. See here this is how this will

enabled. See here this is how this will be. So I don't want to do all these

be. So I don't want to do all these things but I have explained you what it does to you. Okay. Now just simply if you create this sub account we can

create no worry no harm for this just test delete later. I'm just giving instruction to him. The subway account if we can create this see the subway

account will be created. See India

Mumbai GCP has been created. This is the first important step you have to do while you are setting up your environment. Okay. So let it it will

environment. Okay. So let it it will take little time. Okay. If you go into this also you can see what is this. If

you go to the overview of it you can see the overview of this up account while it is creating. See here my region my

is creating. See here my region my provider environment. Okay. And I don't

provider environment. Okay. And I don't have it is a cloud foundry environment by default. You have to enable the cloud

by default. You have to enable the cloud foundry for this up account. Whatever

this up account you do right you have to enable the moment when you enable cloud foundry it will ask you the plan and everything. Okay. Now if you go for

everything. Okay. Now if you go for standard plan this is a standard plan.

So this this involves generally some cost. So I don't want to put all these

cost. So I don't want to put all these things because there's additional cost to the system. This is already a planned version. So I don't want to make

version. So I don't want to make anything. I'm not enabling anything

anything. I'm not enabling anything right now. So here you will enable it

right now. So here you will enable it and then you will add the entitlements.

This is what I have shown to you here.

If you go to here, this is where our zo is there. This is your cloud funary

is there. This is your cloud funary environment. This is your entitle.

environment. This is your entitle.

Entitlements means what all services will be there. You will search it and you will add it all the entitlements by default. Few things will be

default. Few things will be automatically added. If something is not

automatically added. If something is not there, you have to just go through entitlement and you have to add it.

That's it. Nothing more than that. Okay.

This is what you do as part of the initial thing. Once this is done, what

initial thing. Once this is done, what you have to do is the next important step is you have to establish the trust.

That means you have to configure the trust. So that one in the security if

trust. So that one in the security if you go down, you'll have the settings.

In settings you have this trusted domains. That means whatever the domains

domains. That means whatever the domains you want to connect with like success factors, Ariiba, other cloud environments whatever are there the domain whatever you want to access

through your subway code that you have to go to this trusted domains and then you have to add them whatever the domain specific link will be there right that you will add it here like we have added

this one ondemand dot this one. So this

domain will be added. So once this is done you go to the trusted configuration and you will enable the trust for it.

Okay you can add all the identity provider. See this default I told you

provider. See this default I told you just in the architecture right default identity provider this is by default added and identity provider for custom applications. This is both these are

applications. This is both these are defaultly added. This is activated. So

defaultly added. This is activated. So

like this if you want to download any metadata also you can do it but this is all admin activ. But for your understanding I'm telling you this is how you will there will be a thing called enable trust. the trust

configuration will be enabled there and you will enable it. So once you enable it that's it you'll get the connectivity and everything and then your communication API enablement will be

done in back end and you can ready to start your zul things. Okay, this is what a basic setup in BP you will do it.

Okay, destinations you will create I'll tell you that. But before that let me show you on the boosters part. So if you go back to main account so I request it's a request from admin also don't

create sub accounts okay because this will impact on the cost factor because I also have delete immediately after this okay >> you don't even have an access for creating a sub

>> okay okay nice I don't know if I if you have I'm just giving caution to you that's it in the boosters if you go to this see all boosters will be there wherever you want to configure so this

is your booster environment So you just simply search for zool just go don't go through the entire thing here the setting up zool will be there start it >> can you just give like you know one or

two minute one minute explanation of what booster is please >> uh sure definitely yeah so this boosters are in BTP basically whenever you are

especially like this is a like a vizard kind of tool that will help us in the BTP to set up the sub account entitlements or services or configurations whatever you want to

Instead you go manually system has recently added that as a automatic service to you that is called booster you're boosting what an automation an initial setup of automation you are doing like creating your relevant

service sub account in this like zoo is one such thing which you are doing that right that is what the booster it will configure services it will guide you like the step by step what you have to do it will ensure some consistency

without you know going for manual errors kind of things you know all these things will be there like if you can see zu booster it provid ides the sub account.

It will entitles your work zone. It will

see the trust certificates, trust configuration and it will automatically subscribe the service because many of the BTP manual things were not working properly when people are going for manual because lot of things are there

and people confusing. So it was added as a booster as a step by step you can automatically drive it that is booster.

Okay clear >> thank you.

>> So now this is a booster for zu. So it

is taking prerequisites. You can see I'm not able to do this. Now you can see this authorizations are done. I can able to do that. My entitlements are done. My

authentication of identity tenant is also done which I'm able to do that. So

this is what prerequisite will set up for you. If you go to the next you have

for you. If you go to the next you have to set up the sub account. Sub account

means what for your zool services whatever you want to do you will do it.

Okay. This is the basic service which system will automatically take it or it will configure it for you. So that

entitlement will be automatically taking just you have to select your sub account which one you want to do because the moment you create the initially I told you this sub account we created now demo

a zol is what I created right which one we created this is a demo one right yeah I know so that sub account whatever you created activated that one right that

will appear here. So whatever the zoo configuration that you want to make it available on the relevant sub account that you will add here. Let's say for

example demo AI zu is there. This is my sub account. So automatically it will

sub account. So automatically it will gather your org details. The space also space is nothing but is a development space. Okay. Where your uh development

space. Okay. Where your uh development you generally create for blast radius and everything that will be there. So

this is that space. And then once you go to the next part, it will ask you for this production.

>> Okay. In the last screen, can you show me the plans as well? Once the drop down for plans, >> I'll show you in the subway plans.

You're asking, right?

>> No, in the previous screen only.

>> Very.

>> Yeah, that one. Yeah, that one.

>> Yeah, this is foundation and standard only. Any standard we generally go for.

only. Any standard we generally go for.

But this is already application is on foundation by default. So, I'm not changing that.

>> Okay.

>> So, you can see the required kota also.

How many kota is there? How many can use it based on the license? This is only one we have. So one is showing here.

>> Thank you.

>> Yeah. So now this products will be there. What what products you want to

there. What what products you want to add in your subway account? Let's say on for zool you are using buildwork zone sack datas spear. I'm adding everything here whatever now existing for this

integration. So so you'll get lot of

integration. So so you'll get lot of things. So this one you're using for

things. So this one you're using for testing or production you have to mention because I told you right for production sub account separate will be there. Testing if you are maintaining

there. Testing if you are maintaining sub rate you have to create two sub icons for that for testing one production one like this and all products whatever are required for that you will select it and then once you go

for this you will go for the capabilities so in the capability package you will see all these ones okay you can add the automation so you can see here store conversion data submitted

by users for the improvement of zo so as the data controller customer maintains full access to their data and can request it retrieval or deletion whenever needed that is general note that will be given by

system the it's a check for you if you don't want to store the conversion date conversation data you can uncheck it but generally we want to store it so this is by default checked it but still it is enabled if you don't want you can

uncheck it okay so now if you go to the next one you will set the integrations here so in the integration the formation name will be automatically taken by the thing if you have specifically something

you can give it there is no worry it will not affect is only name Like you can key Z demo for example some banking customer. Okay system is automatically

customer. Okay system is automatically included. Okay. Now you have to provide

included. Okay. Now you have to provide all these systems whatever because earlier you added some integration systems right. If you remember all these

systems right. If you remember all these integrations I have added the identity sack build all these things. Now for

this you have to in inform which specific domain will be there. The

domain systems you have to add it. So

for identity this is by default on demand will be there. sack already is configured. That means this domain

configured. That means this domain should be configured in your BTP by your admin. Those ones you have to add it.

admin. Those ones you have to add it.

Okay. Now this is your BPA. This is your build work zone. I'm just adding and this is your data spear. This is your success factors. So all this domain

success factors. So all this domain should be before on hand only have to be configured by your admins. Then you can configure all these things like this whatever you want. Okay. So once you add

all your include systems whatever and the relevant URLs also and then you can say next this will be reviewed completely what you're going to configure what do you integrate what is

your capabilities what is the integrations everything if you say n it will create whatever the new subway counter created on that these capabilities will be launched in it so

from there whatever I'm doing right now you can go click it do it so whatever the development you do it it will be configured on that particular sub account. Okay, I'm not finished. This is

account. Okay, I'm not finished. This is

what I told I show the entire process but I will not finish it. Okay, I'm just canceling it. This is a strict

canceling it. This is a strict instruction for me. So this is how you have to configure your sub accounts, configure your zool. Okay, clear

everyone. Now ask your questions.

>> K in your previous screen right? So

sales analytics cloud was there. So is

that the related domain? So what is what is the domain related to esport? That

was my question.

>> Espana is there right?

>> Which one is it? Actually I did not I mean I was trying to see the >> that's what doain will be there you can add that one also it will be also there it is a service basically you can see in the systems here see

the moment when you go there is a main service you will not get that as a domain internally here if you go here this is the one which we added right >> okay so so the last

trying to put in all the destinations is that what you're trying to do in the last step there >> right right whatever see on you created BTP sub account now you want to Access Zulu. How you access Zulu? You have to

Zulu. How you access Zulu? You have to set up whatever I have shown to you.

That is what you have to do.

>> Got it. Got it. So I have one other question on the previous you basically showed the integrations right. If you

can go back to your the Ppts where you have integration. So one question there.

have integration. So one question there.

So basically in this particular one see what I understand is the build apps is a place where you build like mainly even a Joel skill or something right? You want

to build you will first build it >> and then you deploy it. It will go into the Joel workspace the build build workspace right that's what you call it build workspace >> build work zone build work zone huh >> build work zone now

>> now that is the deployed one meaning like that is really available for anyone to actually query and use right that's my understanding >> anyone means who is actually aated to do

it yeah >> yeah yeah the end user so now the only question I have is now if you see the end user here in this chart they are not directly talking to the the instance

which we have deployed actually they are actually talking to the build apps Juul studio my question is like why is it like why are they talking to the one which is in development I thought that

they should be talking to the Joel that is deployed in the build work zone right >> that's what right the end user is talking to Joel application client only here if you can see here this is application client >> yeah but this application client is not directly linked to the one that is

deployed right it is actually talking to the Joel studio which is being built >> oh no no that is that will internally talk but it will not be showed to user right the moment you are asking something it has to go to the zoo studio

from studio only right this is a prompt for you like you have to assume this is a prompt for you the prompt is going to here to the studio where your skill has been created from there all your story will begin again for your backend

checking or process orchestration and all these things will come to >> no I mean his point is his point is zone studio what we use is a design time

artifact right so when an an end user triggers a prompt using J application client right so it should actually interact with the runtime artifact not

the design time artifact so the the jewel agent jeul or a agent are in je studio so which doesn't actually run when you exude or when you trigger

prompt so basically should interact with this runtime artifact which is in jewel tenant so that is jol build zone that is where I'm saying Yeah. Yeah. Yeah.

>> This is where now this is integrated now through your build process automation all these things. This is your work zone is also internally is there. Yeah. It is

it is also interacting here also.

>> This particular >> maybe if we can see we can see an example we can get a better idea. I

think >> yeah you'll get it that while while I'm I'm going for the practical part you'll understand that when I'm doing that.

>> Okay. I think that's that's a good point because this particular box what you have as SAP build also has SAP build work zone.

>> Yes. Yes. Yes.

>> Yeah. It has the instance which has actually been deployed. I was just confused by if you see the right side right next to >> don't confuse don't don't confuse. Yeah

don't confuse this is all on one these are all different different purposes we use it do console. So you have to understand this is zool studio design time runtime where actual execution artifacts live and run your runtime in

zool time whatever you are going for.

Someone has asked me that right. So

that's it just don't confuse when you are maturing your sessions you'll understand more clearly those things.

This is a standard SAP's like thing I'm just explaining to you. If you go into the practical understand more clearly.

Any other questions?

>> So could you please >> someone is asking right?

>> Can you please show us how did you get into that when you're creating a jewel like a some jewel skill right from the sub account? How did you go to that

sub account? How did you go to that screen?

>> Which one?

>> The jewel skill you created like some XYZ or something like that.

>> This is a build. This is a separate that we are when we have gone to your entitlements right in this one.

>> Second. So when you go to this one, when you go to your sub account here, >> yeah, >> on the sub account, you have your instances and subscriptions. When you go to there,

>> sub account and instance and one second, sorry, one second, one second, please.

Okay, can I go to subscriptions then after that?

>> Yeah, subscriptions only. In the

subscriptions only, all your skills will be added here. Here you will just click on your build apps.

>> Okay, >> that's it. So this will open your build studio and then you will create your zool skill here. That's it.

>> We don't have that any of the zulu skill in our system actually.

>> Can you please share it if you can show me what is the issue?

>> Okay, >> just let in the main you can just show it to me.

>> Yeah, we don't have that basically option.

>> Oh interesting. I don't know everyone is allowed for this. You have you can do this this there for everyone. Yeah,

because we don't have we have a create create from git, clone from git and add from dev space. That's all. We don't

have that fourth option. Whatever.

>> No, no, no, no. One second. Can you

please share your screen? I'll just show you that also.

>> Okay. How can we share the screen? Okay.

>> I'll stop the share and you can share it.

>> This is what I asked everyone to please check your systems. If something is missing, I'll let ask the admin to get it done.

>> Can you see my screen now? Yeah.

>> Yeah, I can see. Tell me. Aa. Oh, this

is one. Can you please close this and add BPA basically? So this is what

basically? So this is what >> XY Z is what I created. Okay. Go for

create. Go for create. Go for create. Go

for create. First of all create first one. Create. I'm not seeing your screen

one. Create. I'm not seeing your screen only. Create. I can

only. Create. I can

>> application.

>> No no I'm not seeing your screen yet.

Just please hold on. Yeah. Now see there is a zool skill on the third part. That

one you have to click it. Then it will appear in your create automatically when you create first. Yeah. Now next.

>> Yeah. Now we do this thing for once and then it will be automatically appear in system. Okay.

system. Okay.

>> Okay. Yeah. Thanks.

>> Any other questions guys?

>> So hello. Hello. So so regarding the document grounding you mentioned right?

Normally PDFs and all you said like catalog knowledge catalog will be there where we keep our documents. So suppose

there is a wiki link wiki page or some other web page where we need to write read those web pages and then do the document grounding and give the results

to the user when we prompt something.

>> So is that possible via June?

>> I don't I don't think so. You can what you can do is you can get that thing I mean whatever the page content will be that means you're touching the document

grounding let's say that means you want to ground zool with the content of wiki page right that means you have to you can do it but the access control should be there because it's very simple you

have to register your source that a wiki source in the knowledge catalog then you when you index the content the user prompted whatever the URL you are giving ing then it will automatically get the

grounding retrieval there and it will answer from you generation page it will be done but you should have all the access control to do the wiki documents that are authorized for that is the only consideration you have to take and

because it is external pages for public wiki pages we usually don't >> not not public not public suppose think like it's a enterprise pages which is

organization >> you can export import repository that's what I'm saying Yeah, >> that's what I'm saying. Listen, so you have to export this or either import this content to your control repository

and you have to index it. Then this

pages will be automatically accessed for your grounding retrievals.

>> So web scripping is not possible >> directly not until unless if you have access control it will be it will be it is possible. I'm not saying it is not

is possible. I'm not saying it is not possible but it you have access controlling things for that whatever the web URLs that you want to access for that.

>> Okay. Okay. So maybe this training will be practical. I'm not sure whether you

be practical. I'm not sure whether you will cover or not but any >> I'll try to show it. Yeah, that is an interesting point. I'll let me try to

interesting point. I'll let me try to show it if I can do it. I'll just

remember me but I'll try to show it.

Yeah.

>> Or else any document or steps to follow maybe we'll try.

>> Yeah, I will provide it. I'll provide

it.

>> Yeah. Yeah.

>> Yeah. Okay.

>> I am also not getting the dual skill option because if I go to build app, >> can you share your screen? Can you

please share your screen?

>> One minute. come to build up but it's showing create create first create first create >> okay so >> yeah now Joel skill next now create

there give some name randomly review create >> okay yeah got it thank you >> okay okay guys so good one when you configure the

integration through booster right and you mentioned the production testing so is this something that we anything we'll do in the testing then move to production or we simultaneously develop both the thing together.

>> Yeah, that's what you know this all depends upon your requirements. You can

sometimes use your one single equipment for your development plus testing as well and one for production. It all

depends upon your budgeting that's what you know I told you right the last one we used for single for this production and development also the same one in a similar manner we have used it yeah but SAP will help you on that if you have a

limited budget scopes on this but SAP will help you on this yeah right so now we will create a destination let me show you and we can bind this session for after creation of that let me share back my screen

>> one another question so I think somebody asked the same question right it's very similar so I am doing So I mean normally the landscape is we have a development

box ITG and then a production box right so we doing a we are doing any kind of like this deployment in manually on like development box and then how do we

migrate this to ITG and then to production boxes >> in in zool you're specifically asking >> yes >> okay so it's a normal thing only because this >> because normally we will have like a TRS and all that right but in this case how

does it work >> yeah whatever you are doing deployments in this dev box right this is a BTP plus jaw design time work so this ends up with a lot of runtime artifacts will be

there so you have to understand that you know there is a promotion strategy for the subway accounts will be there because I told you right a subway account for dev subway account for quality subway for production you have

to build it and then we have a separate transport mechanism we call sap btp transport management service that we call TMS okay or else we have this CTS is also there for hybrid landscapes

where you can use it So here what happens whatever the skills you do in the jaw that skills you have to that will be that skill or agent a agent whatever it might be you will export

them from development to quality and then through this BTP transport management system. So there will be a

management system. So there will be a kind of ids will be generated internally for the skills and that will be like in our ECC how you generating the TR ids TR transport requests are there similarly

the ids will be generated for here also when you're going for this internally and those you will import in QA for the testing and everything and then you'll further transport them to your production so you here the thing is you

don't migrate manually but you use system called transport management service system where you move your skills and agents from across the landscape with different different destinations and credentials will be

there each time they will pick it up automatically. Okay. You won't see

automatically. Okay. You won't see something a dialogue. This is the TR.

This is a TR. Okay. You will directly do the things and backend system will handle all these things. Clear? Yeah.

>> Will you be able to show like as part of your session like in your sessions like we'll be able to show at least some of these steps? I know you might not be

these steps? I know you might not be able to push to another environment but at least show us where to do it.

>> Yeah, definitely. Yeah, this is not an content but still I show you. Uh just

remember this point also as for someone has asked me. Yeah, I I'll show that.

Okay. Thank you. And then this one, let me show you destination and then I'll conclude my training for my screen.

Okay. So you come to your destinations.

I told you right in the connectivity pattern you'll have your destinations, destination certifications, destination trust and all these things will be

there. Right? So as I already told you

there. Right? So as I already told you what is destination in BTP. Okay. So

these are different different destinations you can leverage for your different purpose. See here this is for

different purpose. See here this is for Aribba. This is for cloud for customer.

Aribba. This is for cloud for customer.

This is for field class. Okay. So like

this you can do a kind of different different things on top of this destinations creations. So destination

destinations creations. So destination in BTP is basically a configuration object that will stores the connection details to our external system going to

connect like for example you can see this is for Aribba. This is connecting that Ariba connection. Okay. So what

this contains I'll show you. When you

create this destination, it will ask you from scratch, from file, from service instance. Okay. So, we'll

go for from scratch. From file means if you have already all your technical parameters or inbuilding in one file where you can leverage that, you can directly go for the file. Or if you have already having a service instance from

which you can create, you can do that as well. Okay. But this is a new

well. Okay. But this is a new destination. I'm going from scratch. I'm

destination. I'm going from scratch. I'm

just creating it here for your understanding. So let's say this is the

understanding. So let's say this is the destination destination demo. Okay. So

the authentication you have to give it.

I told you right while creating your destination you should have this oath to authentication should be there. Right.

This is what O2 client credentials or if it is JWT barrier bearer we can go like this. You have so many oath to things

this. You have so many oath to things are there. Your admin can correctly

are there. Your admin can correctly guide you on what you are going for this. But basically whatever I know that

this. But basically whatever I know that we go for this one. Okay. If it is SL assertions we'll go for this one. That's

it. So this is the one which you'll go it the moment when you go it it will ask you. Okay. And I already told you a

you. Okay. And I already told you a number of times you have to put the destination type HTTP. This is what the type HTTP. Okay. So there are many other

type HTTP. Okay. So there are many other things are there but HTTP is one such thing which we use it based on your architecture. If it does changes you

architecture. If it does changes you have to change this one. This is the client ID. So these are all will be

client ID. So these are all will be given by your client only. So I don't know this client ID. What is this? I'm

just giving something randomly for you.

So this is >> so client ID for what client is that one cable? Yeah, your development know

cable? Yeah, your development know whatever the source clients we are going for this right. So that is your client ID.

>> Uh in this example we are trying to create a destination for SAPS400. Okay.

So is that's the client ID means like generally we enter in our system which is like 100 or 200 whatever it is like SAPS 400. Client ID is that the one

SAPS 400. Client ID is that the one >> sorry what is that? I mean in ECC whatever you do 10. Yeah, something like that. That is the client ID here or it's

that. That is the client ID here or it's something different.

>> No, no, no. This is the client ID here.

It is for your oath authentication. Here

in BTP specifically, the client ID identifies the application with this number. When a request when it tries to

number. When a request when it tries to request an access token from an authorized authentication server provider, the client ID will identify that it's like a certificate to this

authentication you're giving. So in BTP destination what we do we often see this oath to authentication and all these things. So for this to identify the

things. So for this to identify the client ID that means in which uh authorization server this authentication is triggering. So that server ID is

is triggering. So that server ID is nothing but client ID not your ECC kind of ID here.

>> Server of >> that means it identifies your application to the W to token service.

That is what this ID will generally do with this is what SAP BTP will um tell if let me say if it is connecting from let's say your BTP let's say you're

connecting to SAP BP trust management service let's say you're going for trust management service now for that client ID will be generated when you create an instance of your trust management

service and bind it okay in that system so that is nothing but a service key for your JSON in the trust management service that is your client ID.

Similarly for cloud system also when you register an O authorization client in system it will generate a key that key is nothing but your client ID getting that

>> okay so is instead of this one can you just close this one and then you have some existing already destinations right >> I'll show I'll show >> is it possible to go and then display mode >> I'll show I'll show I'll show I'll show I'll come in that I have to show the

creation destination also right so that is the reason I'm showing you so this is your thing that is why here you have a checkbox use your token retrieval if you want to use your token retrieval services also for this client ids you

can do it and then if you have any client secret names or something you can make it or if it if you don't want you can make it empty and this is your proxy type internet yeah

>> I think I need to add this here uh the client ID and client secret is like the user ID and password right so when you create the service key in that you get that JSON right so in that JSON itself

it is mentioned the client ID and client secret that is for I think That is what it is used for. I I remember using this uh in our systems as well.

>> Yes. Yeah. That's what I think there is a secret note is nothing but your password here. Uh you can together make

password here. Uh you can together make use of your client ID and password here.

Yeah. This ID I told you that generation of key will be there. That is the ID nothing but here you can use together this ID and password here or your accessa and IAS or success factors

whatever are there those you can use it and for this whatever the link that is generated during the token generations that you will add that service URL also wherever you have been uh doing done that

>> yeah because I remember yeah because I remember seeing it whenever you create a service binding a service key is created there right key you have the client ID and client secret.

>> Exactly.

>> Exactly. The destination call calls token service URL. This is one the destination generally calls for this your ID will be there and that there is a secret which is nothing but a password

or a thing will be there that you have to enter entry it here. If you want to set empty you don't have anything such thing you can always keep it empty.

Okay. Because few things that don't have the passwords or secrets for that that you can omit for that. Okay. So here

basically why this is token service is there this verifies your access tokens that means whatever you're going to access that is valid or not for the APIs to call or not to your S4 HANA as

success factor AIA that will be commonly verified here that is why your token service URLs will be enabled here okay clear everyone so this will be your common dedicated and then your URL for

this your proxy type whatever you want to generate link on which this one so this will be there so if additional properties are there like if you have any specific keys for your web ids or HTMLs everything you can put that values

if you have any more authentication for that so rest all it will be normal like this you can create it okay so now existing one I I'll show you anyone one which is here the Aribba one I'll show

you yeah the existing one you can see here the authentication same thing you can see the token service URL here okay which is dedicated for this only this is not common not shared across okay and

then you can see they Use the basic credentials for token service. You won't

see any client ID and client secrets here. Okay, this is additional

here. Okay, this is additional properties here. These are all

properties here. These are all additional properties what I told you.

The provider types, queries, labels, everything they have kept it here. And

these are all the SL properties. They

have gone for SL assertion. So these are all by default came for it automatically. Okay. In case if you want

automatically. Okay. In case if you want to edit the existing one also, you can edit that. You can see here like this.

edit that. You can see here like this.

Can see here. See this is all been there. Okay. And here there is no such

there. Okay. And here there is no such client ID properties are there. It was

been already done. So you're not seeing that. So these are all externally added.

that. So these are all externally added.

If you want to add existing ones also, you can add with the can add the new properties also here. And yeah, this is these are all the SL properties they kept it. So they're getting all these

kept it. So they're getting all these things. So this is how you can just

things. So this is how you can just configure this is existing one which is already done. Okay.

already done. Okay.

>> So this is how you test this connection like we enter we created a connection destination connection. Can is it

destination connection. Can is it possible for yet like to see to test the connection with the >> oh you can test the connection always yeah once you create destination you have to add certificates for it and then

the destination trust also have to enable it and then you can check it for this this is what I'm saying once you create the destination the destination certificates you have to check it if there is any certificates you want to

create for this you have to create that as well because some services need some certification service and all these things so you have to put that service also certificate which is optional Okay.

So, discard this one. I'm not showing this one. And then you can go for the

this one. And then you can go for the destination trust for your management services here. Just let me for this here

services here. Just let me for this here one second. It did come here completely.

one second. It did come here completely.

So, you can see here for now this is your destination certificate trust certificate which has been generated there. So, we can see the validities and

there. So, we can see the validities and everything here. Okay. Once you generate

everything here. Okay. Once you generate you can see the validity when it has been done and at what time till it is valid. You can renew we can export the

valid. You can renew we can export the certificates also. And again going back

certificates also. And again going back destination if you go into this any of these things here you can check the connection from here directly you said me right you asked me that how can I check the connection if you can check the connection it will tell you whether

it is working or not like this is not working right now an error type unknown host is coming here so like this you can just check for any other connections you can check the connections for this see

this is back end is reachable okay this is how we check the connections if any connections you want to duplicate you can duplicate them if you want to delete them you can delete them so All these parameters are already enabled for you.

Okay. So this is how the destinations will be done. So once your destination is ready, everything is set for you to go ahead and play with the environment.

This is what you have to know in the BTP. Clear? Any questions guys? Clear

BTP. Clear? Any questions guys? Clear

everyone?

>> Yeah. So just one follow up on this one.

So you'll be showing us so now that we have like HANA and like you know Aribba connections ready to go. you'll be

showing us like the data when we have a jewel skill like when we are building like you know an app or like you know however we want to call it so that app will be able to pull the data from this

S4 HANA and Ariba and we we'll be able to see that right >> yeah you will see that yeah which is preconfigured kind of data we can see that yeah from S400 >> yeah so any kind of like data like I'll

show yeah okay yeah >> so one quick point so previously you showed like you know in the Joel We saw some connections right like for

unable success factors and all and then here we are seeing destinations. So is

there a difference between the connections we saw on the destinations here? One second. Hold on. Let me sh

here? One second. Hold on. Let me sh screen is coming not. Yeah. No, sorry. I

am actually in my Yeah, you're asking something. Sorry. I have not cons.

something. Sorry. I have not cons.

>> Basically, you basically previously for sub sub account wizard, right? You know,

there are different steps and towards the end there was like some connections like you quickly selected some success factors and all of that. That is one thing you did over there in the sub account configuration

>> and then here you are actually configuring some of the destinations. So

is there any difference between the connections and destinations?

>> Yeah, connections you know like the system you trust and register on S4 HANA tenant and all these tenants will be there that is through connections and destinations means these are the technical details of your connections on

which your flow will generate that means for example you register an S4 system that when you register where you register in connection it will when you register a connection it will establish the trust via your communication

arrangement. Okay. Then you create a

arrangement. Okay. Then you create a destination naming some xxx_1.

So this destination will point to your S4 API URL with your oath details. So

connection means it will know who the system is like how it has to trust is destination means how to technically call the API through the connection.

This is internal. So basically it's more like the connection is like the face and this whole destination has all the details behind it so that the real call can go go through correctly.

>> Exactly. Yes. Connection is your trusting and registration of your backend system. Destination is nothing

backend system. Destination is nothing but using your configuration objects that for that you need to know like use your API calls and everything for that particular connection to happen. That's

it.

>> Okay. So one actually asked like okay if at all we have to connect to wiki right that's a very good use case uh you know do you think like we have to create a destination for wiki if that was

>> what we want to do so for document grounding right >> using wiki to actually do the grounding I mean should we actually have it like a destination only then we will be able to access the wikis correct

>> yes because that is what I'm saying you have to register the source first of all but here the connections and all these things will not be too involved alternate. Here you have to in the BTP

alternate. Here you have to in the BTP cockpit the knowledge catal you have to add a connector there where in which you usually bring certain because this is a web web wiki pages. So you have to bring

them through a web connector and you have to sync them to your document repository. That means where your

repository. That means where your document management services or your things will connect. Then you have to index your content. That means whatever the wiki page content will be chunked and indexed there that you have to by

using your SAP document grounding services you have to chunk it and you have to you know like make a meta data or indexing kind of thing for preserving the title sections URLs kind of things

whatever in the wiki pages you have to do it that the user can prompt it easily and then the retrieval can happen from the document grounding easily from that.

So this is how the generally works. Yes

in BP cockpit you have to add a connector for this. That is the answer for me.

>> Okay. Okay. So, definitely there should be a destination. There will definitely be a connector. But apart from that, you're saying there's more to do in the knowledge catalog, right? We haven't

gone there, but >> that is something you'll be going there, right? Knowledge catalog.

right? Knowledge catalog.

>> Yes. Yes.

>> Thank you.

>> Awesome. I'm done for the day guys.

Thank you so much. So, I have covered as per the I covered all the setup architectures. Okay. Security I have not

architectures. Okay. Security I have not covered completely. I'll do it in the

covered completely. I'll do it in the later part. The connection testing

later part. The connection testing backend systems we see we have seen and configuration security scenarios I also have shown to you on this hands-on on the module two of your MPC we have seen

the setup for SAP modules and we have g we have gone for the deep of the architecture we have seen the connection extensions backend systems you know that hands-on also I have shown you how you can configure how we could do the

security scenarios you know all these things we have discussed so this week we will be seeing so slowly our uh things will start into this you know but yes few of the things that we have start

with you know in this the module three that I'm starting which is uh uh business use cases with zo so in this we have to learn first of all the natural language transactions and prompt

engineering for SAP task and then you will be seeing the workflow automation with zo and some of the role based journeys okay so these ones will be there so in this I will start parallelly with you you know like showing you the

zel environment slowly so in module four you'll get you know complete maturity on that when you end of the module module four you'll get the build plus develop development as well. So that is for so this is that this model will be a basic

for you for your module 4. Okay like

that. So the first important thing is the natural language transaction. So

these are the important things that you have to know. Okay. So see let's start this natural language transactions.

Okay. So one of the other announcement I want to do so that there will be no class as there is a local holiday here in India. So again our class will be on

in India. So again our class will be on next on the Wednesday. Oh sorry on the Thursday. Okay. So this is just

Thursday. Okay. So this is just information I'm giving you. So yes, so when starting with I'm starting with the natural language transactions. Yes. So

traditionally when we work with SAP we have to know some transaction codes.

People who know on SAP, ECC or R3 kind of environment there we have to know transaction codes and on the public cloud we have apps kind of things but still you have to remember the app names or something but if you still can

directly type it it is still you getting the help. So you don't need to do lot of

the help. So you don't need to do lot of brain work there. So when you have to remember so let's consider the ECC environment right now. So whatever I'm saying the ACC environment so that if

you consider like that so you have to remember what kind of different for example you are a finance guy so then you have to remember what the FB50

transaction code majorly the BL3N the FGL03 these are all the important E codes for refinance right so similarly for purchase orders you have to go for

ME23N people everyone of you know who are already into SAP right and like for deliveries you have to go for V02N and VA01 for sales orders so on whatever it

might be right so which mean was almost like a system only for experts okay so the moment when you don't know the key code you are lost

because I don't know when where I have to go for delivery where I have to create my sales order where I have to know like for an error if some error come the delivery or something where I

will you know validate with my finance you know what is the exact edits These are all things happen you know because this is all the t game in SAP. So you

see we have went with right. So that is why we have gone with the next level generation came with theory with all the apps you know subsiding all this T course now in the public load and all

the things right. So but now with Zel the barrier is completely gone. So

natural language transaction here we call it as NL or NLP. NLP is your natural language processor. NLT is your natural language transaction. Okay. So

this mean we can simply say what you want in plain English. Okay. Always when

you're giving for prompt also you'll get it. Okay. Or not only English because

it. Okay. Or not only English because Zul has whatever SAP is supporting the different languages. Zul also support

different languages. Zul also support all those languages. Okay. It it will it might go in in the near future every single language it will be covered.

Okay. So any supported language and SAP will understand translate that into a technical action and deliver the result.

So that is the end thing that you're going to do. Okay. For example, a finance user he can type or say show me all open items for vendor 3000 in

August. Like this you have to clear.

August. Like this you have to clear.

Yeah. This is called prompting. So a

procurement user we can ask what hey list or throws orders that are pending above 1 lakh rupees a kind of thing okay

like this. So now you think about the

like this. So now you think about the power of this earlier when you had to call an SAP expert what you have to do you have to raise a ticket directly from

SAP I'm talking about not at the internal project organization level I'm not talking if you want an expert in SAP even in your SAP or something these days you have to ticket for a SAP expert or

you have to wait for your SAP consultant or IT help to give you certain report or certain thing to help on it right but with Zulu. What happens was these this

with Zulu. What happens was these this these are called barrier. This is what I told in the in the front my my speech I told one thing the barrier is gone.

These are all barriers. These barriers

are gone. Understanding that so business users now themselves can perform these task instantly with the required authorizations. Okay. So let's take a

authorizations. Okay. So let's take a simple imagine you are a CFO. Okay. your

or else your CFO calls you and says hey what is what is our GR balance right now he might ask you so traditionally what you have to do you have to either if you're an ECC consultant you have to go

back to the relevant ecodes you have to check it you have to get the data or you have to you know like u uh check for all those balancers you have to know like put them export and then you have to

give it to him or else if you open query we have a simple app called display line items app everyone knows that So you can set filters you maybe download to Excel or it could take certain time for you at

least 20 minutes, 15 minutes or at least 10 minutes, right? So with zu you can simply type like this similar scenario.

This is called natural language transaction. Nothing nothing you know

transaction. Nothing nothing you know hard in this. You can just simply say show me current GR balance for company code N101 or something whatever the company code

10,000 or something whatever it might be. So within seconds the answer is

be. So within seconds the answer is appearing on your screen. How? Because

it connects because I told you the art last week. So it will connects all the

last week. So it will connects all the relevant tables and know all the things or prepare the thart get the charts and it will show you on the jaw prom. So

this is the promise of natural language transaction. Okay. So SAP is

transaction. Okay. So SAP is democratizing all these transactions. It's no longer about know like knowing the P code because as you already know the P codes

are now almost not existing you know in many scenarios we are going with when the P theory came into the picture the entire game of SAP has really changed as everyone know that right so this is one

such thing you know like how this natural language transaction is you know like changing the SAP face it in the scenarios right now because in the

context of SAP this always refers your NLP that is by SAP to enable users as they can interact with SAP software using everyday language. Okay. So

whatever I just told you. So this makes what SAP systems more accessible. It can

allow more users to perform task and the developers burden will be released and the users who want to analyze their data they can analyze their own data easily and they can generate reports simply by

conversing with the system itself.

whereby what happens lot of lot of lot of technical hump is I mean technical efforts can be reduced it doesn't mean

that it is something replacing but it is helping as a whole on this as you all know that you know there is a kind of you know like I I know it's it's like something going on in the world that it

is really replacing it might be replacing but it not replacing the entire industry where the supportive task are there so there it is replacing yeah so and This the board is really not

allowing right now to make complete replacement and it might not also happen because this will really give a lot of other things in the other dimensions also as everyone knows that that a

replace everything here. So anyway so people have to so one better thing what we have to learn is how better you can manage this also that is what old is telling then know if it is really doing

kind of support activities generating reports or something someone has to know how it generates what it generates what kind of things it can generate they have to learn how it this needs to be happen

so this backend front end things is right now world is learning so that is one thing which you are also learning right now so this is how SAP leverages

is AI and NLP to understand the int in a natural language. That is where it put

natural language. That is where it put all these things in the conversational interfaces. So users can engage in the

interfaces. So users can engage in the conversations with SAP applications much like they would be like a behaving like a human. So this is about the natural

a human. So this is about the natural language transactions. Okay. So this is

language transactions. Okay. So this is one such thing which you have to understand. And the second important

understand. And the second important thing in today's thing is prompt engineering for SAP tasks. I'm not

talking about prompt engineering for our other a bots or something as you all know what it is. So but as I'm just specifically telling you what actually can be done as part of the prompt

engineering and SAP task okay so I given you a brief SAP's uh NLT now okay so now if natural language transactions are the

found now we already understood that NLT is your foundation right for what for all your basic zool activities right so when the is forming a basic for you or

the found for you Then prompt engineering does what? This is the skill that makes this powerful. These are all interbinded. Okay. So prompt engineering

interbinded. Okay. So prompt engineering is simply the art of giving pure instruction to Zol. Okay. Instead you

saying something nonsense, you have to say something meaningful to the system so that it will get the things as it is because machines understand prompts clearly rather than what you are talking

on that. it will still understand in any

on that. it will still understand in any language whatever but the correlation might go in a different manner. Okay. So

think of it like this. If you talk to a colleague and you say hey give me the sales report. They will come back and

sales report. They will come back and ask what which region what sales report which product which quarter okay what segment. These questions you ask right?

segment. These questions you ask right?

If I ask you also same thing hey give me sales report will you give sales report to me? No you will ask again some

to me? No you will ask again some question to me right? All these

questions what I have generally asked this is what you have to think as a as a machine okay from the human's perspective while you are asking to zool

as well that is the only thing so if you don't specify these things so they might give you a generic report that's not at all useful to you because zool is the

same for like all the a contenders are getting data for you okay the moment when you ask sales report it will give you default sales report No, with this irrespective to your regions, products,

quarters, segments, whatever it might be. Okay, which will not be useful for

be. Okay, which will not be useful for you. So this is how you have to. So here

you. So this is how you have to. So here

how do we engineer the prompts for SAP task? So let me show some of the

task? So let me show some of the important type of prompts that you generally do. So in prompt engineering

generally do. So in prompt engineering also generally I'll give you a very basic this is a very deep subject but still as in the Z just have to learn something on that. So there are some things will be there in the prompt

engineering. One is your direct action.

engineering. One is your direct action.

Okay. And second one will be your analytical query and third one will be your investigative and fourth one will be your advisory. These are your different types of prompt engineering

things that you can generally make on top of this. Okay. So let's say direct action means you put a direct question to it. Okay. Like say for example if

to it. Okay. Like say for example if you're understanding you can say hey create a sales order for customer X with

material Y with quantity 20 like this like say I'm just writing for you also for reference in the recording so this is how your palms will go with so this will be understanded by it so this

customer having this material number with this quantity it needs to get so primarily very basic in a language you are just getting all the primary data for this to know like connected that is

called direct action very simple all primary case for example if you are seeing your social security number your passport numbers your number these are all nothing but comes under he can for

for example if I want uh some of like details in this in this group I can ask hey get this details from the standard customer database okay and this database

name you can ask or something or you can just you know like uh from this uh for this customer get the data with and matching something like that you know you can ask like that primary keys where

it will actually directly hit and get the data ready. So this is how the direct action works in the prompt engineering analytical queries means here whenever you are starting comparing

because when you go for end of comparison between across multiple uh years or multiple months in the functional chart we generally need that for example if you want to compare

revenue for one quarter to another quarter or if you want to see your balance sheet for this year to next year. Okay, these are all functional

year. Okay, these are all functional tasks we generally do with right. So

these kind of things you'll go with the analytical query. So you have to start

analytical query. So you have to start with a term called compare. So you can write like this in a analytical query when you want to generate a chart or something like you can say compare

revenue of year 1 versus year 2 for any product line. You can use

product line xyz something like this.

can give your statement to the prompt engineering in the prompt where it will start getting the data for you. This is

how you have to ask the analytical queries. Okay. And investigative

queries. Okay. And investigative

all your investigives will start with actions with questioning. Right?

Investigative comes with question. So

why, when, where kind of scenarios.

Okay, this is how comes here. Okay. So

for example, if you have some variations in your production cost of order, if you have variations in your balance sheet, if you have variations in your receivables or payables, okay, lot of

things will be there. So when you are having investigative, if you want to do the system to do it, you can also do that. Instead of you going and taking

that. Instead of you going and taking some time into it, you can ask it directly. For example, you can ask why.

directly. For example, you can ask why.

Always investigative should start with why. So you can ask why is there

why. So you can ask why is there variance in production cost of orders for order you have to give the order

number also let's say I'll give 1 0 0 1 0 0 something yes so you can ask that so then it will again let you know why there is the variance in this order if there is no variance it will tell you

that there is no variance observed like that also because this is how you can do investigative things also in resolve.

No, for such kind of scenarios and advisories things go because not only that it will give you direct answers, analysis, investigative but advisory things also it will do. What does the

prompting advisory SAP task do? It will

suggest actions for certain things that you are liking to do or you want to do or you might have something to do on that. All that suggestions, all that

that. All that suggestions, all that recommendations, whatever you want based on SAP best practices, not something as a customized one, it will tell you okay

go for it, do for it. No, nothing like that. Whenever you go for advisory, it

that. Whenever you go for advisory, it will check the internal SAP best practices. It will check your databases

practices. It will check your databases and then it will act it. For example, in the in the functional scope only as I'm speaking right now, so I'm just ask I will be asking the same thing for the advisory as well. So like this we can

ask questions like for example suggest okay suggest actions to reduce my overdue

receivables for the year 2025 you can ask like this. So the moment when you ask system will actually interact with the internal databases what you have

been connected on that and it will what is the overdue receivables by the year 2025 and what are the actions we can reduce for this overdue receivables also. This is what it will do. So like

also. This is what it will do. So like

this advisory kind of things also you can do which means as a whole you can you can get a help for your investigations you can get a help for your salutance for the betterment as

well. So when you get us on the better

well. So when you get us on the better and what you can do you can start taking the necessary actions on top of that right so that is how the prompt engineering and SAP task help you

properly when you ask a question it will gives you a reply based on that your further actions can be taken okay but yes now let's let me talk about some techniques in this because I told you

the different types of prompt techniques different type of prompt engineering task that that will be happening in SAP but yes when you are asking something to

the system. You should be specific like

the system. You should be specific like for example simply you should not say anything to the system. You should

always be specific to the system. Let's

say you should not say for example hey don't like for example know you should you should not say show to sales for certain years that's it will show you have to say as I said earlier in the

example show sales for this material or for this entity in this region in this quarter or in this year you have to clearly tell that okay so those are

called conditions any individual that you go for this zool you have to go for condition you have to add some condition for right? Like each given month or some

for right? Like each given month or some number or some dependency where in which you'll get an exact data. Okay? And you

should always ask for a format. Format

means what? Either in a table or either in a chart or either in a document kind of thing. When you're asking you should

of thing. When you're asking you should tell it clearly. Sized boards are constraed dev platforms. It will not give you the complete things as well. So

it will assume that it has to give something. it will give you some clammed

something. it will give you some clammed or cluttered things only where you will not get the full results. So while you are asking show me in a table or show me in a chart or summarize in a bar chart,

summarize in a pie chart. So you have to ask like that whenever it is giving details to you. So it will give you a neat charts also where you can easily copy paste your dashboards as okay and

the beauty of Jolie is you can refine it. Okay. First time you're asking

it. Okay. First time you're asking something you'll get something second time you can refine it. For example,

first time I asked hey show top 10 customers by for example overdue receivables. Okay, it will show me

receivables. Okay, it will show me something then I can ask hey this is okay split by aging bucket then it will split it for you again also you can ask it because it will continue the same

question again you don't need that again for that if you're going for conversing so for example on the sub messaging bucket if you want to still find you can ask hey highlight those that are linked

to my balances so it will highlight it like this is a conversational you don't need to start from scratch each time remember that okay but of

course what I want to say here is there are mistakes that are there you have to avoid also like for example it may return an inter results you overload with too many details also that might

that might you know give you irrelevant results also so your question should be specific at the at the same time it should be simple for it to get it so as that I told that you have to be specific you have to you should not give every

single like a big query so it will get overloaded okay because it always has to understand simply and you have to refine that. You have to always uh remember one

that. You have to always uh remember one simple thing. There is a technique of

simple thing. There is a technique of you know understanding there is understanding a smartboard you should ask something and start making conversation top of that you should not be very specific at some time you have

to should not give a big query at the initial stage. So system will take a lot

initial stage. So system will take a lot of time or you you might get wrong results also at times. Okay, that is how the prompt engineering also a very big thing these days. You should go one by

one you prompt zulle with one thing and start refining refining refining until you get it you won't take much time but yes the refinement will be easy for you like a refinement is nothing but a

subquery for you. If you think in a database perspective you are giving one query again you are adding filter adding filter adding filter you are just defining the query. Okay. So in the

future SAP consultants won't just prime businesses on decodes but will prime them on how to prompt effectively also that is happening right now but they also for the purpose of zulu that is

getting integrated every environment this should be also there. Now you

starting right now you also doing this now you will get knowmed with it easily.

So this is the one of the important thing that you have to understand on the prompt engineering. So till now on NLT

prompt engineering. So till now on NLT and prompt engineering anyone have any questions? one quick question. So see

questions? one quick question. So see

one thing what we understand is basically you know SAP one of the major advantage of Joel is that the it is always like grounded you know it understands our business data and all of

that correct that's what we understand but what about the custom fields and custom programs custom function modules we create in the system does it really understand you know whatever we have

created if for example like even within a you know standard table right like just let's take a small sales got a table right you might have some additional fields where we have created

extra fields and all of that can it understand those fields >> yeah it will understand why not see all that's a very important point that you have got it yeah let me break it down let me break it down clearly for you

because zool doesn't magically understand your z program and custom fields no uh unless we teach it so zool handles generally kind of way where your

standard versus custom obvious will be there okay your custom fields are there for example in the AC token say you added some as you said some sales order or some regions as a custom pool in your

some quer so you have to expose them via some CDS views you have to register that in your API business hub and then in dual studio prompt engineering you have

to add a prompt first of all for all the custom fields custom programs custom views whatever you do you have to add prompts for it system will not take directly you have to add for example you

added something like in Aca like in certain plant or region. So you have to say show me journal entries with plant region is equal to not. So this prompt should be internally there you have to

map intent for it but to call your APIs what having your Z programs then zul understands that field because that is a backend response including it. If not

you are directly creating something and if system ask no it will get this prompt should be already been there in the system for these programs. Then only system will give replies back to you.

clear.

>> So yeah just not clear on one point let's just talk with a sales order example right so sales order there is a particular field that's what I'm saying >> now maybe maybe normally it understands

a lot of the fields right like for this how many sales are there and all of that that's a very normal query now if at all I ask based on that field right it may not understand that is what you're

telling me right even though >> yeah you have to expose it see will not understand your custom fields or Z programs automatically but if you expose

them via your O data API and map them is the reason I'm showing you skills zoo skills if you map to prompt engineering jewel will treat them like any other business object like and it will start

giving you the results so this is what >> I think I think we I think once we get into the jew skills maybe at this point okay that makes sense that makes sense

>> and one other question right so you made a valuable point Like you're saying that go go go one query after another right you're not going to put overload the system like it is like going one after

another now see it's all about now what we are hearing is it's all about cost also right like queries the number of queries you do and all so doing one big

query versus going query after query like what should we tell to our business like should we go query after query because again each query will cost you some amount of money right does it make

sense to really go the drought or is it better to have only one big query because it's only one query where you try to get all the information I'm talking more from a costbenefit point of view because now every call will cost you money correct

>> so >> that's my understanding >> so you mean asking questions should be limited is what I'm understanding your question so on on the cost >> yeah exactly because I I keep hearing that everyone is like you know getting

charged more I mean like more than expected because you know if they they ask like small questions right you So they keep on going like in to get some information if they ask like 10

questions is it really better they're doing like that way or it should be one question to get the answer because this is how we have to set our business right we need to ask the business people to

think in the direction so what do you suggest is the best way >> the best way is always you know you have to use this prompt for interpretation plus orchestration basically but where

heavy logics are there you have to push that heavy logic to backend script and AP that's where you can save the first because if you are increasing for unnecessary things because first time it will be okay you might feel something

playful and you will do it so that might actually know like increase you whatever you said is 100% true I like jewel run as jewel runs on these prompts cost is

tied to tokens like the moment of input plus output so if users are asking longer open-ended questions the cost will completely rise so that's why I'm saying this prompt engineering and

grounding becomes critical okay this is what I'm telling this This update is not that simple. Prompt engineering is very

that simple. Prompt engineering is very important. Each prompt

important. Each prompt uh each prompt that means your business query that hits the LLM and J giving the response that consumes one single token.

Input token is is equal to your question plus system interaction or something.

Your output token is nothing but your jewel reply. So SAP charges based on

jewel reply. So SAP charges based on your input plus output token. one token

for one individual that is they call one individual request or one individual or something will be there. So specially in the license zone the founder Peter has limits but in the in the license zone

you might have additional tokens where you can use it but the suggestion is always you have to use a structured prompts you have to shorten your responses you have should you should

have you know what I'm saying is the heavy logics or bigger things you have to always put it in the backend APIs and you have to reduce the limit on that so unless three things will put you there so this is the main my side

>> mainly what you're saying is instead of asking Joel to do all the operations better have APIs which it can call and get the things done. Correct? I mean to get the answer that way.

>> Exactly. Exactly. Yeah.

>> And and is there like a limitation like for example you ask like a very big query.

>> Yeah.

>> Does it means that it instead of taking one token it can take three tokens you know can there be like that?

>> That's what my main suggestion is going.

So don't let Jou think too much on raw data. The moment when you are putting

data. The moment when you are putting pressure on raw data it has to work a lot. then your tokens will be consumed.

lot. then your tokens will be consumed.

So give jaw for your language plus intent and like all as you said right now the custom field Z program reports are there into the back end system you have to push them into back end for wherever the relevant things are there

then you have to get it okay so that's how you know you have to use it at a higher level for now and at the back end level whenever necessary then only you have to use it but I'm not sure yeah

this is a confusion going the market also right now because if you keep Zo light what is the use of many users are asking how then what is the purpose of using that people are asking that right.

So you're giving okay a lot of good things are happening but you're saying like you know keeping everything on the plate and you eat only few pieces make doesn't make any sense you know people

want to use it heavily that is a behind quote for this but yes SAP has some like what I want to say they're getting with some bigger license options also where you can have unlimited things also on

this that is also there I think so this I can come with you some costing based things also where it will fit for you uh it's not that very limited as of I see right now but yes there is some cost

rising factor also when you do that.

Yeah these two things are also there.

Yeah >> see other than functional area do we have any kind of administration or GRC related task we can do like when it comes to direct action can we ask J that

give me the list of the permissions this users have from this module also like create a user with so and so permission.

Yeah, why not? We can ask administration jobs it will do but you know because Joey sits in your BTP so you have all these things can be done but I'm not sure whether it will give you at

initially all these things as it is completely role based and security is inbuilt in it it will give it to you because I never tried it. Um so yeah that what that's what I can see.

>> Okay so we need to test it even >> yes we have to test it. Yeah but I'm not sure. Yeah on admin side it is already

sure. Yeah on admin side it is already completely controlled but if you ask these many users what users you have to give whether you have an I think so it will give based on your jewel ID is

allowed to see your details. It will it will give you I think so it will not restrict you as of I can see. Yeah.

>> Okay. Thank you.

>> Any other questions on prompt engineering guys? Everyone clear? Okay.

engineering guys? Everyone clear? Okay.

>> Sorry. Okay.

Please go ahead.

>> Yeah, one question. So when this the query cost when it is computed, it's only in the production environment, it's applicable in the development or >> all environments. All environments

specifically not only production because even though the data is getting from there. So it will go in both your prod

there. So it will go in both your prod environment and development because on development you won't ask right only this is something that you go on the development license you might not see a bigger differences I think so but on

production they might cost you because that is the reason the moment when I have shown you the tenant creation right on the free tier that means in the development you'll go with the free tier generally so the foundation will be there where will you have limit you have

a fixed limit of tokens per month will be there so those once you exhaust it will be done so you have to like good that's more for your prototyping kind of things in the sandboxing whatever you do your free kota will be there in the dev

tier but in this licensed you will be your cost is directly tied to your token consumption as I said so either it's a development either quality either production it will consume from your

licensed kota okay so because it is bund your you your you will be the moment when you take a license it will have a bundle of tokens for your tenant so if you start talking to it the tenant will

start consuming your tokens as well is called we call it as a BTP metering. So

usage is measured in tokens and your service consumption logs.

>> Is there an option to say I do not want my one of my user let's say in a month to consume more than like maybe let's say 5 million tokens. Do we have that

level of control and capability here?

Because like you don't want Okay.

>> Yeah. You can set your tokens limit as well. No issues in BDP. You can have it

well. No issues in BDP. You can have it >> per user. Per user.

>> Uhhuh. Per user also you can set it.

>> Okay.

>> You can set it. Yeah, you can limit your tokens.

>> Could you also show how to do that in this training?

>> I'll try to show it. I have to check my things because last week my admin access was got after I have shown that. I'll

ask the admin to give it. I can see that directly inside studio. You cannot do it in BTPA core is there right there. The

governance will be there. There you can do it. But you can you can put it as of

do it. But you can you can put it as of I know you can put a cap on the kota's perspective on the block perspective. I

cannot I'm not confirming but I have to confirm you cannot set per user hard token caps I think so because when you use kota you can you you can restrict

per environment okay when you use prompt engineering also it will get that per per environment things only but I'm not specifically no I don't have clearcut idea but I have to check with SAP that

we can control on user base or not on the usage so yeah >> clear everyone these ones probably that's something I think that one of the very important point as well.

>> I'll write this point. I'll come back to you.

>> So per user limit tokens cap how much it is common problem right? It's in general like you know there will be some users like you know they might over consume it and there might be some users who will

under consume it. We don't want the code couple of days and leave the rest of the remaining days.

>> Right. I know I know you know you have to control your consumption basically.

So when you go for this role based restrictions you can only assign zool designer and zool user kind of roles to the right people. So you should if you prevent all the casual development users

because they will spam like anything all these problems if you give to them. So

they will play with it. The the moment when they're doing they might not see that the cost is affecting on that. So

that is the reason you have to prevent them. And in a launchpad also we can see

them. And in a launchpad also we can see per user perk still consumption there is that that particular thing is there. I'm

I'm I'm sure about that in a launchpad you can see how much of consumption has happened per user. So you can set alerts if monthly token usage causes a threshold you can say 50k tokens per

this group or something like that that is there in a launchpad but specifically in this for zool I have to recheck on this because the service plans will have certain fixed quotas will be there some

split kas will be there because lot of plans inside in SAP are there so even I also have to you know with them on the on this responses and everything okay I'll get back to you on this >> table there's also one more thing you

know that we have to get back on that's the grounding as well right so we just need to see >> at least a simple and example uh you know how to do the grounding because that's the core

>> I'll show you I'll show you I'll show you the example grounding example >> thank you thank you sir >> that is that yeah >> and in cable one thing see see jewel is a cross functional right it's it's connected to multiple system like it's

connected to your service now it's connected to success factor and all this thing right >> suppose I getting an incident ticket it'll pop up in the screen that okay this is the incident And it'll automatically reroute that how

to get resolve that incident like whether there is a order block and all this thing happening right. So in that way we it will be happen the multiple query right. So we think each query they

query right. So we think each query they will charge and this like that or it is a single query at the back end what we build for that only they will charge how it is like so you get a incident like so

order get blocked like user get a incident why it is blocked okay this is a shortage of stocks and all this thing has happened they will propose that okay this many option is there to resolve

that issue then it keep on querying in that way right getting a point it is not like that key order status and all this thing right it will be multiple things can be happen. So do you think it's a

single query wise they will charge or is something like we back end will build the entire query that that >> I'll tell you that how this works also I'll tell you that see z is open as an

enterprise digital assistant the first thing so by default it can multiple systems as you said so it's 100% yes if you configure instant management as a skill that means whatever the skills

that you want you have to configure first of all right I'll show you anyways these ones the moment when you Configure as a skill. It will show as you said as you are asked is happening show whatever

the open incidents what are the stated updates what is the same team what is the SLAS priorities all these things it will show so so here but Joel will not show details of the users has

permissions or something the second story but as you ask yes it will show but you have to configure if you configure it runs through the LLM orchestrator that means the moment LLM

orchestrator is involving tokens will start consuming Okay, because it will fetches what the back end data by API that part does not cost tokens but it's

your SAP system query basically consuming the tokens whenever system goes to back end data interact with API that will never charges that is free automatically because it's a process

system will start charging you when you are quering that means when it is returning the answer the output tokens will cost again okay like for example if you say same question you ask what is

the SLA status of instant xxx or Yway something. So input prompt it will take

something. So input prompt it will take that means you have asked something it will take 10 tokens there. Response

summary with fields to get it. It will

take 10 tokens there and you know and output response it will take 20 tokens altogether some 50 tokens of cost it will take. Okay. So like it might say in

will take. Okay. So like it might say in our currency or something if you start making one know like for the price it like 50 50 here kind of thing. It's not

very very costly but yes very low cost but it will cost for something to get it. Okay. So this is the way it will

it. Okay. So this is the way it will generally generate the moment you are putting even though incidents even though instant management even though it has to give it while you configure

whenever it's starting responding to LLM giving response it will consume some tokens based on your queries and responses. So that's what I'm saying.

responses. So that's what I'm saying.

Keep responsive structured. Use skill

level filtering. Use your permissions properly. This is very important. These

properly. This is very important. These

three are clear. Who has asked me the question?

>> Uh yeah. Okay.

>> Yeah. So this is what guys. Okay. Next

one. Let me go into this. So all doubts clear everyone.

>> Okay. But is there like any good material what SAP is giving like best practices sort of thing like how >> I I'll add it in the material section.

You can see this.

>> Perfect. Okay. So as everyone is asking me I'll just give you a outline also here how this cost work for you just for a minute for your understanding I'll give you a more detail in the next

session but yes this is a very important one so we have actually three individual tiles are there guys which is found in Joel okay so this is one tile okay

wherein which this is for development use only like satellite kind of sandbox kind of thing use so usually in the foundation you has Okay, fixed limit of tokens will be there. Tokens means these

are per month. Every month you'll have some tokens. Okay. So, example whatever

some tokens. Okay. So, example whatever your request everything will be there.

All request will go like this in the tokens kind of thing. So, this is best for prototyping when you want to go for t whenever you're going for prototyping this is the best for prototyping in your

sandbox kind of environment or to development also. So whenever your free

development also. So whenever your free kota is confirmed extra calls will not be get entitled and they will stop giving respons to you because it is a

free type that's it and if you ask me how many tokens per month fix limit means I am not sure because it is getting changed as per your things okay I have seen 200 to 2,000 some tokens

there because we have they kept a very less limit on it okay just to understand and in the licensed zool whatever that we go for licensing Okay, this as someone asked this you have only

production environments and quality everything can be enabled in this okay and in this licensed environment the costs are directly tied to your token

consumption okay that means prompt plus response so it's not per user as I said environment based environment consumes from your licensed code so

you'll get 20,000 or 30,000 I think so 15,000 tokens I think are there right now I'm not sure completely from your licensed kota. So Kota will be big but

licensed kota. So Kota will be big but you know if your your very big it might yeah but then again SAP will bundle tokens by tenant like you know some

customers get sub account knows also as per to global code strategies or then they have the sub account based token kas also available for SAP they can talk with the team of so this is your

licensed kota other than that as I told there is one more thing called BP metering okay so whatever you start using the a core service consumption logs are there bas Based on that the cost will be there.

>> So this is in separate to the >> yes web can see your paramement is also who is to bringing pawns how many tokens concerned which skills they have used why for what what they have used when

they have used all these kind of things will be there only admins will see these logs. So BP metering will be there on

logs. So BP metering will be there on top of that as well. So these are the basic things in Zoho which will work.

There are still more plans and everything are also there but I'll try to show you that one and you can I'll put a document for you to do. So support

team will add that to you in the folder.

You can just grab it from there. Okay.

>> Can you also know please add you know those three best you know practices uh you mentioned like you know use the skills.

>> Yes. Yes. Yes. I

>> know possible. Yeah. So I'll add it.

>> That's very important the best practices.

>> Yes. Yes. Yes. Yes. Yeah. Okay. So going

back to my content here guys. Okay. Now

the next part for our uh content goes with the third important part is workflow automation with Zul. Okay. So

so this will be there but before that so if you see here whatever I just told the moment when you go into this this is my sub account once again system. So if you

go to the entertainments basically so you will see your kota here basically all quotas can be seen here. You can see your see if you go come to a core is

free unlimited. So see what is the plan

free unlimited. So see what is the plan it is mentioned pay as you go for a safe for cloud TDD that means you have some even though it's unlimited that means you can use unlimited unlimited means

whatever use you use nothing not like that whatever you go for pay as you go is always means whatever you pay whatever you use you have to pay you always check one thing here in the

commercial type it is free you can use it no worries you have to always check it in the commercial it is consumption then it will give bill bringing to you.

Very simple thing. Either consumption or subscription both should not be there.

If it is always free, you are able to use all these things. Now this is a free t. I can use it with that because even

t. I can use it with that because even they have some limits internally certain. So you can use that. You come

certain. So you can use that. You come

to here for zool also you can see here subscription. So it will cost me the

subscription. So it will cost me the moment when I start using it. See is

already jaw embedded entry. There's a

subscription based. So based on my subscription whatever I have only those benefits I'll get it. Okay. If you go to the blue apps also this is where you start working on it right. You will also see here it is consumption. The moment

when you are consuming you know few things on this is again pay as you go for B2P cloud. Okay. So these plans and everything before you start know like adding them to the entitlements you have

to check it and you have to do it accordingly. Okay. Whatever free are

accordingly. Okay. Whatever free are there you are always open to use it. And

there is no subscription only even though it's a licensed version I'm telling you few things because for license they'll give you some as part of but for gave you few things as you few things as consumption few things

subscription okay so services what I'm saying about services right so like you can see in the this one also it is a launchpad also free right so again bad

studio consumption okay so like this these things will be there which will work and this one also consumption see works on where we generally deploy these things okay so your Java prompts also

when you see here as I said yesterday you go to the sub account once. So if

you go to the work zone standard here is where you will land everything. So

whatever you do in the build apps right because we integrate labs build zone with zoo everything they will commence with you originally in this one in this environment. The moment when you open

environment. The moment when you open this default work zone landscape you will see whatever you get this is where this symbol whenever you integrate it I'm just showing you as your outline

here now anyways in the next class you will understand all these things one by one you will see this diamond icon this is what I told the moment when you stay start you know the zool will start working for you so all your work zone is

integrated so whatever you do here specifically in the build apps sorry uh yeah build apps when you go to the build apps so this is your zoom tool that will

start indicated there. So this will work for you whatever the way you want it for example. So simple things I'm just

example. So simple things I'm just asking you here in the build work zone.

So I just ask use op code. So it was not you know see how it is behaving for this. So I just g this is not I have not

this. So I just g this is not I have not given any queries nothing is there but this how we use for the next purposes.

So this is the main one build and build >> jewel when I go open that the build work jone. So what about this on the left

jone. So what about this on the left side right side you're getting like a view job code request rights that >> and also we don't see that the diamond the diamond picture on the top also actually

>> so you go to the directory you'll get this default then in the default you have to go to this >> this is your project this is the environment created by admin you have to go to this then only this is the site

basically where you land all your developments okay so there you will get to clarity so this is how you have to get it you won't need to worry about this I already told them they will take care of this. Just you have to go for

the icon here then it has to work it then you have to check it that >> okay >> something I'm just just showing you how this is working or not for you see this is what so if you have any system like things are the system will tell you see

I'm not access to your sales order or job ports please check your system or contact for admin access for assistance so if there is any integrated issues are there you will get all these kind ofations okay anyways let me show you

here yeah now going back to here the automation of flows so everyone cleared where you have to check your instances where you have You can check your entitlements here whether it is free or not everything. Okay. You can see into

not everything. Okay. You can see into if you go to the instance also you can see your credentials here which will been created here. Okay. And also your organization's environment which was been created. This one also you can be

been created. This one also you can be in uh look into it more clearly for this. Okay. Majorly when you whenever

this. Okay. Majorly when you whenever you want to see your cost and everything you have to go to the entitlement. This

is where you will see your cost factors.

Okay. In the cloud for environment the moment when you create a subway account only it will ask you what what entitlements you want and what you have to add it based on that only it will add it.

>> Okay that's it. So next one >> okay one question on this one. So what

>> we are seeing on the entitlements like whether it's a subscription or whatever it is. So you're saying again between

it is. So you're saying again between dev and production dev can always mean that it is free until certain tokens.

Correct. Even prod also service as free doesn't mean that the moment when you I told you right I showed you how to create a prod by checking the prod a few things will be on free what this is a complete environment setup in the

environment you create that account you are not completely doing that so the environment setup it's not that fraud because of fraud everything will be consumption in prod also a few things will be free for you

>> so my point is you can choose to do it in two different ways right you can have separate sub accounts you know between prod and dev Sometimes you can have the same account

between the prod and dev. So the case if a situation where you have the same account in product and dev you know whatever you're showing here you know whether it's a subscription or consumption for the dev instance it will

always be free can we say that >> yeah for certain tokens >> yes yes yes on on that means you know for that but all depends upon your environment cap that's what I'm saying

if your envmentment cap is having these many tokens you can limit for environment like in development these tokens fraud these tokens you can limit like that It's not that because you

subcategorize something as a system will give you some free. No, it's not like that. If you are once you are licensed

that. If you are once you are licensed when you are making your when you are classifying your accounts to sub accounts into prod and then you have to limit the tokens in both the environments or you go

>> where will be the exact place where you limit the tokens like that >> in the entertainment global account level your global account can do that not you you create a sub account for

destin each sub account have its own security settings destinations and users right so there you allocate the entry elements like what is the token limit what is the service plan separate you to

each sub account from the global pool.

You're getting that as a global pool.

You'll have once you are licensed, you have 10,000 tokens. In 10,000 tokens, use for example 2,000 you keep it for de and 8,000 can be keep it for broad. Your

global pool will be same. How you use it is up to you.

>> And again between these 2,000 you can always give certain entitlement certain amount of tokens is it?

>> Yeah.

>> So it's again the entitlement level you can distribute.

>> Yes, you can distribute.

>> Okay. Thanks.

>> Okay. Yeah, I'm going to the next topic guys, workflow automation, right? Okay,

so let's move to something even more powerful now after the prompt engineering and all these things. So the

workflow automation in Z. So let me start with a question like how many of you spend hours or like approving, checking or reconing tasks that would be

automated in your daily jobs. Have

anyone have spent that that or if you have spent how much of time you generally spent for approving or soaking or reconciling tasks or data in your in

your organization? Like almost every

your organization? Like almost every business has this problem right whether it's invoices or whether it's purchase

orders or whether if you come for the leave request or let's say the so-called deliveries. Okay, approvals and checking

deliveries. Okay, approvals and checking will take lot of time, right? Sometimes

might be the process is simple but the system that has to be respond to you might not be simple or it might take longer time to respond to you as well.

Right? For example, if I want to approve a leave request also in success factors or something when you say in any other web tool kind of thing, you have to log on to tool, you have to see the go to

the request, check the request and then you have to give it like so. So work

this is called automation of workflows.

Workflow automation means you connect these business figures with automated actions and when Jules steps in, it not only triggers the workflows, it can also

guide you in the plain language. Okay.

For example, in finance when a invoice is blocked that you mismatch soon the in teams as well Microsoft teams or in any SAP work zone as well. So in procurement

also in similar cases your purchase order is for example above 1 cr. Okay.

Now you want something because certain limit above purchase orders generally what you do you will take some approval.

There is a blanket approvals right for this one blanket approval will be there.

These will be two kinds of two C of approval for this amount C approval head. So these kinds will be there in

head. So these kinds will be there in any procurement flows. So like this purchase orders or any orders that are at an limit of amount you have to route

to a special approval. So that is also the kind of automation you can do it.

You can get it. I mean Zul can do it and Zul can get it and he can know help you on this like even request as I said you know for example requests that are less than 2 hours can be auto approved. There

is no need to specially go take these kind of things are not there these days right there are no conflicts on this if there is less than two days do a simple auto approval if there's more than 2

days go for step one level on approval if this more than 5 days go for step two approval like this you can simplify your automations no workflows like now let me

tell you that you know generally how zool enhances this see zul does not wait for a workflow it can detect anomalies for example when I search you know

vendor payment something has happened so it will ask you do you want me send a reminder or a manage or you can say you know like you can say hey send what is send some reminders kind of things you

can say so let's take some realistic story imagine company has 500 invoices daily okay each invoice would go through

a manual approval team like your controllers your approvers your accountants everyone have to spend lots of lots of hours in this, right? So with

Zuul, the moment when you automate or do something with Zuul, you can just say, "Hey, show my block invoices that are about 10 lakhs for this entity or for

this particular region like that." So

Juul will brings the list and it then suggest would you like me to report some approvals because it's not that Juul will stop the question the answer it will give you followup conversations

like what is happen in your act or you know or Google kind of things so when ask you to approvals then manager says something to it and it might will

approve on instantly or system will update the post on that. So this is where Juul workflow automated

out not only about reporting but it's about acting to the queries okay which means because of when you when you start

bringing the automation okay it will ease your life with faster cycle times will be there manual efforts will be very very low and most importantly it

needs a data generating by system so it will every data in the system. So manual

errors will be very much you know like reduced when you compare to the regular way of traditional working strategy.

Okay. And most importantly it will free people from associates who can focus on other valued activities what they can do it like workflow automation in Zo like

you know it will gives you like what I can say a productivity plus saving the time for the for doing the other activities a kind of thing it will do

like the moment ask it will start acting this is how in the workflow automation it will do be very careful while you're also doing all those things because doing that will not cost you but after

doing when you asking that will cost you so doing for that so see one thing is true I can say it's not about the system

it is existing in the current society that you're going to use it how you use it is what you know it will brings you the the betterment of your lives as well you know you use for certain unnecessary things it will go for unnecessary

because example of zul I have 100 tokens or you have simply hey how are you what are you doing this kind have silly questions you know if you start asking unnecessary be getting burden right we

have seen recent example also start unnecessary burden because of some imaging processing that was happened on that really got burden it's no use of you know bringing photos on that even though a picture is given for a certain

other purpose but people use for some other purpose in a similar way in your organiz point point of view you have to use it for the people who can be better used for it get the data easily further

rather than you know giving for everyone access on that So that is the reason jewel is very limited for the set of people when you're ordering no and that is why it is licensed also why SAP

brought this also to limit the burdens on the LLMs okay if it is open free everyone can start you know on it like anything and you know the lms get burdened on it so that is a prime idea

that is what I'm saying in the next future in the near future you will get lot of good who want to use zul in this kind of way so you will get out of this cost factor also So that is also going

to happen as of I have seen some sort of road maps with SAP which I have seen internally because this is happening there. This is one such thing that you

there. This is one such thing that you can get advantage while you automate with the ZO and all your functional workflows. Okay. And not only that when

workflows. Okay. And not only that when you when you're talking about workflow automation lot your uh things right so that is called role based learning. So

every role in the enterprise sees SAP differently has different needs, finance has different needs, supply chain etc etc whatever you call it for the different different purposes different different

needs will be there. So Juul brings a private conversational journey for of for every of these segment and for each person. Okay if I start with HR manager

person. Okay if I start with HR manager can ask always hey show me all employees whose probation is ending this month. He

can ask that. So jewel can easily respond with the list and it suggest you like me to trigger some confirmation because who are on 6 months. So it will

it says who are already completed provision if there is no approval need can easily send Joel will send by default all those confirmation letters to this employees because it will have

all the database internally it is getting connected with okay so if you have to do the same work it will take for you two to four days of time to confirm to send letters to all these

guys. So HR not only saves the day but

guys. So HR not only saves the day but can also act on it instantly here. This

saves lot of time and improve the employee experience. This is what I said

employee experience. This is what I said to whom it is much useful. You can

implement and make the things productive on that. Not only which I just given you

on that. Not only which I just given you layman example you say the supply chain functional uh the finance as well. So

every on for CF force they might see the consolidation as well right. So if I want to see consolation I have to do a lot of things internally in the system even though I'm

at executive level for example. Okay. So

you can simply ask though hey show me consolidate P&L varies then so do this COA kind of thing system will show you clear financial statements okay you can explain the root cause of variance as I

told there is any unexpected overtime growth are there or overtime lines are there so you can explain the variances you can take corrective action and all these kinds of things will be there okay

so like this every individual they can get benefit from it okay and not only that the beauty is that these are not just questions and answers. This

is the journeys that you're doing with L. So journeys that are role based that

L. So journeys that are role based that are contextual that are proactive for you. Okay. So employees no longer can

you. Okay. So employees no longer can waste time by just navigating the Fury apps. Now instead what we can do Zul

apps. Now instead what we can do Zul brings the relevant insights, relevant actions, relevant workflows directly to them. Okay. So imagine a day where

them. Okay. So imagine a day where doesn't log into success factors.

Finance doesn't open fury apps. Okay.

But instead everyone talks to Joel like a colleague and they can start executing their task easily. That's it right. I'm

opening it all. I'm asking hey do this do this do this is doing because with an access I'm not opening success factors.

I'm not opening something. Okay. Because

at the user point of view it will be very very easy for you to understand these things. So, so as as a whole this

these things. So, so as as a whole this is how your role based journeys your workflow automations okay your NLP and prompt okay as a whole if I can say your

NLP makes your SAP simple and accessible your prompt engineering whatever is there in SAP task this unlocks all the betterment that you can do in the SAP

and the workflow automation what I told in the zole it will turn the insights into actions instantly where you can take of it and all your roles based on

these talong method will deliver the okay so all in all I can say with SAP zool when you know how to use it productively SAP is no longer a system

to use it's okay your next colleague for you to talk to and you can make something for it that's how this is being called for it >> just one question

>> I mean you spoke about the executive uh analytics right so I mean do you think sack you know dashboards and things like that you know would be of a great help

integration you know with for the analytics and you know dashboards and things like that you know for the executives and for the you know say procurement heads and things like that would that be helpful

>> yeah you can it will be very helpful for them for executives that is how right it will bring lot of value addition also for you the moment >> so they can go to sack isn't it rather

than you know going into SAP they log into their dashboards in sack and that's an integrated you know with of course in SAP and you know Joel and then you know there you know they have their dashboards now automatically that

can be done on top of the job implementation isn't it so so that's additional an activity isn't it >> yes Google can integate in stack so that

exe and consume all the analytics very easily yeah >> yeah yeah perfect thanks >> I just have one question so basically let's say if we are integrating Aribba

with esport and we would like to use the Joel capabilities in this scenario let's say your escore environment is on prem and but your ara is on cloud so how how

do we actually integrate it because usually Joel works only for cloud-based when >> it is coming my understanding uh you're integrating with Joel right >> correct so we are integrating Ariba with Joel

>> m >> because Ariba is on cloud >> but but your Ariba system is uh integrated with S4 where S4 is on prem

so in this case how can we leverage Joe's capabilities to interact with S4 system to retrieve any kind of information.

>> Yeah, it's not an issue. I told you that there are two scenarios are there. It's

a good question. Real world integration question you have asked me. See the

setup of Ariba then you have to set up your Ariba to on-prem to Zo. You already

have Ariba integrated with your on-prem is a classic setup which you have done that. Now you want to bring your ZO into

that. Now you want to bring your ZO into a front end which is a cloud environment. Okay. So this one if

environment. Okay. So this one if integration is already set up to you your jewel works as a conversation this can pull your insights across both the system. So it does not replace your

system. So it does not replace your integration but it will makes the integration for your business users in the conversation layer level. Are you

getting that the integration is possible? The first answer is and second

possible? The first answer is and second answer is integrate. No your aribba and s4 have integrated which is already done. So now when you integrate Aruba

done. So now when you integrate Aruba with Zo, Zo will start accessing both the systems that means you are exposing APIs of the both the system. So Aruba

APs will be get to Zol for your requisitions or contacts or whatever you call and S4 HANA onre onrem APIs you will connected through cloud connector because I told you destinations in B2P

the other day. So that is the one which will connect your cloud connector and which will connect your job skills.

>> Okay.

>> Yeah. Yeah. So it is a possibility that you know we can still leverage Joel capabilities on >> yes you can yeah when yeah when you're third party I mean Aribba kanker or any

of the applications yes if cloud something as for onrem there is no you can still get the jol capabilities >> I think it's important to add here if it's onrem you know system you know

connected you know within a jaw sasank I believe you know there are certain limitations you know you you cannot you fully use the capabilities of Jaw. I'm

sure you know I read that or you heard that somewhere in the webinars or things like that. So you can't you know fully

like that. So you can't you know fully use the jaw you know capabilities. I

mean if you are connecting you know with the onrem uh system you know I mean I can't recollect why but I think you know there is a constraint. tell you what is I already got and for know I have only

outlined it in the initial demo but I'm telling you when when Zel with S4 onrem happened there are some limitations are there like even security or network overhead competive cloud systems are

there where APIs are ready for that that is one such thing you can see and one of the limitation you see commonly on AP exposure VP where in onrem business objects may not have the modern APIs

that is one of the thing because they're still on bies and lighthouse kind of thing so jewel works generally best when with the standard the code data these are new things are there best services

these are coming right Juul works best with them okay so you for this what you have to do you might need to have some customs use app services to expose the

right data to zool so these are these are the areas where lacking of direct development is one of your biggest limitation when you go for on-pre direct integration method and on-prem also what

I practically seen is the latency and relative matches is Because Zo is completely on cloud each query will travel from cloud and then know it has to go to onrem back and then

come back to you. So if your connectivities or sidewalls is slow the response time will be very longer than you generally see with public cloud or S4. That's the problem with performance

S4. That's the problem with performance overhead know realtime queries when you go for on-prem integration. These are

the common limitations which I want to outline you when you go for on-prem integration.

>> Yeah.

>> Yeah. Perfect. So

>> all right let's test your knowledge.

Here's a question for you. What is the primary interface method for interacting with SAP Juul? Option A, command line interface. Option B, natural language

interface. Option B, natural language conversations. Option C, complex coding

conversations. Option C, complex coding requirements. Option D, traditional menu

requirements. Option D, traditional menu navigation. Take a moment to think and

navigation. Take a moment to think and when you're ready, choose the correct option. Remember, each choice holds a

option. Remember, each choice holds a key to unlocking the answer. Good luck.

Type the correct answer in the comment section. Hey there. Want to get really

section. Hey there. Want to get really good at using AI in SAP? Our SAP Juul course is here to help. You can take it at your own pace on our platform. In

this course, you'll learn all about SAP Juul. It's like an AI helper for work.

Juul. It's like an AI helper for work.

From asking smart questions to getting instant insights for faster decisions.

Our course covers everything you need to know from the basics to cool advanced features. It's made by experts who

features. It's made by experts who really know their stuff. Your teachers

are pros who've worked with SAP tools for years. They're here to guide you and

for years. They're here to guide you and answer all the questions you have. And

don't just take our word for it. Our

students love the course, too. People

just like you have found this training super useful. Best part, it won't cost

super useful. Best part, it won't cost too much. This awesome chance to learn

too much. This awesome chance to learn is really affordable. Ready to become a SAP Jewel Pro? Sign up on our page now.

And for more info, check out Zarantex website.

>> Yeah. So coming to session yes we are going to discuss about SAP build apps into which we will be seeing as you are seeing my screen already here. So we

will be discussing on the SAP build apps here and then we will try to build some application in the build apps. Okay. So

on on know like when we are talking about Zo doesn't mean you know like only on the Zo's perspective you so on the build apps also we have to learn like how to build applications on that. So

you have to learn few things on that and then parallelly as I said you know three environments we will be touching in this environments. One is the build apps

environments. One is the build apps which is a low code no code platform and in which we will see how you generate kind of web applications and kind of EA applications here and how you generally

use it how they how you preview it how you know like export them you know like these things we majorly learn on the build apps and build code is the one thing in which you know with the jewel a capabilities you will build something on

the build a so that is one such thing which you'll do and whatever the jewel skills that you do on the build apps also those things will alter integration that will be landed in the work zone as

well. Okay. So these are the detailed

well. Okay. So these are the detailed things we will learn not only this will take a few days of time one by one one by one slowly we'll learn but I'm giving you as a overview that these are the things that we are going to learn in

this next couple of days because whatever are there you know like the initial detailing I have already given on that aspect of the zool. So now we'll be going deep insights into little of

practical as well. Okay. Yeah. Now

opening the build apps. So before you do build apps always we have to ensure one thing on the BTP's connectivity layer.

So if you see here on the BTP you should be always in your sub account. So if you go to your main global account first of all. So there are some subway accounts

all. So there are some subway accounts are there. Okay these were created for

are there. Okay these were created for multiple purposes by my admin. But this

is our environment. If you can go preferably into our environment. So you

will be seeing some of these environment instances and everything right. So we

specifically go into our instance and subscriptions. Okay. So in this you will

subscriptions. Okay. So in this you will see HTML 5 application. So first thing you have to understand is so whatever you do in the build apps. Okay. So that

that will be just a preview to you. So

that will land in as a HTML 5 application to the build works. Okay. So

the moment when you do something in the build app it will directly go and sit here. Generally it has to but you know

here. Generally it has to but you know you have to check the layer. What I'm

showing you right now is they will check the destination first of all. That's

what I told you right the destination should be properly built in it. You have

to check it. So I'm telling you how you have to check it. So this is the before check you have to do before you going for build apps. Okay. So in the destinations you go to the destinations on the left side. So you will see the

destinations here. Here you will be

destinations here. Here you will be having these are all the different different destinations that has been created here. Okay. So for this also I

created here. Okay. So for this also I observed one of the SAP build apps HTML 5 repo the name is HTML 5 repo that is

not there even I have also observed that in I and I told this admin he told he told he will be initiating that yeah but that is not there only SAP build apa means process automation which is on

HTTP is there but there is one more thing which will be called I'm repeating that SAP build apps HTML 5 repo so this service should be there in your that

mean destination service should be there in your this destinations list. So then

only whatever you do that will come and sit in this HTML 5 application the moment when you go this is your deploying platform. So you have to

deploying platform. So you have to deploy means so whenever you do something in the build apps that will come and sit in the build zone environment. If you go back I'll just

environment. If you go back I'll just show you one more time. See here this is a pre-checker guys. I'm telling you whatever is all the pre-check. So this

is our work zone right if you go to the work zone. So usually just deleting this

work zone. So usually just deleting this one now. I will detail you about this

one now. I will detail you about this later when I'm talking when I complete about this one. But for now remember there is a content manager will be there in the build workshop. In the content

manager we go here. Okay. This is a content manager. Okay. This is a create.

content manager. Okay. This is a create.

So whenever you go to the content manager here see no content providers to display here. Content is not there. So

display here. Content is not there. So

we have to add it for here. If you go to the content manager again go back here.

So you can see here see this was la this was not there last I asked him to add it here. So here in your content manager

here. So here in your content manager this should be there. See here only I mean 10 days back only I asked him this guy to add this. He has added see here ML file app repository. So this was been

added by him. So whatever you if you don't find so this is the one this is the domain in which whatever you do in the build app that will come and sit in

here in this build work zone if this is not added whatever you do you cannot see in this build work zone environment are you getting so in your content manager

HTML 5 app should be there if it is not you have to add it manually okay if you don't have because this is a very secure environment usually you won't get permissions to your local admin or your

global admin will have it. So if you are the admin, you have to add it from here.

You have to simply click on the new give you destination service and it will be automatically added. Okay, this is the

automatically added. Okay, this is the very important check you have to do.

Okay, the moment when you do it here, you can create a site in here. This is a site. Site is nothing but like a folder

site. Site is nothing but like a folder in the build work zone. Like for example here, whatever the apps that we create, right, that will come and sit here. So

at the end once we are done so you should not feel bad you know hey this is not showing something like that you know this is how this will you have to check it first of all go back these are all

perfectly done so this is our general jour launchpad so here is where whatever the apps you do right whatever you do here that if you check it here for example I do something po something like

that if I search it it will automatically come here see this is the landing platform so here you will see it you will add it to the builds platform.

So this link whatever you're seeing this link is your main URL where in which all your apps get landed once you deploy in the build platform. Okay. So three

checks. First check in destinations whether you are getting this in the in the destination folder here. First

important check what you have to do the destination folder you should have this one which service I told you SAP build apps HTML 5 that is not there. I asked

you to add it here. Okay. And second one if you come to your build zone here in the build zone you should have in the content manager your repository should be there. Okay if in the content

be there. Okay if in the content explorer you can go that you can check that there this one should be there and second one if you go into this also here also you should have to add it. Okay

that is also is not added. So this is also should be there. See these two he will add anyways. Don't worry that will not block any of our demos or sessions here or your practice as well. But yes

this is how this one will be is one such thing you have to check it. So these two things you have to check it and parallelly the connections what you are saying that if you go to this on the site directory while you create that

site should be created and your app should be done. Someone is practicing please don't do that while I'm doing that. Okay.

that. Okay.

>> What is what's wrong in that one? I

cannot understand.

>> No if you practice practically you know like doing you know when I'm doing this you will not concentrate what I'm telling. Right.

telling. Right.

>> No I understand because I wanted to see that what is there right? So you are restricting everything actually what is that? No, not restricting, not

that? No, not restricting, not restricting. You have to understand that

restricting. You have to understand that Sur I'm not restricting. I'm telling

that you know any session is happening people will watch the session you know you can do it this is recording right you can do it later on so I don't have any issues if you're doing like that so I cannot understand because you went

through multiple places so I wanted to see that everything is there whether I'm able to understand or not right so this is something no no I can understand

but really not good >> this is how any training will go let me tell you that you know please you can tell me don't you Okay. But I'm okay with that one. KO.

Okay. But I'm okay with that one. KO.

Okay. I can stop it. But when you're doing it, I can try. If you say that, I don't want to do it. Okay. But you can tell me in a nice way. But you say that like it kind of commanding that.

>> No, I'm telling in nice way. I'm telling

nice only. I'm not commanding.

>> You're commanding it. Actually, don't do it. What is that?

it. What is that?

>> Okay. Fine. Fine. No worries. Yeah. I'm

not commanding to anyone. See here, this is up to you. You have to learn it. See

what I'm saying is if you do parallelly with me, you will lost what I'm telling.

So here I'm going here and there and you know entirely doing that right. So it

will it will not you know make you in a linking line there. That's what I'm saying that's it. It's up to us. No

fine. No

>> see we are all mature individuals only.

I don't have anything. So I don't want to command anyone. So I'm just giving you the right content at the right time here. That's it. If you miss something

here. That's it. If you miss something you will asking the questions to me. I'm

not commanding you. You have to understand that any session trainer is going on people will watch it. That's

what I'm saying. If you still want to practice you can practice. No, no issues because it will actually sometimes you know it will like what I want to say give you a kind of block here because some things will not open one is opening another type of things will not open for

you. So again you might think something

you. So again you might think something is not working.

>> I had a question.

>> Yeah please.

>> Uh uh uh regarding uh this one you said three different checks right the destination and even the configuration of site directory. So do we have any

official SAP documentation for it? Can

you list that as well?

>> Yes. I can list list it as well. Yeah,

one second. All right. So, I'll give you those links whoever asked this question to me and then you can go through it.

Okay.

>> I mean is there a central place you are putting those links?

>> Yes. Yes. Not links. I'll be directly putting documents there.

>> LMS. >> Yes. Yes. LMS folder as everyone has

>> Yes. Yes. LMS folder as everyone has showed to you. So, there is a folder called training trainer trainer documents. So, in that whatever I give

documents. So, in that whatever I give these guys will go and keep it there.

Yeah.

>> One very quick question just a basic understanding right. What is the

understanding right. What is the difference between build apps and build work zone like what is the is just that whatever we deploy will come to build work zone or what is the major difference? Yeah, that's what you know

difference? Yeah, that's what you know build apps basically you know like you generally develop a kind of all new applications like that you know like it's a digital workplace for us you know like whatever you want to create

organize you know do something on the front end so you will do everything on the build app kind of thing build work zone you will consume those apps in the unified workplace it's like it's a common platform for us where we

generally use it okay a kind of thing so in in this build apps whatever you do it's like all drag and drop kind of things will be there because lot of A lot of visual logic and back end integrations will happen in this but

build works on there's nothing. It's

like a launchpad for you for all your different different bridges to showcase you know to how they will look and feel you know in your environment at the output you know that will show you in the build zone. So that's the main difference between build work and build

apps. Okay.

apps. Okay.

>> Yeah. All right. Thank you. Next one. So

I'm going to build apps. Hope everyone

is clear with the pre-checks. I'm going

to the next one.

>> Yes sir. Please.

>> Yeah. So as I said now we are into the build apps. the launch of build apps.

build apps. the launch of build apps.

I'm closing the work zone right now.

Okay. So on the build apps as everyone know now let me let let us go one by one to the build apps clearly. Now this is complete a low code no code kind of application. So whenever someone is

application. So whenever someone is quoting low code no code is nothing but build apps only. That is the only environment in BTP you develop all these low code no code kind of development.

Okay. So what is this you know? This is

a kind of an uh environment which will enable basically developers or users or a kind of mid-level people who are few kind of coding few kind of coding kind

of things will be there like the rapidly build enterprise gained web and mobile apps will be there like without needing any deep coding knowledge because so many people you know I mean 70% people doesn't like coding you know like they

just want to use it as it is you know they want to know like go over certain kind of functionalities on that you know kind of things going on there So these kind of people and we call them you know citizen developers you know like these

kind of people will sit into these build apps you know because as I said there are three important if you see in our in our entitlements also I go back to the entity one more time should go to

completely show you that here in the entitlements so this one see this work zone is there bass is there apps is there again this is nothing but a kind of build apps only but along with that

we have build code is also that is also there that will be added to you by end of the So build code is the one environment where you will do complete end to end coding but there is also you have to learn few things will be there

where you will add this you know like apps to the zool as well like through coding okay but there also certain kind of coding will be generated back end and you know you can also use it I'll show you that anyways but yes so this is

these are the three important ones build apps build code build work zone for zulu specifically build apps build work zone build code so build apps I said this low

code no code. Build code is completely coding based. Okay. And build work zone

coding based. Okay. And build work zone where you generally land all your applications into it. Okay. So build

apps generally know like very very highly fit for professional developers.

Professional developers means who extend the apps with some kind of APIs, some kind of custom logic and I said citizen developers. That means the kind of

developers. That means the kind of business users who want to just directly use it but who doesn't want to write some code on it. Okay, these are called

citizen developers. So why this build

citizen developers. So why this build apps was came into the market also because just as everyone knows like in SAP web SAP like you know ad hoc kind of

reporting tool where we just drag and drop certain kind of things and we do we do something on the business objects right? people some many of you know that

right? people some many of you know that in the similar lines when you drag and drop UI when you when you want to pre-build certain logic flows know with easy backend integration so these kind

of things will be done through this build apps completely okay so build apps was earlier a name was there I don't know how many of you know it was called

SAP app giver a p g y v e r not jr gy vr it is app giver earlier it's completely a visual development tool on BP stack.

Okay. So, build apps generally I can say it will democratize your app development instead of you know waiting for long months to for an for an IT person to

deliver a new app. Instead business

teams like you or someone like you can create a kind of prototyping for a full solutions in just weeks. Okay. So not

only that at the same time what happens in this also IT teams can you know like they can easily govern they can easily secure and extend those apps to the

enterprise standards as well. So this is very important where in which you have to understand this one. So this is how build apps will help you. Okay. So in

build apps we have see you can see this you know I'll just explain you every single thing in this. So here you can see we have quick start templates are there. These are all templates okay

there. These are all templates okay which are already given by SAP like in ECC how you have all your preconfigured data for certain applications or in S4 HANA similarly for these also you have

all these preconfigured templates are there okay these templates will come from SAP build directly okay in SAP's main backend stream data templates it will come automatically here whatever

they put it in these are quick start templates but as you have to understand so in SAP build apps for drag and drop the main thing is UI designer. So where

it will be if you see here on the on the main mid page you will see create platform don't go to this one instead you can go for here you will see this one you will see zul skill zk skill keep

it tested no worries so you can do other things also in this first of all you have to know what you can do in this so here if you go to this create directly don't go for these ones up now if you go

to the create you will see these ones these are the important ones which you have to start like the first one is the application This is your application. You can create an application. Okay. S use development

an application. Okay. S use development tools to create and extend business applications and services. This is 100% your drag and drop tool where you will drag and drop certain buttons, certain

type of features, you know, to develop a small app kind of thing and you can deploy it on a mobile or web page kind of things. Okay. In a similar way, there

of things. Okay. In a similar way, there is an automated process like you can see a kind of HR process, a kind of something you can automate that. Then if

some of these are already done and making them you can then start using jaw skill also directly jaw skills if you will do you will get nothing. Okay, I'll

show you that also. Now why you get nothing in business suit? You can

customize your sites with the no code experience also. These are all no code

experience also. These are all no code only. Whatever I'm showing you here,

only. Whatever I'm showing you here, these 1 2 3 4 these are all no code only. Okay. So these are the important

only. Okay. So these are the important ones which you will we will see one by one in the in the coming days. And if

you go to the lobby if you expand this this is the hamburger menu is there. So

in the hamburger menu if you go you will see all these ones. First of all learn what are these. The first one is the connectors. So in connectors you have

connectors. So in connectors you have three things actions, events and automations. In actions these are all

automations. In actions these are all process actions. So these actions are

process actions. So these actions are whatever you build or else whatever you want to manage as part of your building blocks of logic you know like those are all called actions. Here you can name

see search by project name. In every

project you will add some actions. Okay.

So these are all like you know like a predefined operation that you will define in the system as an action. So

like these are all called logic canvases for you to connect your flows like a flowchart for your simple example. So

each action can have different different inputs okay like know like any input parameters will be there outputs will be there so they will determine your step like for example here flow for example

I'm giving an example to you. So you can say HR leave approval. So leave bucket you can keep leave approval one leave approval two. So number one number two

approval two. So number one number two number one number like parameters. So

those are all whatever you define in a process in a flowchart kind of thing those are all comes under actions. So

these actions are many number of actions will be there. Okay. Like you have navigation actions will be there. Let me

explain you. Let me take my notepad. If

you see here these are all the different actions here. So this first of all your

actions here. So this first of all your navigation actions in this actions pane will be there. So you want whenever you want to move one page to another page or

if you want to create a open page or a close page kind of thing. So those are all called navigation actions. Okay. So

this this is nothing but I told you right it's a kind of a flowch flowchart activity you will call into the system or into your main project that is called

your action. So for example I want a

your action. So for example I want a open page where after you log in that means after login you will get some success page right a kind of thing. So

that one is nothing but your second open page a kind of pages whenever you want to create you can do it. I'm giving an example like that you can do lot of things also the navigation action is one

such page. Okay like I'm giving example

such page. Okay like I'm giving example here also here it's like open pages close pages these are all called your navigation actions. Okay. And then you

navigation actions. Okay. And then you have the very important thing is data action. So in data actions you will do

action. So in data actions you will do all your crude operations okay create okay update delete you know these things will be there. So these are on the back end for logical data or I can say local

data as well whatever it may be. Okay

you can create a record you can get a location you can update a record when you want to delete a record. Okay for

example the main action you on the expense in Ariba kind of examples if you want to submit an expense. Okay. Then

data action will come. If you give a submit button or something, this data action, the one which you create in the data action will be called into the main system. Okay. So this is a data actions

system. Okay. So this is a data actions like you know submit. Okay. A kind of things that you do on top of this. Okay.

And then one of the other important actions that you can create is user interface actions. Okay. Whenever you

interface actions. Okay. Whenever you

want to s I mean display some components. Okay. Or you want to set

components. Okay. Or you want to set some variables. Okay. And for example,

some variables. Okay. And for example, once you logged into something or once something is opened if it's successful or not. Okay. For example, if your

or not. Okay. For example, if your expense is approved or if your leave is approved or if your purchase order is approved. So these kind of approval

approved. So these kind of approval small small dialogue boxes will be opened. Right? So those ones you will

opened. Right? So those ones you will take it as a user interface actions UIA.

Okay. So to these will help you to create such type of things like you know kind of alerts and pop-ups. Okay. And

then we have one more action called device action. So device action what is

device action. So device action what is that we'll get it is you know like whenever you want to access mobile features like cameras, GPS, bar scan corners you know like you know barcode

scanners you know like and then any uploading of files these type of things will be there on the devices whenever you are performing on on the device as an output. So those things you will do

an output. So those things you will do it on the device action. For example, if you have to capture a photo during your failed inspection. Okay. If for a simple

failed inspection. Okay. If for a simple example for any kind of let's say banking processes you know you have to take a photo of someone or else if you are doing some sort of KYC like know your customers kind of thing. So these

types of things also you need some device actions right. So all these things you will do it through this action. Okay like simply while is

action. Okay like simply while is happening to make some additions or I can say some inputs on the device. So

this one you will do it and the next one is with your flow control actions. So

these actions are very important again.

So when you want to write some condition, when you want to make some loop or when you want to write some formula, okay, very very simple example I want to add you know like if you add

our very common statement if else. If

this is a condition go with this, else this is a condition make this or if something is not matched make the data empty or something is done erase this one. A kind of things in which you will

one. A kind of things in which you will do a kind of conditional thing those ones will define your flow. when to go what to go because the flow will change from there only right if the condition is meeting one type of scenario

condition is not meeting another type of scenario so these ones will be gone through flow control actions okay I'm not writing because the name itself indicates what is the flow can be done so here next one is your integration

action so in the integration action as you the name indicates it will integrate what it will integrate whenever you want to integrate your rest or oata APIs or whenever you want to trigger the BDP

destinations or whenever you want to connect to SAP systems you know these things will be important for us in your flow. So where you want to trigger where

flow. So where you want to trigger where you want to call where you want to connect these kind of things will be defined and know helpful for this action. So basically you will integrate

action. So basically you will integrate with APIs and other services okay to fetch data. This is important right. So

fetch data. This is important right. So

these are the six kinds of actions which will help us know like to validate inputs to create records to show alerts to navigate pages you know kind of things will be there in this. Okay

everyone clear with these actions and then events.

>> Quick question here. So what do you mean by open page and close page and what is the difference between the two?

>> Same only open page close page.

Sometimes you have to close from existing page system won't go from there. Right? So in those cases you will

there. Right? So in those cases you will create pages for this or else once the process is done it will show an end page right so this process is completed or this is thank you for your using services this is a close page wherein

you know admit something on the end of the screen those are >> okay like that okay thank you >> yes yes yes and then events so if you go to the events yeah on actions also while you run the actions if you create I'll

just show you that also here so see here it will ask you to API source on which source you want to create these actions So you have six live APIs are there here and some API specifications are also

these are the standard ones only these are all already there in our system. So

if you want to say for example build from scratch that means something which is completely customized you can build from scratch you can manually define actions with custom specifications okay

or if you have anyone from API you can do it okay majorly we will do it through business accelator hub because you have lot of APIs that are already inbuilt and pre-delivered by business accelator hub

is there so from there you will create these actions and everything or else if you have any common things like our o data destinations or integration suit or you Unifi custom landscape. So these

these things are there. You can do it.

For example, if I want to give build from scratch, I have to simply give a project name here. I'm just showing you.

I'm not utilizing them now. But in the app when I'm doing I'll just show you that. So here for example the project

that. So here for example the project name test underscore. Okay. See here

it'll give you a lot of operations here.

So like crude operations basically it is giving you know whatever I told you because by like based on the actions that you define. So on the manual action it is going for this type of actions. So

if you can see either you can put the this action can be a get action a post action a put action delete action something like that okay so you can just give the name for example I'm giving forget so if there is an any relevant

endpoint for this you want to connect you can connect it for now I cannot I I am not going directly with the endpoint here but I can say here something like

okay it should start with my funnel and add this okay that end point is not active but anyways yeah so this have no data right now you can add a data in the later point I'll tell you while I'm yeah

so like this you have to add some parameters you know all these things I'll tell you later point of time so this is how you generally go for actions you know while you're building for this

okay if you go back again the same system see here this is already there okay these ones whenever you want to go you can rename you can manage members also whom whom you want to deliverly I

mean to see this particular thing there are many things for example if I give everyone to access. It will give you view access or a developer access admin access. It will ask you. So it's all up

access. It will ask you. So it's all up to you. If you're admin, you can have a

to you. If you're admin, you can have a full control on it. Or if you are just a developer with emails and organizations like this and based on that the particular team member can use your action as well.

Okay. Once an action is built, you can reuse them. Okay. It's not that every

reuse them. Okay. It's not that every time you have to rebuild. If the action is commonly built for a application, you can re reuse it. For example, if you build something in HR, if you want to use it in expense management something,

you cannot do it. But HR is for HRs only. But still, if that action has the

only. But still, if that action has the technicality inbuilt for it, if you can reuse, you can still reuse it. But what

generally follow as per the best practices for a group of application that actions can be reusable for next project or next application, you can create a new actions. Okay, n number of actions. There is no limit for the

actions. There is no limit for the actions. Again, we can create n number

actions. Again, we can create n number of actions on this. Okay, this is what about actions. And then going to events.

about actions. And then going to events.

So these are all the events. So events

as you already know these are nothing but the triggering ones for the buildups. So these define when a logic

buildups. So these define when a logic flow I mean sorry when this logic flow should start like events are like you know commonly attached to our UA

components for data sources. Uh so once this event occur the corresponding actions will be automatically executed one by one in a sequence. So to once your actions have been completely build

you can go with the event and create a event. Okay like this you can go for

event. Okay like this you can go for again it will ask you on which you want to create one. So you can specify as I show you any this one one of these ones you can put something or you can create

from the hub directly these events. So

like this there are many specific to our system will be there. If it is HR we can simply take HR events will be there or success factor success factors will be there. Okay. So many events will be

there. Okay. So many events will be there like components, page, app level, data events, you know the customized events know whatever you want to define as part of the trigger just to trigger

right. So whenever you want to trigger

right. So whenever you want to trigger by user action, you know, triggered by a page is loaded, triggered by some app is getting launched. So these events you

getting launched. So these events you have to declare them and you have to use it. So I'll tell you when it comes for

it. So I'll tell you when it comes for you, you have to do it. And then there is an automation SDK is there. Go to

this. So automation SDK the name itself indicate there are different SDKs are there if you can observe this here we have outlook is there excel okay PDF

core SAP UI is a very one very important one so first of all what is this SDK everyone know that is a software development kit SDK that's okay but what

is this in SAP build apps is doing so this SDK will hold a set of predefined actions that will allow the app that we

develop appear right that will allow that basically to trigger your processes. It will trigger your

processes. It will trigger your workflows. Whatever the automations you

workflows. Whatever the automations you do, these are all will be triggered as a predefined actions in that flow. Okay.

In this through this automation SDK G.

Okay. So instead of just calling your APIs manually, SAP provided this native SDK integration so that what happens?

You can easily connect your build apps to your Sba. Okay. When is a build process automation. So why this is

process automation. So why this is important? Why SAP kept the automation

important? Why SAP kept the automation SDK here is because many enterprises generally if like instead of naming as enterprise I can say enterprise apps

these need certain backend automation like for example if I'm submitting a leave request it should trigger an approval workflow right so it when it has to trigger a workflow it should have

some automation so that should be automatically been configured and should be called the relevant APIs also for me so that mechanism was there in this

automation SDKs. Okay. So, normally this

automation SDKs. Okay. So, normally this requires a a kind of a set of API calls and complex logic part will be there.

Okay. But because this automation SDK is there, build app developers, they can just simply drag and drop the actions like your start the process instance, you know, wherever the flows has to break, wherever the conditions has to

apply, nothing, no deep coding will be there. Just drag and drop. Add some

there. Just drag and drop. Add some

points there. Add some little bit of coding there. very little bit and then

coding there. very little bit and then you will use asset. So that's what that means you can understand that in the layman terms that is all preconfigured coding parts where system has given you

to use it in your drag and drop UI features. Okay. So what it will help

features. Okay. So what it will help users means it will start your process instance. It will get your process

instance. It will get your process definitions. It will help you in your

definitions. It will help you in your user task. It will complete your user

user task. It will complete your user task when you are submitting or doing something in your end of the flow. All

these things will be done through this SDKs. Okay. So a key strength I can say

SDKs. Okay. So a key strength I can say on the SAP build apps is its ability to connect with your build process automation using this automation SDKs

only. Okay. So with this SDK what

only. Okay. So with this SDK what happens is all the citizen developers they don't need to worry about APIs or custom code. They don't they should not

custom code. They don't they should not worry about that. this they can simply drag and drop the predefined actions and they can easily complete their flows and then they can they can easily export

their apps and they can start working on it. Okay, for example, if you imagine an

it. Okay, for example, if you imagine an employee submitting a leave request inside a build app using this automation SDK that request will automatically start a workflow in the build process

automation. So that will route it to a

automation. So that will route it to a manager updates the back end HR systems once approved that that strictly it will align the integrations also. So this

this makes what finally the build apps will not just is a front-end tool but it's like a gateway to your complete enterprise automation as well. So this

is bridging your I can say businessf facing apps with all your backend workflows. So this is what delivering a

workflows. So this is what delivering a kind of complete process experience to the end users and the business aspect right so any questions on this clear

everyone these three characters we will see we'll use them very frequently in our flows now everyone clear and coming to store so store level you'll be seeing this is a kind of I can say marketplace

of thing where you will have all these SDKs you know different different types of things will be there whatever is useful for your build apps you go for them. But in this few will be

paid. See whatever are paid you will see

paid. See whatever are paid you will see this one called paid because the publishers are from different service entities will be there who are business partners with SAP will be there. So if

they create something see for example unlock unlock transaction if you want to use it instead you create if you want to use it you have to pay for it. Okay. So

few things are there wherever paid is not there you can see all them add and open. Open means already added. Add

open. Open means already added. Add

means you will add them directly. Here

you can see here few things are open which is are already added. Few are not added you can add them. So if you are paid as I said you have to check properly while you're using them. Okay

you'll have a number of I can say hundreds hundreds hundreds of store SDKs are there. You can just simply come and

are there. You can just simply come and check whatever you want. Okay. So this

is a very big console here. Okay. Let me

go back. See here business partner creation approval process. You don't

need to create even the process is also inbuilt in it. What I'm saying is till now what I said you know you have to create something from the scratch you can create it but still something similar like is already there you can

create from template also you just want to tweak wherever your business adjustments are needed so like you see here if you go to one such process here you'll have the process diagram here and

also you'll have the artifacts what are the artifacts in it you can see here these are all artifacts means different different actions and triggers so you will see these ones one by one know every single detail will be an artifact

for you here. So like this this this process which was given by SAP is already been built. So you can create this process for whatever you want and there are some dependencies also that you have to check for this for create

action restart process they enable certain data management based AP calls will be there. This you have to save it.

Okay. And one of the other important thing is this version. So whenever any change is there they will capture in different versions. So in one version if

different versions. So in one version if a change is not there in another version that will be there. So you have to properly deploy your versions also. You

will see that now I'll show you simple thing now. So these are the different

thing now. So these are the different versions which will come into picture according to the version only you can deploy the features as well. Okay. So

for example I'll come to that now. Yeah.

So and coming to the monitoring these are all different different instances whatever you want to monitor can see this process workflows and monitoring.

So you can see here what does this monitoring in build apps will do specifically is for you. This will help you to refer the app behavior how it

actually happening and it will track the app behavior. I think that's the right

app behavior. I think that's the right term because how this app is behaving what it is performing how it is performing and what is the usage of it that usage means at the system level. So

these kind of things whenever you want to monitor you can go for this monitoring. So there are a lot of things

monitoring. So there are a lot of things in the monitoring because this particularly covers your runtime monitoring, your analytical monitoring and your error handling and debugging as well. During the development some errors

well. During the development some errors might happen. So you can come to the

might happen. So you can come to the monitoring can see the monitoring pane there any area any error that is happening in your screen or kind of things you can observe in this monitoring screen. Okay. So basically it

monitoring screen. Okay. So basically it will help you to know like if logic something you're writing or if you're calling an API is getting failed. So

build app will show you some red red indicators will be there. So those you can see on the screen itself. If you

want detail you can come to the monitoring pane like this. You will see here in the monitoring pane all these ones. See automation jobs how many are

ones. See automation jobs how many are running. You can see here see how many

running. You can see here see how many failed how many errors what is the health of know you can see all these things here itself only. Okay. It will

show you a kind of thing and you can manage all the business rules also. Is

there any custom business rules or predel preconfigured business rules are there you know when you're deploying or after deploying because after deploying you will integrate with monitoring with different backend systems will be there

you're as I said the automation SDK monitoring is also important so these are all comes into picture when you start working on it so these are all you can just check and monitoring this one and the next important thing is your

control tower so control tower you can see here this is one such important activity in the build app So whatever

the tenants or your backends or your agents or your other APIs know uh whatever you call those are all can be comes under this control. Okay. Control

tower the name itself indicates it's a part of your complete process automation. So I can say this is your

automation. So I can say this is your central monitoring and management hub.

Okay. Like your I can say a global admin for your build apps kind of thing. Okay.

What it will do? It will track all your running processes and automations, all the defined user task like your approvals, your reassignments, okay, your know like renamings you know kind

of things you know you can do everything from this control to not only that this control tower we will also monitor your errors your performances even your SLA compliance you know a lot of things it

will do as part of this year okay because you might be surprising hey by how it generally relates my build apps okay build apps It doesn't have any

control of itself because when a build app use the automation SDK that moment control will automatically comes into picture because the moment you are

starting the workflow kind of approval request ticket or something. So the

execution and monitoring of those workflows will be done in this control tower. Okay. Which means in simple terms

tower. Okay. Which means in simple terms your front end UI is your build app.

Okay. where user submit some request your back end is your bill pros automation but your monitoring and governance whatever I told in the initial part of session now that is your

control tower okay so this will completely process your instance tracking it will take care of your task management it will h it will help you if a workflow triggered from build app

fails it will the admins have to see in the control tower only where it fails and what how it what is what happened for failing for Okay. Or your business KPIs getting some

Okay. Or your business KPIs getting some for example if we can say your business KPIs will be there they are getting timed out no the moment when they're executing they're getting timed out you set some time you have to rework the

time to some other you extend the time.

So those kind of tweaking of times approval times request completion times you know those all can be set here itself. Okay, even your agent

itself. Okay, even your agent configuration. Okay, all these things,

configuration. Okay, all these things, agents, agent groups, agent attributes, everything you have to do it here only.

So if you configure it here, then only system will understand for the automation SDKs. Okay, because the

automation SDKs. Okay, because the control tower as I said this will be a central cockpit for you to show to run

your process. Okay. And whatever if any

your process. Okay. And whatever if any employee or if any process associate face issues on the build app. So while

while the request is you know request means in the app level the request is processing those are also can be treated or you know can be resolved from this control term only. So that is the

importance of your controller. Okay. So

these are your main menu items which you have to understand. So everyone clear any questions before I go to the flow?

Everyone clear? Everything the

technology is clear.

>> One quick question.

>> Yeah please. Uh so when you go to the store so which all jewel related templates do we have available? Can you

quickly glance? No no no no there is no separately jewel related thing gra these are all you can use it in the zool whatever this is all a process you have to set it it's not about zulu we'll have

only dedicated ones wherever your process there you can just search and you can use that these are these all can be used in zoo >> every single thing all the process related flow related everything these

actions is given like for that the major thing is you have to first create a app for that then that can be incorporated into the zone so that is why why I'm showing you it's a it's The good thing you guys enrolled for zu training but

you're getting complete train on build apps also. Now that is the secret

apps also. Now that is the secret because directly zu if I show you will be seeing some kind of you know like if you are a native of telu you will be seeing mal you don't understand anything

a kind of other kind of language movie only because you have to understand all these basics for specifically zul you have to know build apps completely that is why I'm showing you everything in the

build apps. So once you understand build

build apps. So once you understand build app zool is nothing it's very simple to create because zool also see that's what I told you the moment when you go and create zool skill here it will ask you all the buildup things only see for

example if I'm doing this so this is also I'm just copy pasting the same thing see scenario has to call so the moment when you do you have to call action whatever I just told you right

you have to call action you have to run an automation you have to launch a skill which was predelate you have to define a process if these are not There you cannot launch any jewel jewel skill

there. You cannot create a skill. So it

there. You cannot create a skill. So it

will be like okay empty space there. See

for example if I ask go for action see there are no actions because there were nothing in the build someone has developed on it. Okay these ones we have to develop then only you have to know

like get things into the zool studio then you can start using that. This is

why I told first of all you have to get complete knowledge on the build apps then you create your skills then you can deploy them in your studio and then it will be possible scenarios for you to

see on that okay so the basic 80% of part you will do in the build apps only that is why you are learning build apps completely in this so then once you create the build apps level all the apps

and every actions and events everything it's easy for you to incorporate with the jewel skill and it can simply put a process there it will be automatically done that's in the build apps. Okay. But

in build code again that's a process different. You will learn anyways in the

different. You will learn anyways in the coming days. But build apps this is what

coming days. But build apps this is what the environment is supported. Clear.

>> So you are saying we will create our custom actions and events whatever we need and then we will leverage no let me complete. So we will leverage the this

complete. So we will leverage the this one LLM capabilities and then combine all of them together.

>> So something of that sort. Right.

>> Right. Right. In the process you should have all these things. Right. So there

you will leverage all this thing and then your jewel skill will be created.

So that jewel skill you will use it further wherever you want it and not only that see every time so please come out of that mindset you know like every time it's not a chatbot kind of thing

you're doing jewel skills means it will help you like you know like for example in the build code you will create a app there jewel will be help jewel will be

helped for you to create a app for certain processes. So how jewel will

certain processes. So how jewel will help you? It won't come like a as I

help you? It won't come like a as I showed you know as I showed in the earlier it won't come like a chart either but it will help you. Jewels

skills will help you. How jewels will help you means it'll have some automated processes. The moment when you go to the

processes. The moment when you go to the build code it will help you to trigger certain processes and add that container contents into it and you can simply build some more applications using that kind of scenarios. It's not always a

diamond icon will come and from the diamond icon a chart. Chartbot is your whatever I'm saying this kind of app based process only. Other than that there are some other specific purposes

also when you're going for build code kind of activity. So you will see that a complete back and front end environment how it connected how zulu will help there. So those scenarios we will see in

there. So those scenarios we will see in the module four. Okay. But here in build apps first of all you have to understand these apps then only you can create some jewel skills that can helpful for your other process. So to create that you

other process. So to create that you should have all the internal binding processes like these actions or events and whatever you want. So those are the basic data we are building right now.

Clear?

>> Yeah. Thank you. Everyone clear? Okay.

Now, let me go into this.

>> So, we build on the build apps, >> right? Then we use whatever, you know,

>> right? Then we use whatever, you know, we have built on the built uh you know, I mean build apps in the jaw skills and then we use those you know, Jav skills,

you know, container into our, you know, business, you know, processes and things like that, you know, as actions or or you know, whatever. And then finally we

monitor you know manage all of that you know we have built and uh deployed through the control tower is that correct >> right right so this deployment also will

go to the public if you see here see something supplier is there I'm just randomly clicking that there see here this is a complete someone has built it okay so in this one if you go to the

version this is already deployed so the moment you deploy it it will ask you to wait see are deploying to public. So in

the public whatever environments are there which are connected in the public environment are there. All that

environments can access this app. That

means this app information. So in the studio or in your other other environments wherever you just name all those environments you are ready to use it. You are going to directly deploy in

it. You are going to directly deploy in the public. Okay. So here at this level

the public. Okay. So here at this level only it will be a difference for you.

Sometimes you will go with your restrict environments where you deploy only to few environments where you can see that app or something or else if you're directly moving to public it will be accessed by all users all environments

in this step. Clear?

>> So this app you can we see in the control you know tower.

>> No you cannot see app outputs in control. You can just govern it to

control. You can just govern it to control tower. That's it. You cannot see

control tower. That's it. You cannot see any outputs there.

>> Can we go to the control tower and have a look you know what are the options there. Sorry I missed the other section

there. Sorry I missed the other section because I think that's quite important you I heard a lot about it. Governance

environments. Okay. So, is it a kind of an admin section?

>> That's what I told, right? I told have you missed my session controller or >> Yes. Yes. Yes. Yes. Yes. I missed that.

>> Yes. Yes. Yes. Yes. Yes. I missed that.

Okay. Was so Yeah.

>> Please, please refer that recording. I

clicked.

>> Thank you. Thank you. No worries.

>> Okay. Okay. Perfect. Thanks.

>> Okay guys, fine. So, everyone is clear with this options. So, this is how you deployed once you create this one. So,

that's where your deployment will go.

Now you have some idea some mockup idea how this will go where it will sit how this will happen. Everyone clear. Now

let me go into this. So as I said first of all while creating you have to create an application right this is an application. Say next. So application

application. Say next. So application

also comes under different categories guys like it will be a fullstack application or it might be your front end your back end or your mobile application completely end to end mobile applications will be there. So all these

can be done. Okay. I will not be covering everything in this because our content will not cover that. But yes,

the front end one is one such thing which I can show you. Basically here if you go to the front end one. So here

you'll have this one. The front end also three important things will be there.

There is one more thing which was recently been not added by the deleted by SAP. It was web and mobile both are

by SAP. It was web and mobile both are there. Now they have segregated to

there. Now they have segregated to mobile completely. Okay. Now this is a

mobile completely. Okay. Now this is a web application. You can directly do it.

web application. You can directly do it.

Or if you have a fury front end where you want to make it only in Fury, you can do it. Fury cards are the new one which you have like a card components for business application purpose they created but it have some access and

restrictions are there. So you have to check with your admin for that okay not here in your original ads. The main

we'll go with the web application. This

is a complete visual studio for you. So

if you go to the web application give the project name like I'll give here ab_lication list. So you guys also while you're

list. So you guys also while you're practicing you can just go with your first two surname first name last name WA web application test. So follow this naming convention so easy for you to

retrieve your applications whenever you want. Okay. And then just review this.

want. Okay. And then just review this.

You can see application front end web application project everything. Okay.

Then create will take little time while first time it when it is you know getting boarded because build apps project whatever I did is created now the default homepage will be displayed.

So once it is created you can can access all these things. Oh my god what's happening here? Reload this. You can

happening here? Reload this. You can

just refresh and reload it. System will

it's a home page. It's kind of URL only.

So no worries. So there is no harm that you if you go back something will collapse or something will harm that no nothing like that. Let it be loaded completely still loading. So once your

project is created you can access that any number of times from the build lobby. That means our build lobby will

lobby. That means our build lobby will be there right from there you can access it directly. See here this is your

it directly. See here this is your interface. I told you build I told you

interface. I told you build I told you first one statement. What is that? Drag

and drop right? This is your user interface guys. Everything is drag and

interface guys. Everything is drag and drop like whatever the fields you want, input fields, the list selections, the essential things. Okay, this is your

essential things. Okay, this is your homepage. If you want to have different

homepage. If you want to have different different pages, you can show all pages.

If you want to create a new page also parallel, you can create new page on this. For example, I want page two. I

this. For example, I want page two. I

want to create this one. I can create a page two also in this. Okay. So like

this, you can create pages and you can do this also. Now let me show you a simple application also here. So here if you can see these are all your this this is the page section. This is main homepage. You can just create a number

homepage. You can just create a number of pages. I told you right. This is one

of pages. I told you right. This is one such thing. And the left side I don't

such thing. And the left side I don't need to explain you know all these different different menu options are there. Whatever you want to drag and

there. Whatever you want to drag and drop. This is your body design body

drop. This is your body design body where you will drag and drop those things. Okay. This is in some other

things. Okay. This is in some other language. I don't know. So I don't know

language. I don't know. So I don't know this is this is German might be by default. I added that.

default. I added that.

>> That's a placeholder.

>> It's a placeholder only. Okay.

>> Yeah. It's not German language.

>> No this is Laurum dollar something is there right? That's what I'm talking

there right? That's what I'm talking >> that is Latin but that's a place >> I don't know this placeholder talking about this language you're talking so this is >> language only that is Latin >> that's what I'm saying I don't know

that's a Latin okay these ones can just remove okay this is a text field they have something was by defaulted for the headline whatever for you for your app to be name that was here and then you

can see here majorly these things is important the one which you're developing the application is it for mobile it's for tablet or it's a full screen for your desktop or laptop or

it's a custom there is a categorization here. Okay. So based on that you can

here. Okay. So based on that you can select it here and here also you'll have some resolution factor will be there at what level you want it. So based on that 100% is what we generally default. So

based on your purposes if you want to move it you can move it. Okay. And these

are all your text. You can see these are the text ones their styles their layouts everything will be there. It's quite

common. Everyone knows that. Okay. So

whatever the styles you want whatever the layouts you want. Okay, you can just see this here. Okay, so variables, I'll tell you what are all these things now one by one. This is your user interface basically. Okay, if you go to the

basically. Okay, if you go to the variable section, so in your variables, you have different different app variables, page variables, data variables. Okay, these will be the

variables. Okay, these will be the whatever you want to create, whatever the parameters you want to create, you want to use it, you can add them one by one here and you know those you can utilize in the interfaces also. Okay,

I'm just showing you now on the integration level as I told you these are all the integration based app you know actions and all these things if we can add integration it will show you the destinations at level what integrations

we can do automatically we added something in the BTP right so from that we can get it so for our S4 and our back end system is already integrated so you can get that so in case if it is Ariba

or field class or success factors you'll get those ones automatically okay if you integrate that so those ones you can use it okay Going back from the library if you want to get it also you can get it

from all projects specifically now we are not allowed on this even though I add this with the industries or all these things okay because we are not allowed we are just for our back end is not for only so we're doing that so

removing all these things and then navigation so your navigation headers will be there if you want to navigate in the built-in navigation will be there where you want get your header bars your menus your tab pages one by one if you

want to add first page one first page two next page three kind of navigation if you want to build in your mobile app or your custom apps you can add them as well. So based on the ticket design for

well. So based on the ticket design for example bank page is there. So initial

bank page you will have some login or something. Next bank page you will have

something. Next bank page you will have some transactions kind of whatever the design you decide with your users and everything you can based on your design you can go for this navigations and okay like this the user interface will be

completely inbuilt for you. You have to just create and you have to use it.

Okay. And whatever you do here you can preview it here. First of all, preview will show you how it looks in the output. So output can be seen here

output. So output can be seen here itself only. And then you can publish it

itself only. And then you can publish it to the cloud. Okay. Wherever you want to publish it. Okay. Whenever you save

publish it. Okay. Whenever you save these applications, these will go sit in your direct folders. Okay. And these are your versions. Wherever you have been

your versions. Wherever you have been saved one by one, those versions also you can see it. So this is your complete uh build apps folder. Okay. Everyone

clear? Let me show you one thing from mobile. Trying to do from mobile. Can

mobile. Trying to do from mobile. Can

you >> can you build like you know one example application here maybe integrating >> I'm doing >> oh you'll be doing okay okay >> yeah that's what I'm saying >> okay okay

>> I'll show you one so this is a headline for example add something so I added this one now this is a headline where you can add whatever the text you want you can copy it you can delete it whatever you want in this okay for

example let's say you're doing some kind of barcode scanner or something okay you can add it whenever you want it for that you can do that so you can add a text also here. Okay, this is the one thing.

also here. Okay, this is the one thing.

Now we can add another text also like you can add something like you know uh add this one and it's stored because in bank you won't do any barcode thing

right so in food items we'll do something so I'm just trying to do this scan the barcode of your can and write some food product okay from your

smartphone okay so these ones also I'm not doing any changes here. So max

length, display line, styles, you can just check it out which one you want.

You can just put that one. Layout is

also up to you how you want to put it.

Okay. If you want text alignment or width adjust, height adjust. No, all

these things you can do. These are all features you can do R&D on this. Nothing

total is own just a properties only. So

I'm just showing you how you can build the app on this. Okay. So for this is a barcode scanner kind of application we are doing right now. So if you can see here, okay, we don't have the scanner here. You can see button here. I'll just

here. You can see button here. I'll just

put the button here. So this is a scan.

I'll take this button. Write this button because we have to scan something on the button, right? Just write simply here.

button, right? Just write simply here.

Scan. Okay. This is doing something.

Just so you can keep like this. This is

absolute button. If you want on the top, you can change this and just put it in the relative right now. Yeah. Like this.

Okay. This is a scan option if you want to see it on the top. Simple. That's it.

I have this very simple thing here. You

simply save this guy. Okay. And then you preview this. So something this will

preview this. So something this will look like this in the preview page. Very

very very basic level thing I have just shown to you. So like this can create any app.

you. So like this can create any app.

Okay. This is now saved and available for you to preview whatever you want on the different different things can do it. So let me show you something also on

it. So let me show you something also on this. This is close. So if you have a

this. This is close. So if you have a specific image of any span, any barcode image that you want to do it, you can do that as well. For example, let me check a barcode here. I'm just checking from

Google. Any barcode images you can

Google. Any barcode images you can generate, you know, I'll show you how you can generate that also. But for now, I'm just taking some images just for knowledge, QR scanners or something. So

you can add your respective barcodes also onto it.

You can add this one. Maybe you in properties you need to >> I'm doing one second.

>> Yeah, >> it's a static image only. So these

dynamic images for generations there will be a process for this. If you see here there is a data and variables formulas are also there for certain type of imaging things. If you want do we'll

do those scenarios also understand that for now let me take static image. It's

not covering drag in this one. This one

can be like this can use this image.

That's it. Now I'm just save this and then you can preview it. So this is how basically based on your sections it will show you how this Oh my god it's too bad showing too bad. So on the mobile level

it will show you the preview like this.

Yeah but yeah let me show you this. Uh

if you want to do it on tablet or on full screen it will be too bad I think.

So I have to just check out this one.

This is what I'm saying. This image

properties you have to know like check it out the style and everything. So that

should you know fit into your environments properly. That's where you

environments properly. That's where you have to keep it the scaling and everything. So the adjacent height grows

everything. So the adjacent height grows to full width it can get. Now this we have to put this one. Okay.

Yeah. This pixels I can make it four two and spacing also we can just check this out like this. Okay. And all these custom groups are there. It should be

default gap will be there. Okay. And

these ones you can publish this.

Anyways, this will show you here like this. But in the mobile environment when

this. But in the mobile environment when you see it will be okay for you to see and you know make this happen. If you

see this, you can publish this one. You

can build and deploy or you can create a real version. Create real version means

real version. Create real version means as it is it will go. If you want to still make changes on this this package as a project and a web application, you can download them and deploy. Okay. Two

things will be there. You can save the current state and you can number this version because if you have still changes will be there that will be go into that versions. For example, I create a current version release 1.0

only. I'm releasing as it is now. Okay.

only. I'm releasing as it is now. Okay.

Fine. So the same version will go to the cloud environment directly. Okay. So

this is now released app. Okay. So yeah

there are lot of things that is a very basic level app I have shown to you. So

lot of input fields we can give data we will bring it from the S4. I'll just

show you some of the scenarios also in the next classes. You'll understand

them. But this is how a very basic app you will create them. Clear? You can try creating your own apps and then you can know explore that. So in the next class I will show you how you bring data from you know standard preconfigured

containers or preconfigured things from the SAP S4 HANA and then how you map some scenarios. We can create some

some scenarios. We can create some tables. You can create some based on the

tables. You can create some based on the drop-down fields you know edit some data. So field imports know all these

data. So field imports know all these things we can see in the next scenario a kind of a different dashboard kind of thing. Okay clear everyone.

thing. Okay clear everyone.

>> Yeah one question. So I know these are all like foundational right I mean basic but is SAP at a state where like just by query it would create everything like I

mean we have seen like apps outside like replet and all just by prompting it would create the whole website or even an application actually. I mean

at this point yeah >> understand in a in a jewel you're asking if you say I want this website this this this so so so you create it will creating something like that you're asking

>> right exactly >> no no no not in such state I told you right it's not in that that state >> okay makes sense >> it won't create >> so you'll show the ne in the next

classes right you'll show the s4 data >> oh yeah now we got all the things about build apps right now we Next class we will see these ones what are the different different items are there I show you how they fetch the data how you

can fetch data from S4 HANA so what are the other items you build so those applications you will see in the next session >> okay yeah please spend a little bit more time on that I think that will be one of

the key important parts of this the training right yes >> automatically you have to build learn right so I have to show you how you bring variables how you do integration these will be there yes

>> okay great and a Sorry demit interrupt.

So there can you is it possible to show like one full stack application also because I tried like you know just like playing around with like a fullstack application but >> no no in in build code I'm showing you

that one only in our syllabus also that is that module 4 a fullstack application is there that's what I'm going to show you there also in build.

>> Okay you will show the full stack application there.

>> Yes yes yes we'll get it.

>> Okay thank you. Is there any application is there where we can see okay this is the front end how it will be there it it'll be clear the imagination because I'm very new and I'm not able to saying

okay >> you will see that you have lot of inbuilt applications are there I told you right in the SAP build itself only if you go there you have templates are there from there you can see all these things yeah I'm I'm about to kind of

close the session of time here because yeah yeah these are all the templates whatever I see so from these we can create them and uh you can get web master there are a lot of templates out there you can just simply go for example

invoice process is there you can just go into that and create from template and deploy them and you can use it directly that's it >> just a little feedback the full stack application right like

know Joel skill is not working fully so I don't know maybe there is something that you might have to talk to that >> yes yes I I already had a conversation also the build code itself is not there

first of all I asked the free tier to involve in it so then only even this HTML also was not there. I talked to Admin last night only. He generally

works in the night time of India. So I

will speak with him after 12 1:00 and then know because I need a screen share with him. So I have to show him what is

with him. So I have to show him what is what then build is there then yeah we can be done. See I can directly go to billboard and so you won't get anything on that you know it will be a zero knowledge for you. If you understand

build apps you do some apps on this you'll get some confidence in build you will understand that you're covering like know it's really good. So yes, so the background is really good and like know then you're going to the actual

articles of it. That's that's really good. Yeah. So yeah, that is okay.

good. Yeah. So yeah, that is okay.

>> Okay. Yeah. Thank you. So that's it. So

someone asked me right. So this is the templates guys. So you can just this is

templates guys. So you can just this is all already done. You don't need to do anything. You have to just tweak it

anything. You have to just tweak it whatever you want. You can just you know release this and deploy this in applications. And you can see that

applications. And you can see that outputs as it this is how you generally make work with updates. You can just deploy this to the public. So this is deployed in environments. You can see this is a public environment. You can

see that as well. So you can see these are all the environments. These are all the projects which are already successfully deployed in this environment. So these are all your

environment. So these are all your triggers. You know all these things will

triggers. You know all these things will be there. So your output environment you

be there. So your output environment you will see in the build zone for this ones what I showed you but that is not integrated. So that's what I told I will

integrated. So that's what I told I will just check with the admin. I'll show it because these ones are not getting you know like incorporated into the build zone directly. So whatever you do here I

zone directly. So whatever you do here I mean in the UI space those only you can do it. So for that also you have to

do it. So for that also you have to incorporate some templates. So that has to be there. So if you see here s you are the one who asked me this one who who asked this question to me.

>> Uh me Abhishit.

>> Yeah abish. Okay.

And this is how this is not coming even in the BTP stack also. So whatever I just deployed that right. Abijit. So

whatever I deployed that right you generally see in this one whatever has been deployed in HTML 5 applications they will come and sit whatever there are difficulties in loading global whatever everything you want to see the

preview output something you have to come to BTP cockpit in HTML 5 applications you will see that they will be listed here automatically because we are on on the BTP platform only so those

are all come to comes under HTML 5 only so you have to come and see here if work zone is also because there are a number of ways to preview it so one is this one. Yeah, one way is this one. Second

one. Yeah, one way is this one. Second

way is build box. Refresh this page.

Something problem is there in this now.

Yeah, this is not I'm showing but this is not getting that one. Yeah, I will talk to the admin. It has to approve here but it's not showing me. I'll talk

to him and I'll get this done. Okay.

>> All right. Let's test your knowledge.

Here's a question for you. Which of

these is a primary benefit of SAP Juul for end users? Option A, increase system complexity. Option B, reduced need for

complexity. Option B, reduced need for training. Option C, more manual data

training. Option C, more manual data entry. Option D, longer processing

entry. Option D, longer processing times. Take a moment to think and when

times. Take a moment to think and when you're ready, choose the correct option.

Remember, each choice holds a key to unlocking the answer. Good luck. Type

the correct answer in the comment section. Hey there. Want to get really

section. Hey there. Want to get really good at using AI in SAP? Our SAP Juul course is here to help. You can take it at your own pace on our platform. In

this course, you'll learn all about SAP Jewel. It's like an AI helper for work.

Jewel. It's like an AI helper for work.

From asking smart questions to getting instant insights for faster decisions.

Our course covers everything you need to know from the basics to cool advanced features. It's made by experts who

features. It's made by experts who really know their stuff. Your teachers

are pros who've worked with SAP tools for years. They're here to guide you and

for years. They're here to guide you and answer all the questions you have. And

don't just take our word for it. Our

students love the course, too. People

just like you have found this training super useful. Best part, it won't cost

super useful. Best part, it won't cost too much. This awesome chance to learn

too much. This awesome chance to learn is really affordable. Ready to become a SAP Jewel Pro? Sign up on our page now.

And for more info, check out Zarantex website.