Streamline Sales Order Approval Process with airSlate SignNow

How to create outlook signature

foreign [Music] [Music] it's an immense pleasure to welcome you all for the today's webinar session so I am Mahesh I'm the host for the today's webinar by increase all I will be assisting you in case you find any difficulties during this session also you can keep posting your queries in the chat which will be discussed in the last 15 minutes of our q a session as a speaker today I have Mr Suresh Kola the uh sales and distribution consultant so Suresh all handed the mic to you you can take the session forward yeah okay yeah foreign let me start the presentation now yeah uh I hope you know everybody is able to see my presentation you can start okay okay so as part of this session was flexible okay so what is the you know how it works in the uh with respect to the SJ module for various business process so you would be able to know about these things okay so let us go through the uh No Agenda of it okay so so as part of this session you will be able to understand what is you know flexible workflow the benefits of the flexible workflow how to start with a flexible workflow and one business process example and so there's an app called maintenance teams and responsibilities foreign applications and my inbox fairy application okay later we have a q a session okay so the flexible workflow allows you to Define approval process for the documents ing to your requirements okay so it has been introduced in the S4 owner system okay so which is being used so which is used in the existing business workflow functionality with some announcements of it okay so by using the flexible workflow so you can simplify your configuration okay so the sales document workflow functionality is available okay from the 1809 so this is for the sales uh document popular functionality so uh the flexible workflow is already available in the earlier versions also but it is you know available for the sales document workflow only from the version 1809 okay so it can be enabled with the three of your applications which you can say in the below screenshot okay so one is main is teams and responsibilities the second one is mainly sales document workflows and my inbox okay so along with that we also have to implement sap customization okay so we'll go to those uh by one so when it comes to the uh other scenarios like General uh General General entries purchase requisitions purchase orders request for quotation service and receipt scheduling agreement preliminary building document legal transaction condition contract settlement documents marketing campaign marketing plan sales credit memory request sales orders sales quotation Etc okay so these are you know scenarios on which you can you know make use of the flexible workflow okay so now so what is the difference okay so as you know the there's a classical workflow and now when it comes to this for Hana we have flexible workflow right so what is the difference between these two okay so classical workflow and the flexible workflow you can have a different functional this year on the screen like when it comes to the transaction by interview so the classifical the classical workflow can be you know built in the transaction codes SW DD okay so in flexible workflow it will be under swd underscore scenario okay the purpose of it is you know in the class a classical workflow these are the classical uh workflows build using the workflow Builder and developed by sap okay so there's usually as a simply workflows okay but when it comes to the flexible workload it is just a building block where the end user you know where they know a client users can configure it and maintain the flexible you know workflow as per their business requirement okay the resulting Buffalo can be configured by the process expert using the main Network app okay so these apps will be discussed in the you know later okay yeah and the other one is select efforts okay when it comes to the efforts point of view so when it comes to the classical uh workflow so everything starting from uh from the start plan to end points you have to develop everything whatever that is required by the customer so there has to be a development have to be provided to the customer but when it comes to the flexible workflow so their development effort is less as compared to the classical workflow because it is a ready-made okay it is just a build block right so there you can just activate it and you can use it as per the requirement okay okay so custom development so when it comes to the development maybe the standardized functionality may not be suitable for all the businesses however there is a functionality where you can add up as per your business requirement okay so which is as part of the custom development so that is available in both Custom Classic classical workflow as well as in the flexible workflow and conditional recurring okay maybe there would be many scenarios where there would be you know different conditions to trigger the workflows scenarios like example maybe the order value you have to uh set a order value as a condition so for which you have to write the code in the classical workflow so whereas in a flexible workflow there's no coding required as it is a precondition to manage triggering as a steps okay so that you can see in the down the line so where you can have the demonstration of the ferry application Okay so then email templates so no much support in the classical workflow so whereas in the flexible workflow there are parade delivered email templates can be reused okay if you tell you want to enhance them further you can also enhance it for a very well okay when it comes to this technology find of you so this can be a beaver based and class based but the flexible workflow will be on Vivo based class based as well as the serious base okay so then what are the benefits of the flexible as I mentioned minimal technical development so it is just a business building block where you just activate and you can run through it right the flexible workflow so whereas in the classical workflow so starting from the starting point to ending point you have to develop each and every scenario that is required as per the business requirement but for the flexible workflow you just activate it you can configure it and you can activate it so system will trigger it as per the business requirement So based upon the affiliary applications that you activated right so that that's why there's a minimal technical development and the reduce the cost so so there's no there's no more you know so what I can say is there is a less chances of reaching out to the technical consultant as and when there's a functionality is deviating okay so in that case so there will be obviously a cost reduction right so by using the flexible workflow and ability to access in Mobile tablet and desktop so if it is a flex a classical workflow there's no much you know opportunity for you to use it in the mobile or tablet right so since it is on the end of every application the approval mechanism can be run on the way on the mobile uh platform tablet and desktop so you can directly I access Theory application in your mobile and you can approve the you know required transactions easy to add change workflow so as I mentioned here so there is no technical development rate so they whatever the change are can be uh can be managed using the ferry applications just add or change a functionality in that so as I mentioned so there's a app called manage teams and responsibilities where you define the number of team so the team members in a application so that can be further used for the flexible workflow activations so here this is where you configure the flexible workflow for the sales document scenarios so we'll just see that in down the line right then the my inbox query application where the user directly log into the query application of my inbox and he can approve a reject a rework okay so you can do that activity in the my inbox application right now how to start with flexible workflow which are mandate and optional okay so as you can see on the screen there's a picture right so the straight line will you know Define you know mandatory step and the Dutchland will be saying that it is an optional stick okay so the color is also for the administrator uh a configuration expert and business process a specialist okay so as a case and the flow so the EF will be defined in the initial slides okay we'll go through it one by one okay so now the sap has given this functionality to add the approval reasons on the base of the document category let's say so for order so there is a document category is C and for the you know uh credit memory request it has a different document category and for the contract it will be B right so ing to that document category so system has you know sap has introduced that functionality to add this okay so let's see that okay so if a sales document made the condition that I Define a body so so here so there is one battery which is introduced by sap in which you can set the preconditions to trigger the workflow or not to trigger the workflow because this is where you can write whether you just uh you can enable this functionality by adding any customization table like SM 30 table where you can maintain or delete the activities there as you can directly write the code in the battery so as per the requirement this is just to trigger the flexible workflow functionality to reach or the you know uh the ferry application for further approval process so in case you do not want the system to automatically create a purchase requestion so as I mentioned so if the criteria is not met okay if the criteria is met and that flexible workflow is required for the you know third party cases let's say RL set is an individual purchase order let's say so in that case as long as it is not a Pro system won't allow you to change or you know create the purchase requestion in background so for that also you have to have the other reason uh that has to be adapted in the bad implementation okay so in order to consider this uh approval request reasons you have to go through the you know spro path like sales and distribution basic functions document approvals different reasons for approval requests so this is where you have to configure the approval request regions as you can see on the screenshot there's a uh different if different uh other reasons are there like one is for credit memo request one is for domestic order and the other one is for our quotation approval okay next Once you have you find our Pro request reasons you specify Which documents these reasons are valued by assigning them to a one or more document categories as I mentioned that these are the approval reasons are you know uh assigned to be assigned to the document categories of the sales scenarios okay so as you can see on the next screen share rate so you have to assign this approval request season to the document category of the business scenario like quotation add a credit memo okay so as of now sap has given a flexible workflow functionality in the sales only for the quotation order and credit memory test okay not all other functionalities okay so say yeah now activate workflow okay so here so as we mentioned that so system is able to uh adapt the existing functionality which is a part of the classical workflow right so these are the scenarios which have to be activated as part of the flexible workflow activation okay for this you have to navigate through the sap netweaver application server business management business management business workflow flexible workflow then you have to go to the scenario activation okay here you can find the description of the each workflow okay so workflow for sales order workflow for credit memo request and workflow for sales quotation and so how do you so there are the different Asian keys right so maybe that would be for approve reject or requestry work so these are the major I know uh decisions which have to be taken by the approval okay maybe a sales representative initiative one sales order for which there would be a rework is required so in that case the the approver has to initiate the request rework in order to uh initiate the functionality uh in order to intimate the sales representative to to do his uh required changes in that R if the requirement is not met as for they know uh uh sales criteria then it has to be resurrected so that can as eviden and if it is meeting the you know marketing criteria then it has to be approved then he can select the approve so these are the main three uh dation case which have to be adapted to the flexible uh the workflow functionality okay so that can be configured under the given birth away platform is a this is where you have to configure all this stuff okay then so functions are assigned to the team members so that they can perform various tasks okay so as I mentioned so there are different levels of approvals okay like level one approval level to approval level three approach so that could be a that that is purely dependent on the business uh requirement like maybe one business may require one or two level of approvals the other uh business may require five to six approvals right so that functions can be enabled as per the business requirement as per the standard sap provides level one level two approvals however you can add as many approvals are required you can mention it here okay then different function profiles so this is the function profile where you have to assign this level of approvals to the relevance in Azure so as part of the session we are discussing about the sales part so that they say screenshot that is highlighted with the sales part only so in the same way you have to adapt these functions for the all other profiles as well like maybe as I mentioned in the initial screen that the functionalities adapted in the purchase side and it is for the finance so those profiles will be visible here in which you can add the required level of purpose here next so we have to make sure that the system is active with the workflow or rfcs okay as you can see on the screen so there's a left side you can see uh the right marks right so these are the minimum bare minimum activations to be required okay along with that so as part of the flexible workflow you are supposed to create a new sap user that is sap underscore wfrt okay so the sap purely uses the this dedicated user ID for further processing okay so you can see that in the uh this workflow or screen as well sap has clearly mentioned that the sap user sap underscore wfrt must be available so for that you have to ask your basic system uh basis consultant to create this uh workflow user ID for further processing okay so this is the battery which we are talking about so it is SD and a underscore APM underscore set underscore approval underscore reason so in which you have to set up the other reason okay the approval reason right so in our case we have taken this and if the order type equals to 0 or so it is a domestic order then the approval functionality has to be triggered okay further so this is just a basic example scenario which I have adapted here so likewise you have to implement this body in which you have to write your preconditions to meet the flexible workflow criteria okay now so as I mentioned this is what the ferry application that is main is TMS and responsibilities is the affair application okay so with this app you can manage teams the responsibility definitions and team members functions in responsibility management okay you can use responsibility definitions and members function to Define their members that are responsible for workflows okay so a team member is a business user okay so in this case so whosoever is whatever is uh required to uh participate in the workflow functionality so they are supposed to be created as a business partner in the sap system they might be provided with an sap login user ID right that has to be assigned with the uh this partner uh what what you call this employee partner later this has to be synced with the business partner okay so that is mandatory in the s4hana system whatever the master you have for the customer either vendor or the employee that has to be synced to the business partner so which is a mandatory thing in the s4hana I hope you know all that okay so in that case the business partner shouldn't be the status of the business partners shouldn't be black market for archiving and business purpose completed so if the business partner has these you know statuses then it won't be able to you won't be able to use that ID for flexible workflow okay okay now as you can see here so each each user will be created as an employee in the sap system as you can see there is a personal number which is assigned per individual employee for which we have assigned the system ID that is nothing but sap login user ID and then we have synced this personal number to the business partner that is one two four right as you can see that you can see the personal number under the identification tab okay so without which you won't be able to use that particular user ID for further flexible workflow functionality okay so this is the mandatory thing for uh running the flexible workflow functionality so uh later so as you can see main estimation responsibility for your application you have to create you have to create a workflow team okay so in which you have to mention the team owners and team members okay so down the line you can see there's a functions uh uh screen right where I have mentioned sales document approval okay so here you have to mention who is level one uproar and which is level level to approval okay so that we can see on the screen in the live system I'll show it to you okay so let me go through this and then I'll show you on the screen itself system itself okay so many sales document workflow for your application so with this app you can you know uh so you can configure the uh required uh things here okay like let me show you that okay so this is where you set up uh the preconditions to trigger the required approval persons okay so you've just initiated the flexible workflow functionality in the battery which is written in the Sab system now in the main a sales document workflow you have to decide the preconditions for example if my order type is Jedi or then the workflow team members have to be triggered so there also you have Next Level precondition step where if the net value is greater than to answer amount then this approval has to be triggered by the approved to be approved by the level on approach if it is greater than so and so amount then that's it has to be triggered by the level to approval so like that you can mention the preconditions and the stepper conditions okay we can see that in the Okay so here if you set up the workflow with more than one approver be aware that the several conditions can be met at the same time so as I mentioned so before you can maybe you would be having different teams in the main stms and responsibility Theory application however you have to set a certain preconditions where to meet the exact team members to trigger and approve the flexible workflow criteria now so choose the required workflow so as I mentioned here so as I mentioned here so as of now sap has enabled the flexible workload for the sales orders credit memo requests as and for the sales quotations okay as part of the as far as the sales uh scenario perspective okay so here there's an option called create so once it shows the required workflow functionality then you have to click on create button okay so once you click here so this is the start condition uh just a moment okay so as I mentioned so this is the start condition so if this condition is made then it will go for the approval mechanism here so this is the start condition so if the sales data type is Jedi over then it will go downstairs okay so here are the steps so here you have three conditions uh for your step conditions so level one approval is required okay which is less than 20 000 of amount okay then it will go for the level one approach so that's why the in the step condition there's no any precondition here so if the level one approval is required as and when the net value of the order is greater than 20 000 then it will go for the level to approval as if the order value is less than twenty thousand then it will go for the level one approach okay so this is the step condition and this is the start condition so once the start condition is met with the requirement then it will go for the step conditions and it will send it to the appropriate approver okay so we will see that on this screen in a detailed manner okay so now the next activity is so this require a set of you know basis activity where basis security activity where the authorization is required for the approval functionality okay so if the person is this functionality strongly recommended for the no uh Synergy weight or solely approval is required okay maybe for example as you can see on the screen if the sales stagnation is 2910 so in that case the particular approval can can only be able to approve that a particular sales order okay so that's that's how you can control with the on the base of the you know this uh authorization object foreign a user must have authorization for below or things so as I mentioned so there are different users are involved in this one is sales representative the other another one is approval and the other one is workflow user ID so these three must have the required authorization objects and that has to be assigned for their activities okay so as you can see the user must have the authorizations like V underscore VBA K underscore 880 and the V underscore VBA candles underscore APM so these two are existing authorization objects however you also have to provide the additional authorization object that is V underscore VBA can underscore APM this is a result for the users okay and the workflow user should have the authorizations responsibilities okay so because in order to run this functionality this workflow user already has to have this authorization object as well now so business process example let's take one business scenario so I offer a demonstration purpose I've just taken one simple business scenario so that illustrates the purpose of the flexible workflow and how it exactly works in the sap okay so let's say an internal sales representative creates a sales document that requires the approval of a sales manager okay so for example if the level one approval is needed if the net value of the order is less than or equal to twenty thousand and the level to April is needed if the net value of the order is greater than the 20 000 okay so in that case we have to activate these conditions here like as you can see there's a pictorial diagram for the approval process let's say so create our app where the sales sales document then is this document is relevant for approach so this check is done in the barrier right so if it is yes then it will go and update the sales document okay so like that and uh uh yes if it is s trigger the workflow and which action okay if it is release or rework or reject so these are the activities to be triggered here okay so is the saver required then it will go this way and it will update the create a sales order update sales order whatever the required changes have to be done then the user go and make the required changes and he'll send it back to the Uproar okay so in the same way if it is released then action will go release and it will update the sales document that saying that it is approved okay then the if workflow functionality is end here if if it is reject then it will also workflow will be end as if the saying that the sales document is rejected okay so these are the things here and create sales order okay so here now the sales representative logs into the sap system and he is trying to create a sales order so as soon as he creates a sales order then system defer if the battery implementation with the preconditions are satisfied then it will set up a approval status here so as you can see on the screen so there's the approval status in approval and the reason is domestic order approval so which has been implemented in the battery so based upon the system has set up this approach status there okay now so as soon as uh this is created right let me show you that now okay so guys take the order for the approval in here's my inbox very application as the other has the value below 20 000 you can see right there's a net value which is highlighted in this so the net value of the address is 5000 so because of that the level one approach has received this order for approach so if it is more than twenty thousand it will definitely hit the level to approval okay so this is as part of the my inbox of your application okay so if something is so as soon as the sales address upload by the uh person so as you can see there are different actions right on the screen one is approve reject and request rework okay if it is upload the status of the adder will be changed to released okay if it is reworked then the status will be changed to requested to be reworked and if it is rejected then the status will be set to reject it so these are the activities which I will you know adapt in the SF system itself and you can find this fields in the VBA take a table okay there are Rafael select approach status and what is the category there so you can see these details in the Esperance system and the table will be VBA K there you can see the approach status okay yeah so if I tell you on to market the workflow process in the sap system you can run the T code as the WIA so which is an existing transaction which is available in the ECC as well as in the s4hana system okay you just have to enter the task name in the input selection criteria then execute it so as you can see on the screen you will find the list like this here select the required workflow item then click on the notes button then the next screen will be appeared with the if H activity like you can see there's a workflow for sales order then scenario for sales order approval so release of sales order so like this so the steps will be visible as soon as you click on the uh this note icon okay so here the internal sales representative can withdraw so maybe there are certain situations where the user might have saved the sales error with inappropriate information where he wants the system where he wants to edit the sales Adder again maybe he is missing with the discount or he might be missing with adding the additional components there or he might be enter miss you know sale price sales price so in that case he wants to withdraw a pro request and he wants to make the modifications so in that case so Iceland IRC do not withdraw the approval request he won't be able to go to the change mode of the sales order so because it is sent for April for the higher authorities right so in that case if the user wants to edit it back then he has to withdraw from the approval request then he make the required changes then he'll save the sales order again so as soon as he sells it again saves it again then it will go to the required approval based upon the functionality we made it okay so for that so in the display sales order then you have to go to the edit sales order then additional function there you will find the option call with the approach request foreign application where you can see all the notification which I have been triggered from the different uh you know uh areas like maybe it would be from the procurement maybe it would be from manufacturing maybe it would be from the uh a sales Etc so all those will be available in the my inbox I uh Affair application where you can go through it and you can uh you know proceed with your necessary activities so as you can see these are the bare minimum functionalities which are there in the my inbox application so you can see there like as I mentioned earlier so release reject rework these are there and you can also see the notification maybe so their level level on approval is done and the level 2 is there okay in that case you would be able to see the notification that has been mentioned by the level one up role under the notification right so there you can read that and you can proceed ingly okay so if at all you want maybe you are feeling that all the documents which are not required for you know money uh go through it and approve it so you you can directly act it you can by clicking on this icon you can select multiple selections and then you can perform Mass release options here so that all the orders will be approved uh in a sequence okay in single kick so like that so I don't want to explain all this stuff because you are you know really you will know about it like relays rework and reject okay so for example uh uh for example any uh uh the approver might be mentioned in order to the sales representative saying that the amount is too high please make a rework so that information can be seen by clicking on the notification box here so this is what a text message where you can see the information which is mentioned by the level one or level of approvals okay so now let me show you on the sap system now okay okay so let me stop sharing this or else yep okay Mahesh is my screen visible is your screen is visible okay let me show you the sap system as well so let me stop and share again okay so let me show you my sap system now okay so let me show let me come from the bad implement the concept part okay so let me show you what is to be done in the sap system okay if you go to the spro transaction right right there you have to create so what is that foreign reasons here then you need to assign it under this section okay so once it is assigned okay let me show you the bad implementation as well this is this is the battery in which you have to define the no approach and setup here okay so this is where you have to write the conditions to meet your business requirement only then you set up the approval reason for the particular sales document type okay so likewise you have to this is just a basic precondition that I have mentioned here you can mention different information you have contact information here like from the sales document the header data item data partner data Etc okay you can make use of this data and you can build up your you know business logic as per the requirement okay so then let me show you the fear application okay so this is the app in which you have to set up the you know themes foreign button so as I mentioned in the screenshot right so this is the create button where you have to create a new workflow a new team as per your business requirement Okay so click here so I have just already created it for our demonstration purpose so here you have to mention the description of the uh you know t teams okay then you have to mention the team owners here so who are the team owners and the team members so this is where you have to set up so is the level to uproar and who is the level one approval okay so likewise you have to Define it as per the team members availability and the level of approach as per the business requirement okay so once it is set up then we have to uh you know go to the next app so this is mainly streams and responsibilities if you go to the main a sales document workflow and this is the second app in which you have to set up the workflow conditions okay so workflow first as sales order so here so the this is where you find an option here like this is for whether you want to create for a sales order or for credit memo or for quotation select it and then click on create button here then you will be able to create it okay so for time being let me show you the created one so here you have to mention the workflow name okay so like as I mentioned workload for sales order you can mention and the quality periods and here I've just mentioned a start condition if the base criteria base condition is made then it will go for the next level of approach here so as far as my you know requirement is concerned then it is my sales order type which is and then if the net value of the order is greater than 20. 20 000 then it will go for the level to approval if it is less than or equal to 20 000 it will go for the level on approval okay so this is what you have to set up so these step conditions can also be done in the further navigation so here you can see so you have to name it okay so sales document approval level one then what is the step condition here so for the first level I haven't mentioned any uh precondition because so my condition only and the 20 000 right which is greater than 20 000 then it will go for the level to approve level else it has to go to the level on approval only okay so for the level two I have just mentioned a precondition here okay like step condition where the net value is greater than 20 000 INR Indian rupees then it has to go to the next level approval so this is what you can mention and the actions can also be mentioned here so required action what is the required action whether you want to make it rework or whether you want to block it okay and how do you uh know what is the next action what is so here this is where you can mention the restart workflow right so this is how you have to set up uh workflow okay then you have to activate it whether you want to act whether deactivate there are different options here you which you have to explore further okay so once you set up the main estimation responsibilities and the manage workflows and in the sap system there's a configuration and the bad implementation so these are the requisites which have to be realized in the sap system only then you would be able to trigger the sales order workflow functionality okay let me run through one uh this scenario here let's create a sales order a sub screen is visible right Mahesh so I'm just mentioning this information here and I am going to create a sales order okay so the net value of the order is 5000 now it is supposed to go to the level one approval okay so I'm saving it let us save the status of the sales order is so in approval okay so the reason is domestic approval which has been managed in the bad array so that will be visible under the approval status if at all you want to see this information so just go to the table level so here we'll find this information here so these are the three fields okay so what is the status effect a a stands for in approval relays rejected to be reworked so these are the status you can set up using the free free applications okay what is the reason and what is the rejection reason if at all you want to reject it then there would be a dedicated rejection ID which you have to manage it okay so likewise you have to do this activity right so once it is uh created right if the user wants to make the required changes maybe he overlooked the order and he created something else okay he wants to make the required changes here edit additional functions if you do not do it if you click on change button system throws an error okay sales document is an approval no changes are allowed so in that case you the user has to go to edit additional function request then the April request for the sales was withdrawn now so he will be able to edit and make the required changes and he can make the required changes and you can save it again still my network is 10 000 only let me save it now let me go to the close status now the it is again in the in approach status right let me log into the uh you know user uh the level one approval user this is the my inbox uh Fair application foreign foreign foreign yeah so this will be you know the action has to be triggered by the Uproar okay that will be a visible under my inbox item so however so actually we are you know running out of time so let us quickly get into the uh q a session Okay so so let me end up here so this is where you have to configure and uh so functional has to run through okay let me go to the QR session now yeah so Suresh we have a few questions actually so kind of excel workflow for sales order to be changed after deployment yeah so we can change it very well so as we have seen that it is a fairly comfortable function which has to be managed in this upload of your application so whether you want to add a new condition or you want to delete the existing workflow or structure you delete it and add it that will work yeah if we have another question is the flexible workflow for sales order available in all version of s4ana yeah it is from the 1809 it is available especially for the sales workflow and however there are other flexible workflows which are available for the earlier versions as well not in the sales module but in the other models and the other question is who are needed to set up set up the flexible workflow yeah okay so there are different persons are needed like this is for the initial requirement like uh you know in order to implement the body so there's a technical person a evapor is needed then one basis consultant to set up the workflow or authorizations for the workflow user ID and the sales representative and the approach and the other one is like functional consultant later once this initial setup is complete then the business process expertise can log into the query application based upon the inputs given by the functional consultant he can do it on his own okay this is purely given to the business process specialist he can manage the manage the manage teams and responsibilities as well as many sales level workflows so these are the person required for it so there's another question can we add more levels of approval as per the business plan yes we can have it and there you can set up whether you want to set whether only one person is required to be approved or any one of the members have to approve so this functionality is there and that can be managed in the main a sales document workflows yeah okay so there's another question what is the difference between the start condition and the step condition in the manage workflow theory app yeah so this is the high level the if you say the start condition is the high level uh condition so upon meeting this requirement then it will go for the approval mechanism where you have a step condition let's say if the scenario is domestic order then it has to go for the next April step conditions where you just mentioned if the order is domestic order then it will go for the April which April high is required then it will go for the uh step condition so in Step conversation you will just mention whether it is a net value or any sales department or sales office or any particular customer so based upon that you can set which level of approver is required so that is the real difference between these two any other questions there's another question coming up can we have multiple approvals for the same level approval uh can we have multiple levels of operation as we can so let's say so once the start condition is made then you have to mention a step condition whether the value is greater than so and so as as I've just mentioned it there okay the value is 10 000 then the level one approval is needed and if it is level two then if it is 20 000 it has to go to the level two so likewise you can add a number of approval as per the requirement the level one is triggered then it will go it the workflow is initiated to the next level of approach once it is approved then it will go to the next level of approval so likewise you can mention a child so in which you can Define the step conditions then it will act ingly yeah okay okay so these are the questions Suresh we'll just for a few seconds actually will wait for any questions rooting up yeah sure then yeah no issue so I think we are going to go Suresh you know yeah okay okay yeah thank you thank you all hope you enjoyed it and must have taken some input takeaways our next webinar details will be circulated along with the schedule and the registration detail by our event team thank you thank you all [Music]