Improve your sales order cycle for customer service with airSlate SignNow

How to create outlook signature

22 in the area of service and we really have made a good step forward in in supporting complex service management and also to provide a good alternative for service management for customers that were used to run the service Management in CS right um so let me quickly move forward here right so view as usual we have um the usual disclaimer I will talk a little bit about roadmap right and I'm looking forward what we have what we have done um so you know please take in mind that some of the things that uh um our forward-looking statement whatever we'll Point them out uh precisely right as for the agenda um we will give a quick introduction into the overall sap service strategy so where and where uh what is the overall picture and where are we dive deeper into s4hana service the s4hana component take a look what's new in the 22 release uh we'll have time for a demo like 20 minutes demo 50 minutes demo um and then I will spend some time to um talk about the um considerations for ECC customers so what is a CCS customer so if you are in a CS customer what what are possible migration strategies what are upgrade strategies um some things to keep in mind and and help you we are making your mind up it's not a simple topic but let's start looking into that all right let's go to it um the sap service strategy so this picture actually uh is a very nice presentation of the overall sap service strategy sap is providing an end-to-end offering um for service execution spanning uh the front office where we have the sap service cloud apparently the service execution part that we do in saps for Hana and the field service uh where we have the sap field service uh component right and each three of these components or pillars have a really dedicated um functionality and dedicated reason in the in the service Cloud we do the front office and you execute the front office all interaction with customers but this could also be used as kind of a mesh up engine to coordinate some of the back office operations right if you need to stitch them together differently this is also what we do in the service Cloud field service management is really dedicated for your mobile feed service team going out and doing the actual service execution and in the center and core we have the um saps for Hana service execution that that's sap service execution in s4hana I mean we if you look at what sap has done and the history of service solutions that sap has provided you've seen that we have also looked into different options so we have had sap CRM where we had a side-by-side solution to ECC for service execution right also we do have the service cloud and also service execution capabilities into the service Cloud um these non well if you move service execution out of your ECC core Erp core that has some advantages but also disadvantages right it may work well if you have fast moving service then yes you can move that out in a side-by-side mode but really if you do more complex service then you will see that service execution is highly integrated right so you have if you do quoting uh in in US during your service you need good integration into um your service products into your fin into your financial uh information into your pricing information uh you need your contract right contract is also something that is really requiring very strong integration into your billing and financial capabilities which you typically have in Erp world the same is true for asset Data customer data all that is typically in an EOP system and if you do service and leverage that capabilities and that data it's just much easier if you do that within uh the Erp system itself and this is also the strategy that we're taking with s4hana service and going forward and I think it's kind of you know competitive Advantage for sap to be able to provide a service execution capabilities within Europe it's just you know much simpler no integration um tighter integration into all these back office processes but I'll come to that later in a second all right uh that's it let's dive deeper into uh esperana service now we did ask for Hana service we are um supporting all core service processes so uh customer service to feed service or the reactive service process ticket comes in is processed maybe quoted and then sent out um to a field service technician uh the second topic recurring service where we have the service contract and the service plan and you have recurring service visits like you know annual inspection of an elevator also this is um supported here uh in in the Espana service and also the um return to in-house repair process where not the technician goes out to equipment but rather the equipment is sent to your repair shop so you need the returns Logistics and is repaired there um we are offering uh two process variations for that so one is the classical product so it's like all right that's um yeah the straightforward service for fast-moving and more uh simpler service execution we have this product or this option in uh on premise private cloud and public Cloud available and we've shipped this since a few years actually in the Civil constantly evolving um to cater more and more uh service requirements that we receive right um since 22 and cs4hana released 22 we also are providing maintenance service in the current stage supporting the uh reactive also the proactive service and the return to emails repairs something we have on the roadmap for 23. but this maintenance service um is is available and specifically looking to support more complex service processes where um you need more proper planning right so that's a preview so let's look at the two and let's try to understand let's understand the differences between these two options let's start with the product service like a product service I said it's a very straight uh model where we try to consolidate and make it simple um for customers which the core really is the service order with the service order items actually this one object is that one object that does it all right it's the object uh the commercial object for commercial planning it's the object for um for service planning right um also Service confirmation so in Cloud you know this object is also the object where confirmations go in where reservations are happening and where finally the building is happening so it's one object for the full service process uh plus a service contract plus a service quote to do service execution right nice straightforward clean model all Fury um and and you know works well um for straight service right so this is what we have again we've shipped that since a few years and and really you should take a look into that because this is where we think um you know if possible you know try to try to use that which is just a clean and simple uh model here right still there were customers um that said this is just too simple I said yeah well we have uh let's let's build a bit more advanced and complex one well if you look at servers actually one of the challenges and services there isn't really a one-size-fits-all right so we have customers that do really fast moving service several service done a day right and then we have customers that do enormous complex repair um where a service takes a month or weeks and uh then you know it's it's really hard to have the the very same um service process and same service object for both right so this is why we have this other model for the more complex one one more complex customers now how does that look again we have the service contract that that we have the new service contract we have a a service dedicated service built and again we have the service order so the commercial objects that we have here for the commercial uh service planner are the same in the other model right no change here but this is what uh we would want to achieve to have basically uh the same service planning um and and service commercial objects for the for the service manager right so this manager role here but what we do have we have different objects for um the the planner the technician planner and the technician itself for the execution so what we have is we are using the maintenance order the maintenance order that you know from the maintenance work or that you know from installation from uh Asset Management right so the pm01 order we use that maintenance order for planning and execution of the service right so light blue left side is the commercial world and this greenish blue we have the planning and the execution that maintenance order can read task list so you can use task lists for planning your maintenance um and then we have the operations that you know and also the spare parts procurement the components that is also on the maintenance order and also you will use standard confirmation out of q41 confirmation uh to confirm um your technician of work that was done right so so this is the the technician planning and con and execution world right and then there's a third role the financial analyst role and the billing clerk role and for for billing but we are now allowing resource related building where actually you look into a Cost Plus model so if you look at the more product service that we've introduced earlier this is more thinking a line of a service product where you can model the service that you have as a as a product inspection service or uh repair service and you have a price for that in in this world you can actually also use resource related resource related approach you can still use product price can you still use fixed price but you can also use resource related approach where you look at the costs we collect the costs of of that service and then add a surcharge and this is what you build now so we have resource related billing using dip you create the memory request and you do the invoice right we also have some integration into new the new Financial capabilities of s4hana saps for Hana um and which for example we'll give you real-time Revenue recognition so at the time costs are confirmed already the revenue is recognized in the system all right so these are um basically the three roles and the separation of the three rows that we have in this maintenance service world if you compare it to CS4 the Cs customers eccs customers you will likely recognize quite some things which are quite similar to what you have so in CS in the Cs world you also have instead of the maintenance or the PM or you have this CS order these are really you know both our work orders very very similar and others hardly any difference between the two and we are extending this maintenance order to make it look and feel have the capabilities of the Cs order as well all right also tip again you can use dip as you have used in CS no change here the only change which is uh that we have is we have new commercial objects now we have the commercial objects from s4hana service or service contract Service Code and service order instead of the SD objects as the orders that we used in CS some of the differences here all right enough said let's go we'll take a look um into that in the system right open up my system here all right here we go so this is a 22 system that's 422 and um yeah I'm you know having many roles here so I will explain where I start what I'll do which role I'll take in uh you can follow my My Demo let's start to create a service order I'm the service planner now I get a call from from a customer equipment is broken um let's get there and create a service order right first thing um I said we have two options in the system to create so it's giving me it's first asking me which of the um which of the option I would want to see it's asking me do you want to have a classical service order or a that new maintenance service order I go for that new maintenance service order all right um here we go that's basically now my new commercial object like my selling object for selling that service right it's and it looks like you know what you would expect from from a service order uh it has uh service description let's make a pump repair right um it has requested start dates external references if you have a reference um you know it will find a contract later we'll come to that later categorization and and Status right okay um first thing I get typically is is a device that I have the reference object right I can enter product a functional location or an equipment customer gives me an equipment let's start with the equipment okay in the equipment and now system is looking for the equipment as we are in yeah in that EOP system and have all the equipment data there it found the equipment it also found that the equipment is owned by a customer and Equipment database so this domestic Us customer one was identified already and now it's pulling for some requesting some work data so what is the Service employee group and we'll need that later to find the right team to do that let's pick that one as a Service employee group and also the contact person at the customer site all right that was this one here all right and still we need a bit more organizational data so I also need the sales organization that's that one here right so quick word to the organization that is we have the sales organization no we don't work this is sold we have the service execution um the service Organization for service execution right and as I said we will do the execution in a maintenance order and the maintenance order lives as a bit of a maintenance work order has a bit of a different org model it has the org model of planning plant and work center and and we do the mapping from the service group and service organization to planning plant and work center so that that you can do that and you see these uh tools right away in the in the org setup um reference objects also we have here so we already have one reference object um that printer here but I can add more right so there is um if required can add additional reference objects multiple ones if you want right and then of course you would have the usual things my prices price details but let's skip that for now all right so we have uh the order header data we have and now let's enter my service product so this product um has said you know basically we have the products that we use here and we can only use one type of product these dying products classical dying product and we map each item let's go back to that slides and if we map each item we map to one maintenance order right we have the service order we have the service order items and for each item we add we will create one maintenance order but here are the items the quantity is one that will now be mapped into that right so the item itself already has um a value all right okay so what when I enter the item what then kicks in is the uh the contract assignment search so the system found the number of contracts for the customer either or we're also for the equipment contracts are basically would then be used if I assign a contract it would be used to pull um pricing conditions for example from the contract but also it I could assign controlling of that service order to the contract so that basically you have all the the commercials on the contract and not on the service order right this is what would happen well that's that's not assign a contract for now let's keep it there separately there's a price you know status and some other interesting Fields one is the Deep profile like I said we can with this model with a service execution model we can do resource related billing using dip and for that you need a dip profile and you can use your existing the profile that you already have if you are a CS customer and finally billing relevance that's basically deciding how to to to do billing and you have currently four options not relevant really meaning you know it's it's or free for the customer you only collect costs billing on completion means that you will do um fixed price billing you know where basically what you have on the order will then be built and then there are two variations of resource related billing one is the summarized billing where basically only main items will appear or itemized building where you will even see sub items on um on on the invoice or adopt price definition right I'll just keep let's start with itemized billing all right and let's already release that order and save right and now basically the order saved is created saved and um right and in the background we have a maintenance order creator let's go to there so again this is the order it's safe now here are the items here's one item I created let's go into that item let's look at the item details okay here we go so yeah I mean just the product again nothing special here with price details um where you would have um currently list prices are there basically but you could also Define your your markup percentage or you could add any pricing conditions that you have or you know any other system for rendering pricing conditions can be pulled in all right but let's look at that maintenance order I said at this version when we create a maintenance order for execution so this is actually the link to my execution object so this was created already at the time I have released the Order release maintenance order is created um I have the ID of the maintenance order here right uh I already have the status so this is created it's the creative status uh material has been committed and pre-costed already because what we've done is there was a service product I guess the service product and there is a mapping between service product and task lists and from that service product and equipment and we've identified a task list that was that order was populated with the task list already and this is probably already have a a planned cost but let's go into that order this is basically you know from a commercial perspective we're done right so we have that initial planning and now we're changing heads right I'm leaving the role of the commercial planner and now I'm working as the uh the maintenance planner well I'm now the technician with my equipment right I have that new order on the table right um it it's it's a pm01 it's a classical maintenance work order that we have extended and some some few extensions that we have for 22 release and most importantly here's this billable flag right so all PM orders now have a the option of a billable flag and if you click that billable flag if you tick that then you say well this PM order is actually in context with a service order it's not a standalone maintenance order it's a maintenance order which is used in the context of service and if you click that then you will see two additional Fields one is the sales data as you need a sales data that actually came from the service order and also the service product service product and service information and and here's the link back to my service order right so these are the new Fields all the rest are standard Fields I said we have um the service product was mapped to a to a task list what is this information is pulled from the task list and like of course I can I can you know edit that I can add a check for example a check step since I had two hours check slip I think this is required for that device so you can as a planner I would then now do and edit the the tasks that I have same is true for the component well you will add the components and manage the components and you can procure the components anything that you're used to in your maintenance order and also in your CS order and you can do here as well pretty much but no no change here but we have that we have the cost we have well everything that you have let's go back take a sign we have that order I think it's good now I will re-ease it and now um okay material is done all right and then I'll save it and off goes the work all right so I'm done as the the maintenance planner and now it's the service technician to do the job right it's released it's out so this ignition will go out pick pick up the order in a whatever mobile system for service management do the work and once the work is done the service technician will come back and confirm that work and for confirmation click again let's change roles again let's go to iw41 or confirmation but here we go so now I'm the service technician I want to confirm the work I've done the order Kristen let's see here the order is the 366. start with that order right here our basic here is now the um the task the list of tasks that we've done and the new check the new check um Step that I've introduced and let's confirm the first one I've done with actually with the plan data so one hour is okay and that five hour is also okay and let's save that but that I have confirmed now okay what you see happening is now it's calculating costs all right sending back the cost that I've done with my my work but it's not only calculating cost it is also doing a deep simulation it's also calculating revenues let's look into that so I'm done now with my job I've confirmed it okay and that's again go back to my order so this is my service order here okay this is an execution right let's see so we have released the order work has happened costs were created let's look into Financial again changing head to a financial analyst I don't see what what nice tools we have with financial analysts in S4 one nice tool is the line item marginalized analysis tool right where you can look into into the film booking and look into um our our journal to see you know what type of booking have done I can do the analysis based on various accounting documents and controlling documents um let's have that with the service document right the service document is itself a controlling document let's look at what's happening here so let's document um let's see what type of bookings or fin entries we have based on the service document right the special service document the 1024 right what type of fin bookings have do we have for this 1024 and we have some all right so first of all they are all Associated of course with um our sales org that we've mentioned right and if you go down what we see is we see first we see cost bookings right we see two class bookings coming from that confirmation so at least 30 dollars costs are was the first um task one hour and then we see 150 dollars for the other five hours now these are cost bookings that we have and these cost bookings are already associated with the customer and with the service product and with the service document so we do all cost bookings already associated with the service document and this is why we know um it's part of service as we know that already right we can do many more things and so this is important to understand cost bookings cost bookings are already attributed with the product with the contract with the service document and with the customer for that data but if we have that we can already recognize revenue and this is what we also have in the system here we have Revenue and actually we have um 75 revenue and this number comes from dip so we've we've called dip at the time of confirmation we've called dip dip has calculated that these thirty dollars cost will result in 75 dollars Revenue right and the same is 240s 150 into 375 dollars Revenue so this is the revenue that we will Bill our customers and as we have done the job already and we can already recognize that as um Revenue this is what we call real-time Revenue recognition let's take a look into um there's another tool for this event-based real-time Revenue recognition for service documents again use our service document forward right and let's take a look what we have here so it's basically pretty much taking the same numbers as pulling the name numbers from from the from the universe Journal and uh just more nicely displayed so overall we have recognized costs of 180 this is the cost from the confirmation we have recognized Revenue the dip calculated of 450 and this gives us a a recognized margin of 270 right and this is already in the system at the time we do the confirmation and so this is one of the new things and nice things we have in S4 that we can do real-time Revenue recognition as even as the service order is still in in process all right enough said for the demo let's go back to the slides and have a uh if you're concluding uh words here okay so we have seen that model right we've seen a service order the maintenance order um and the confirmation uh and also we what we haven't done um we've done a little bit of dip for for the real-time Revenue recognition Netflix would be um debit memory requested invoice generation but this is you know as before but it's rather spent a few seconds also to understand how the quoting will work because we also have a new quote and this quote allows also allows resource related quoting right so how would that look like we have the quote it will create a line item an item for uh with a service product right either you could do fixed price and just add the product okay or you say no I need to have a resource related quote so I need detailed planning if you have this then um once releasing the quote um you will once you're creating the vote you will create a maintenance order but during quoting you will create a maintenance order this will go to the maintenance planner maintenance planner will do all the operations and components tasks and all the magic that maintenance planners do on that maintenance order and that indicate that he's done with with the planning right good World planning once maintenance planner indicates that it is done with the planning the planning information is sent back to the quote so all the the parts and the components and um and the time of the operations is sent back to the quote and then listed as sub items under that item so that then the commercial planner can then say well you know with 20 hours plus these in these parts now this will be the price that I will put on that quote right that pull quote will go out with a customer hopefully accept it and released and once it's released and accepted it will create a service order as a follow-up and that service order will use the same maintenance order so no change here we'll use the same maintenance order that has been planned before so no double work right and that will then go into in the execution as you have done as you've seen before finally the preventive maintenance scenario which we also have in with the 22 release uh where you have a service contract and and a maintenance plan to kind of now what we can do in this 22 releases um we not only create service order but we create these maintenance a service order and maintenance or service order for the commercial part maintenance order for the execution to do your um to do your execution okay um a few words to um additional resources so if you want to take a look into system and experience yourself we have two uh best practices available I have added the links here so one best practice is the one for the corrective and it's pretty much the this is an area that I've showed you plus the quoting right in one scenario or the preventive maintenance and you can download these uh scenarios uh and also there are test scripts which show you how you can walk through the system and it gives you a good idea you know what is possible and what we've shipped um there's also another recommendation for um for CS customers right so we have created we've created um a node that is showing some of the capabilities we have and some of the limitations that we have so if you are a CS customer then you would typically expect certain capabilities let's take a look into that note certain capabilities and what we wanted to show with that node is we want to give you a a rough sketch what of these capabilities that you may have been used in CS are available and which are not available in the 22 release again it's 22 release right so some of things are available so one of the things really that is important you know we have this switch to activate this new maintenance service process which is actually something you need to do in order to to come to that new process uh then yeah we have the best practices here and then we are pointing out to some of the limitations So currently for example in the company uh is not supported uh we can't do configure configurable service products down payment we don't have credit checks and there are some capabilities uh in our repair we're still uh in in processing Advanced shipment is something we will do for the 23 release so there are some things which we are still working on let's just heads up for you to see what is possible in the 22 release and when would be a time to go for a later release okay back to the slides so this link and this node is a is actually quite interesting to look into so when we want to give you know as much transparency as possible for you to make a good choice uh um roadmap um so if you were to the road map we and I've added the link to the roadmap Explorer to make it simpler for you to have service and basically everything that is then tagged with maintenance service this is relating to to that maintenance service process until the roadmap there and were the 23 release we have three major things on the roadmap one is in-house repair integration so that we have also the logistics integration into our maintenance service process Advanced shipment of spare parts right which is a specific capability that only DCS order has and the PM mode or not and also configurable service products and to be pushed down across the whole chain plus some other things we're currently working on I would just listen heads up what we are planning to do for 23 release okay a few words final words to CS right because I guess some of you may actually be using your PCS um first of all TS if you are using CS in ECC no um there is still CS in s4hana so this is still the very same capabilities of CSI in in s4hana as well and you can do a Brownfield move basically lift and shift from CS to S4 and it will continue to continue to work um CS is part of the in S4 it's 4 is part of the compatibility scope meaning you can use it until 2030. so the user drives what was extended for CS until 2030 so this is the time you can actually use that support the information and there's still a lot of confusion out there what is happening with CIS can I use this yes you can use CS in S4 and yes you can use it until the end of 2030 at which time the usage ride expires and you should do a migration to new S500 service um now what would that mean like you know if you have CS right so this is that process one that you have typically you use um you use um SD objects for selling on the SD contract you have to order an SD quote and to use the CS notification order and confirmation for the execution on technician world and the for resource related billing so this is the classical we'll see a setup if you compare that with with here at the left side we have this product service process when the first one I I showed quickly and we've we have shipped for years now these are quite different right there's also the feedback that we got if you move from CS to this simple product-based service um it's pretty much a Greenfield implementation for for service related things I mean all master data is the same that's good but the service process itself will be will be new that is still a good recommendation for many customers and we have quite a number of customers that do that because the Cs process was just too complex for them and they want to simplify and and get more straighter and it's really recommendation to look into that product um service process and simpler one to see if it will help you if not right you should consider that maintenance service process that I have just introduced with the PM or an asset what we are doing we're kind of mixing the Two Worlds the best of Two Worlds so we in that maintenance service option I have to introduce we are taking the commercial objects from aswana service um contract quote and the order and the execution object from the PM world order confirmation and looking into migration or the execution part there is actually very little to do right it's you know moving from CS or to PM order with the extended one isn't a big deal uh also confirmation is just the same dip is pretty much just also the same so here on that technician side there is an on the planning maintenance planning side there is uh not much change in that new world we are adding capabilities so we will leverage all the innovations that we'll have from the from the asset management side with the fury apps we'll also have leverage these over time so this is why we actually moved to that PM world to benefit from the Innovations here right um but but if you stay on that world that's pretty straightforward right what has changed is the commercial side you have that New Order that's more like straightforward but also you have the new contract right and this is probably um one of the bigger steps in that migration you need to migrate the contracts from the C the SD contracts to the service contracts so it's probably the biggest step in in a migration from CS to maintenance service okay a few final comments and recommendations right again we recommend you look into that straight service solution into product service that we have um see if it helps you and if it's simplified if you are CS copper a customer and happy with your CS process right you should look into maintenance service 22. see if it helps you already look into that note where we described some of the things we can't do if this is okay for you and it should be okay already for many customers just you can plan your migration if not you can look into 23 release which again will come a lot of additional capabilities where we think we can cover most of the Cs customers um yeah this is basically true also for customers that have complex assets or say you know you have biasics are so complex I can't really work with a straight simple sub solution and also for the customers that do build maintenance utilities customers very often that that have the same team doing service and maintenance and they need one solution for service and maintenance and also these ones actually would be quite good off with maintenance service all right with that actually I would want to close my presentation and open up for Q a yes we have some questions in the chat thank you Oliver for your presentation maybe um you myself and a borrow go um on camera and you unshare your screen so everyone sees us while we um well we address the questions we've got dark here in my room wow um right let's get started um first one is from Ives can we also use the orders from the face model that question was pretty much in the beginning of your presentation yeah face model I guess you mean the nine face model um from from the fury apps uh this is what we're currently evaluating some things will work out of the box others won't and we'll try to make that straight but we're working on a full integration into the face model all right thank you I hope I hardly clarified the question product service is the service order controlling object is the item-based accounting available in op 2022 yes the answer is no not yet so this is actually the thing that if you're on the simple straight product service there we still have the in okay depends really right if you are in the cloud Espana public Cloud then yes product service is controlling object and the item-based controlling is available but you're specifically addressing on premise right if you are on premise then product service is still using internal order for controlling and we are doing that change to um to item-based controlling with the 23 release okay so stay tuned we'll be coming up um next question how would a migration from CS to the maintenance service look like is a brownfield-like approach possible yeah well Brownfield typically means you kind of lift the shift right this isn't really live the truth what you would do is yes first of all you would do actually lift the shift force of Cs I do a few CS process in S4 and then as pointed out um you have New Order objects so there are some changes in the in in the selling of the service but it's more like a process change right um actually no data migration required here where we would see data migration is on the contracts on the service contracts and we are working here to come up with some Concepts and how that could be done so that would be you know several objects several modes thinkable but if your contracts expire often maybe you run your old contract until it expires and then on renewal you create the new contract in in maintenance service if you have long running contracts then you may actually need to have a migration but again this is uh probably the biggest thing and we are working on voting that it will not be a click on a button although it this will still be Project work to do perfect thanks to this just said that his question was answered but maybe that helped if someone else listens to the recording and uh the question comes up for that person um next question can we ask the customer for down payment from his MCSO order all right this is something also we have on the roadmap as one of the limitations we have in that in the note this is what we hope to have in the 23 release right also coming up um the next question was asked during your demo um for you to to know where you can put it in uh into the sequence of you presenting and how can we use this with a maintenance plan as a starting point yeah again this was that pointed out in in my later slide where you actually we have that integration into maintenance plan and we have new call objects that you can actually use main internet service as one of the call objects in the maintenance plan okay then a question generic one everything we're seeing here that was also during the demo um isn't sap s4hana on premises 2022. yes that was an on-premise 22 system also uh private Cloud um yes in 22. correct perfect thank you then two questions by Ganesh um after PM order is qpcd if component is added is there a way to transfer the information to the maintenance quotation Yeah so basically um the qpc if qpcd means quote planning completed thanks then so basically when you when you complete uh the upon completion of the quote planning right then um then the components are transferred to the maintenance quotation so you have then in the maintenance quotation you will see the list of components um but once the quotation is completed then right it's it's already there I'm not sure if you can do that multiple times okay garnish thumbs up if that helped you out if not you can reach out to Oliver later on in the sap Community I'll share the link to his sap Community profile um another question here is it possible to bring in the spare part Etc to msco and not create PM order for these items right yeah actually so if you look at that maintenance service or the MSO then yes we have only one item type this is the maintenance item and that maintenance item will create a PM model but this is basically how the mechanics work and and then um on that PM order you do the spare parts planning because you know we want to make it as close as possible to CS if you want to do spare parts planning on the service order and you would use the straight plain simple product service order the srvo the srvo the classic one that has time planning and spare parts planning on the service order and you don't need APM order for that so this is the other model that we have and and for that if you want to do spare parts planning on the service order use this service order perfect thank you and garnish just um gave me a thumbs up that it answered his a question before and hopefully now the second question as well so thank you for your questions garnish um one more here by Kevin um any plan for maintenance service in s4hana Cloud yeah good good question um we are discussing that of course because it's it's a pretty powerful tool set right you can do many things however currently if you look at as you can see we have reused many of the existing ECC capabilities that dip um the the maintenance planning capabilities which are not really cloud ready and so we need to rework them we are currently investigating if if and how we can make that cloud ready um currently there are no concrete plans but we have that in mind very much okay there's lots to come so to say perfect um yeah that was the question so far in the chat a lot was covered Oliver thank you so much for your time and your presentation maybe as we have two more minutes is is there like one key message that you'd like to hand over to the sap Community what what should they take take with them from this call right so uh pretty much from my experience with talking to many customers if you are Cs and I guess many of your customers are still running CS right I think what sap is providing with s4hana service this is by far the best option that you could have as a next step for CS so there are a lot of messages out there um look at that maintenance service see it's it's a very simple step you can reuse many of your assets um you can um yeah it's it's a pretty relatively straightforward step look into that and um sap will not let you down right if you have CS and spread the word right with six thousand CS customers out there and you have the same problem yeah you have to meet them spread the word that we have a nice replacement for CS in S4 and they should take a look at um very easy and handy way to spread the word is sharing the link to this recording that is available under the exact same link that you're joining us at the moment um two more questions by garnish and I love how many abbreviations you use in your question scanner so for fixed price billing we need to use dp92 and use the billing type as on completion oh yeah yeah all right so for fixed price billing we do not go via dp92 but we do um you do direct billing right through the release yeah yeah that's exactly already figured okay that was his second uh double checking question cool all right thank you everyone uh who joined us today and who um asked Oliver uh with your questions of course the sap Community is the place to ask questions in general um and our experts in the community are eager to help out but as I said always um profile link to his sap Community profile is shared in the chat and you can reach out anytime that's just what I now say okay thanks for the confirmation yes all right perfect then good with that um I wish you all a wonderful rest of the day and I hope to see you all soon in our next sap Community call thank you naboro and Oliver for joining us today thank you thank you bye-bye take care goodbye