Streamline your sales order workflow in employment contracts with airSlate SignNow

How to create outlook signature

hello everyone this is ashley with quest and welcome to quest experience week today is jd edwards day and our session is efficiency gains managing sales order work order relationships ux1 and orchestrations can ease the pain of exceptions with brian rose and bernadette durham with terrillium a few housekeeping notes to go over before we get started all attendee lines are in mute and will stay in mute throughout the session if you have any questions please feel free to put them into the question drop down box located on your go to webinar panel we will be answering questions at the end of the session this session is being recorded and will be uploaded to the quest content library at this time i'm going to pass it over to bernadette who will kick things off thank you ashley you appreciate it uh thanks everybody for joining us really really glad to have you join us today um i'm actually super excited about this session i always love presenting at any type of conference anyway um but this one is extra cool because uh it's the first time that i have gotten to co-present with brian rose we are we are colleagues at terrillium i'm a solution architect on the distribution side of the business and brian is a solution architect on the manufacturing side and i was kind of laughing um getting ready this morning because i'm i'm always miss let's tell people how they can make the system work better for the business i'm i'm miss process and brian has become very much about let's leverage the tools and when we were talking through the session for today this became very much a meeting of the minds and how do we make the tools meet the process and work for the business this is probably the presentation that i am most excited about of any that i have done at any conference in the last three or four years so thanks for joining us i am super stoked about this one uh so we're talking about uh the relationships between sales orders and work orders specifically but i want to make it really clear that the concepts and the tools that we're talking about can apply to pretty much any transactional situation where you've got two where you've got two orders or two sides to a transaction in the system it doesn't matter functionally where in the system you are it doesn't matter what type of documents they are the same concepts and the same tools would work irrespective so we're in distribution and manufacturing today but this could work just as easily between manufacturing and finance or between two pieces of of a finance process um so we're going to be focusing on using orchestrations and a little bit of using ux1 tools to look at how we can take some of the pain out of managing exceptions that occur when we're running into issues with uh with producing work orders to meet the requested dates on sales orders and i'll talk in a minute about what some of those issues are but also about how we can put some necessary controls in on the sales order side um so that we don't actually shoot ourselves in the foot when we're trying to provide customer service and actually make things more difficult for manufacturing to to produce as we need them to uh so first of all introductions uh i'm listed as bernie durham honestly half the time i never know what my name is i got married um you can still contact me at the durham terminum.com it does still work these days i am bernie dana miller um and i've been working with jd edwards for going on 23 years now um it just makes me an old fart i started out in industry as a business analyst and then got into consulting almost 15 years ago and and spent the majority of that time as an implementation consultant and for the last five years or so i have been working as a solution architect which you know pretty much means that i feel whatever role nobody else is feeling at the moment but a lot of what that role entails is working with companies to identify areas where their processes and their software are not fully meeting the business needs so a lot of what i'm doing is working with companies to identify opportunities for incremental improvements and ux1 tools and orchestrations have been absolutely enormous for giving us tools to be able to meet some of those business needs without enhancements and also with the ability to actually remove some of the enhancements and get back to a vanilla footprint so that's a large part of what i do i also head up the distribution team at terillium and i'm going to shut up for a minute and let brian introduce himself thank you bernie hey guys brian rose uh i'm a newbie to jd edwards compared to bernie she's been doing it forever uh 10 years jd edwards 10 years with terillium i grew up in a supply chain company so i've been doing supply chain all of my life my role is very similar to what bernie spoke about it's just more with a with a manufacturing twitch to it so understanding how we can automate and process improve and standardize different organizations leveraging whether it's process improvement or like bernie talked about the tools so i i've been very fortunate to leverage orchestrator for a long time i think i started using it back in 2014 2015 when it first came out so it has come a long way from where it was to begin with which is great uh and also we see more and more people you know leveraging it and seeing business use for it so looking forward to today and i'll go ahead and hand it back over to brent cool thank you brian brian sounds a little bit funny because he is sitting in uh in a lounge at an airport right now and um dealing with a little bit of background noise so apologies if we get some background noise there all right so before we jump into the actual exception management of this i wanted to talk just for a couple of minutes about how important dates are when we're talking about honestly anything to do with managing sales orders and producing to fill them one of the things that i consistently run across dealing with clients is misunderstandings about how sales order dates function and i'm not going to get into a ton of detail um so if you do have questions about this you can absolutely feel free to either ask questions and we'll hit them if we have time at the end or uh email me and i'd be very very happy to follow up with you about this but when we put an order in the system the system tries to drive everything from the requested delivery date and a lot of times folks don't understand that when we enter the requested date the system does treat that as the date that the customer is requesting the product gets delivered to them and if you don't have anything set up that is driving transit days in the system either through preferences or through transportation it doesn't necessarily behave like a delivery date so you don't have to treat it like a delivery date but that is what the system is doing so there are really there are more dates on the order but the ones that we're really caring about most of the time are when is the customer requesting it uh when do we need to pick it in order to ship it on time so then my promise ship when do i have to ship it in order to deliver it to the customer on time and if you don't have any date set up in the system then whatever the customer requests for delivery as long as it's not a date in the past um the system is going to default all of these days to be the same if you're actually producing product or if you're needing to actually purchase product or move it in order to fill those orders the system's going to use that scheduled pick date in order to derive when that product needs to be available to actually be physically picked to fill the order so if you're running mrp if you're doing any kind of planning or if you're producing work orders that scheduled picture is the critical one for when the system thinks that you need to have that product physically sitting there in a condition that you can pick it and start packing it to be able to ship it and i'm going to click through these slides pretty quickly um i'm i'm alluding in here to the fact that you can use preferences advanced preferences or you can use the setup in transportation routes to manage how the system will apply date calculations to back schedule to calculate into these dates i'm not going to get into those in this session there is an appendix on the back end of the slide deck that goes into a little bit of detail not a ton um so again if you have questions about these please ask questions and i'd be happy to follow up with you but the basic way that the system calculates is it's a back schedule the customer is going to give you a requested date that they would like to take delivery of the material and what the system will do is it'll start calculating from that date it'll start using that as the promise delivery date then it'll look to see through either preferences or transportation or out if there are any transit days that apply to actually get the product after you ship it to that customer and it'll back those days out to back schedule to calculate when do i need to ship it in order to get it to the customer and then it'll back schedule again it'll look for either lead days or um what are called order preparation days to see if you have specified that you need a certain amount of time to actually get that product either through quality or packed or something else that you have to do within the warehouse between having it picked and actually having it ready to ship and so what the system does is it's back scheduling and as long as that scheduled pick date is not prior to today's date the system will actually let you place that order which if you think about the situation when you're actually going to need to produce it could be a bit of a problem um if you're going to be entering a sales order that's going to create a w line type for a work order you've also got to have time to actually produce material and what the system will do is it will look to see if there's a lead time set up for the item branch that the line is created for and if it can't produce in time you'll get a warning not an error um the system will assume that if you get a warning and you decide to go ahead and place the order anyway that you know what you're doing and you're either going to be able to suck it up and produce it today or you're going to be able to suck it up somewhere in that picking shipping delivery process in order to get it to the customer on time so what i want to lead with is the fact that while we are talking about how to manage exceptions there is also kind of a need to recognize that you should have a good date process on the front end of this because if you start building a a process over an inherently bad setup you're gonna end up making the software look like everything is being handled as an exception um when we're talking about making exception handling easier that doesn't mean that we're trying to have it so that the entire business process is being handled like everything needs to be an exception even even when everything is going great even when your customer service folks and your customers are placing orders and paying attention to what your lead times are you can still end up with plenty of different scenarios that are going to cause you to run into situations that make it um challenging or impossible to actually produce on time and when i when i saw this picture i kind of left because there isn't anybody that's dealing with supply chain right now that doesn't look at that picture and know exactly where i'm going with it practically everybody that is dealing with distribution and manufacturing has dealt with some level of supply chain just crud um in the last 18 months and um and and that has compounded the normal things that can cause us to have to deal with uh with work order oopses we're used to dealing with the fact that we'll have material shortages because the supplier either either short ships or they they send us product that has quality issues so we're sure on raw materials we'll have that machine that was running just fine and all of a sudden we have unexpected downtime but going through covert you know we've also had short staffing we've had to um we've had to have closures we've had to completely deal with running out of raw materials so what has in the past just been an exception basis has made it completely apparent how painful it is trying to deal with those exceptions especially in in a manufacturing environment so what we're looking at today is how can we better manage those how can we provide visibility on the sales order side when we do run into those um oopses on the work order side and also how can we put better controls in place on the sales order side to protect us from actually making bad decisions so like i already said the system doesn't force us to pay attention to lead times and order entry um we need a mechanism if we do that to recognize as we're updating our work order that we cannot meet the time that was requested um if we for any reason need to change the expected completion date on the work order it doesn't automatically update back to the related date on the sales order line usually that involves somebody in manufacturing either picking up the phone walking across the street sending an email and hoping that somebody on the customer service side actually reads that message or even worse they forget to do it you know they change the work order and the next thing you know somebody in customer service is screaming because why isn't why isn't my stuff ready to ship and whoever it was that updated the work order completely forgot to actually call customer service and let them know we can't meet your date we're pushing out the work order so we're looking for something that will actually take the memory piece and the not getting 300 emails behind factor out from communicating the update to the customer and something that can actually take the manual work out of executing that update to the to the sales order and then lastly um one of the pieces that's always bothered me about the sales order work order process is best practice tells us that there is a point at which we should no longer be making changes to a sales order if if i've got a stocked product i know that at the point that i generate a pick tick to the what stick it out to the warehouse i really should not be making changes to that sales order i've released it to the warehouse i should consider it to be in the shipping process from the work order side the last point at which i can get a standard update from jd edwards is when the um the parts listen routing is attached and that doesn't necessarily reflect when the actual manufacturing process is started and so something i have wanted for a long time is a way to get an update back to the sales order when the first action of that work order production starts and that is something that we can manage through an orchestration so that i can now get an update a status update back to the sales order that tells me when that process starts um so brian is sitting over there chomping his teeth because i'm talking for too long here's what we're going to show you the status codes at the top are what i would typically expect to see in a really simple um work order process on a sales order w line type i enter my order and this is my next status i enter my order my work order gets completed i may sometimes have an interim status there if i see the world quarter and parts list get get attached um and then my pick ticket gets generated what we're going to show you today is what it looks like if i can see when a date change suggestion gets made because the work order um completion date gets changed we're going to see that pushing data back to the sales order and notifying the customer service originator that they need to look at it and make a decision whether the customer is going to be okay with that date change we're going to see another status change when that date change gets accepted and we automate the update to the sales order to say okay we can live with that those are going to be our new dates on our sales order and we're also going to show you how we can put control in place so that when work order production actually starts we get a status that we can now use in sales order entry to prevent any additional changes on that sales order line so that we don't shoot ourselves in the foot and ask for changes that that we can no longer accommodate so i'm going to hop over into jd edwards and i'm going to enter sales order that's going to generate a w line type and because i'm a good customer service user i'm going to to give my manufacturing team plenty of time to produce this product and so you'll see that i do have i do have dates set up here that are um that are back scheduling for me so i'm requesting delivery on 12 23 um that is that is then back scheduling to tell me that i have to schedule it two days earlier i've got two days of transit time and it's telling me that i need to pick it on the 19th that is um that is because i've got two days of warehouse setup time built in um and so i actually need to have this available to pick on the 19th so i'm gonna go ahead and place that why did you not like that well this is this is all kinds of fun because i did this earlier and it worked just fine bernie i think the sales order is 1546 thank you sure if i could type i don't know how many times i have said this in the last two days if i could type i'd actually be dangerous all right so you see that my sales order was created at next status 530 i have my work order number here and so imagine here that a little bit of time passes and this gets celery for tea manufacturing and they're planning work order and brian who is my manufacturing team is like all right well ordinarily that would be absolutely fine but in this instance we we can't meet that that scheduled pick date we actually can't produce that until december 31st that's the earliest that we can actually ship this and so on the warehouse side what brian is going to be doing is he is updating the um the work order to reflect that they can't produce until december 31st and and when i turn this over to brian he's going to show you the orchestration piece of this and and what is actually driving the update that's coming back so first of all before i even refresh this you see i've got a notification up at the top of the screen i'm going to refresh this and what you're going to see is i've got a status change pushed back to my sales order so i see 533 that is my indication from customer service side that the work order has been updated to say i cannot meet the date that you requested now we don't want to start changing the sales order dates until customer service is actually taught to the customer so what we're doing is we're updating that that new date that manufacturing is telling us they can do we're putting that to the user reserved date field and that orchestration as well as updating my my status on my sales order putting that new work order date that we can do into the user reserve date field it's also sending me a notification telling me as the order originator that the date has been up updated and it affects this sales order now if i didn't have the sales order open right now i could launch directly from this notification to come into here and it's going to bring me in to work directly with that sales order i've also set up um i've also set up a watch list so if i refresh this real quick because you know people take vacations um it may be that the person that originated the order they may have left for the day or they may be on vacation when this date change gets notified so you may also want to have something but somebody else is able to keep an eye on date change requests that are coming through and make sure that they're actually all getting managed so if i come back into this date change here if i take a look at this and either i know i i know that we're in in a manufacturing crunch and the customer is going to be okay with this or i talk to the customer and the customer gives me the thumbs up what i can do here is i've got a form extension with an orchestration behind it that when i select this line when i highlight this line and i take my date change it's going to grab the date from the user reserved date field it's going to make that my new scheduled pick date so that it now matches the expected completion date on the work order and you're also going to see that my promise ship date and my promise delivery date they're also going to get my lead days and my transit days applied to them you're also going to see that my next status is going to update so that i can tell that this went from 533 meaning i needed to be reviewed to going to a 534 meaning now i've now i've actually been executed and and i've been changed so you saw it flashed up a little submitted and now if i click find i've disappeared and now if i look at my records at 5 34 now you can see my scheduled pick date got updated to that 12 31 date and my promise ship and my promise delivery date are reflecting my two days for setup and my two days for transit and my next status got updated i've still got visibility to my customers original requested date i can see in the ledger that each one of those steps happened and i do still have the ability if i want to to work with manufacturing and figure out if there's something that we can do to kind of find a halfway happy i don't i'm not locked into having to um to accept the date that came from manufacturing i've still got the capacity to do all of the normal things that i would on the sales order including actually cancelling that line and then the last thing before i hand this over to brian would be when we actually get to the point where we start production on this work order um this is this is the point where normally it's completely invisible to me when manufacturing actually starts so i don't have anything from the sales order side to tell me hands off do not touch this they're actually producing it at this point um so brian is going to do an issue as if he is actually starting production on the uh on the work order let me go back to my original yep there we go and when he did that first um that first transaction on the work order as if he was actually starting production another orchestration updated the status on my um i stopped sharing another orchestration updated the uh sales order so now i could actually use that status as a processing option control in sales order entry to prevent me from being able to to make any changes after we had started uh production all right so at that point i'm going to hand this over to brian and now he's going to actually walk through what that orchestration piece of this looks like that is actually driving those updates to the uh to the sales order great thank you bernie and uh hopefully you guys can hear me better now like like bernie said i'm in an airport so try my best to keep the keep the audio down in the background so can you guys see my screen yep okay great all right so like bernie spoke about in the the goal of you know the next 20 minutes or so is to give you background of you know how all those functions and features uh were running in the background from an orchestration perspective how do we create the service request how do we attach them to specific steps or clicks or buttons what are some of the key components around orchestrator so this is an example here of that order number that furry came in and created so when i came into my manufacturing work order if i were to jump in you'll notice i can come in make any changes that i want and i've added this little button here which says update sales order date so what that means is it allows me to make changes to the requested date maybe do some simulations look to see if i change to this date will it alleviate my shortages or give me the capacity that i need and once i've firmed that up and i feel like my date is where it should be i can run that update so that update is leveraging a form extension with an orchestration built behind it so to give you some understanding of you know what that orchestration looks like i'm going to jump into orchestrator studio and this is the orchestration and the great thing about orchestrator as a whole is it's it can be as simple or as complex as you want it to be so uh for this specific use case we had to one know which update or which sales order we're updating uh which line possibly on that sales order and then we had to go and update two specific status codes so our last status and our next status and then we also wanted to update that user reserved field so we exposed that field with a form extension and now that allowed us to create or add different values inside of that step so you can see in here this is just a two-step orchestration the first one is me taking the values from my work order and passing those into my sale order details updating that status updating that date and then also sending that notification so the bell that bernie saw inside of jde that popped up and said hey there was a change made that is built out inside of this orchestration so this service request what's great about these is you can come in and create them manually if you want so if you know exactly all the clicks or all the functions but more times than not what we see people leveraging is a tool called the process recorder okay so process recorder in jde uh think of it like a macro in excel to where you click start you do all the processes of everything that you want to do you click stop and it captures every single click from me querying on a sales order to go into the detail line to updating the status so if i jump over here to jde what we're going to do is kind of show from start to finish how you could build out this type of orchestration from creating the service request to attaching a notification and building that out so let me jump back here into jd and i'm going to go into my sales orders okay so here is an example of a sales order that came in like bernie sanders the 520 status 530 next status and for the orchestration update i want the ability to go in and update some key specific values okay so to do that i'm going to go ahead and just click all records let's bring up some more data up here in the top and this is in any application you go into in jde if you click in the top right you're going to get this little record a process button so if you click that i'm going to go ahead and start it and then all you're doing is clicking through all the steps you would normally do when you want to make this change so i'm going through i'm saving through my header i'm then coming in here and saying okay i want to first update my user reserve field to a date i'm going to put in this 12 31 2021 and then also i want to update my last status to 5 30 and my next status to 5 33 okay click ok and then stop so all the steps that i just went through from clearing the sales order to saving through the header to updating the sales order line was captured in a service request so we'll just call this service request request i'm going to save this all right so now that i've created that service request i can jump into the orchestrator studio and i'm just going to go ahead and log in and log out and each of those service requests are if you're going through an application it's going to build out a form request so a form request in orchestrator is me clicking through any type of view edit form okay so if i come in and look up request can just find it let me try real quick i didn't like my search okay so it's not like in my search let's build it out this way so let's start from the top at the orchestration okay so once again this built out my service request or form requests but we still need to associate that to an orchestration to actually be able to leverage it inside of some type of form request okay so to do that i can come in here and click new i'm going to call this quest form request request form sales order update and then i can go ahead and determine which different components do i want to build out inside of this orchestration so in this example once again i'm going to be leveraging a form request so i would click the add button see if i like my search in here [Music] here we go so now i have my service request and if i click save and let's go ahead and jump into this once again to show you all of the steps that are being captured uh when leveraging that uh process recording so it's showing all the forms that i'm walking through it's showing all the values that i'm passing so what as you get comfortable with the orchestrator you'll kind of realize once you run through a process recording how you can clean up some of the inputs and outputs so a great example is i'm going to go ahead and clean up the default value for order because i'm always going to be passing in something new when i query down to a specific order i don't need to pass anything so i'll just default that to a one right i can pass through i come in here and this is where i say okay which world do i want to update if i were doing a sales order that had multiple lines i could pass in a specific row that i wanted to update since this was a single line sales order i would just default this to a one i want to pass my date and then for this specific update i'm always going to be passing in 535.33 so instead of making the orchestration more complex than it has to be i would just say you know what i don't need to pass in any inputs here i'm always going to go to 535.33 so what this gets me to is now i really only need to pass two key values to determine or make that specific update i need to pass in my order number which is my sales order and i'm going to pass in the date i want to update that line to the status changes it knows automatically in the background what it should be defaulted to so once i've done that i click save right back out and now it's going to say like i said these are the two inputs that i need to pass i need to pass order number i need to pass date and the very simple way to add these to your inputs from an orchestration perspective as you can click this little button up here which is add inputs to orchestration so if i click that and then auto map it will automatically create this mapping for me it's where i know where i need to pass my specific values to so from the from the process of me creating the uh form request to process recorder to coming in and generating the orchestration it's a five ten minute task and that's what's so incredible about orchestrator as a whole is you can build up so many different iterations of a specific function or business case with very little time and you can apply these to any type of click inside of jd edwards so once i've gone i've said you know what i've built this out the way that i want it i'm going to go ahead and save this and so for me to associate this to a specific step or click or button inside of jde that's leveraging that form request functionality that i was talking about so let me jump back in here to jd edwards let's go ahead and log in log out okay so let's go ahead and just for example purposes i will grab this work order and this is that button right which is doing all of that orchestration run in the background uh to go ahead and look at kind of the guts of what that's doing i would come over here and click that form extension and in here i can do all different types of things so i can add a button i can go into my associate orchestrations so to just give you an example of how you could add a button and associate that orchestration behind it i would click the ok here drag it to where i want it let's just call this request once i've associated this button i can now uh click and determine what orchestration do i want to kick off when i click this button okay so what i would do is click into this control button and what's awesome about this is it doesn't just have to be me clicking a button it could be when i click the ok it could be after i put in a description or after i exit a control so every single field inside of jde you can use as a trigger you can pass values back so if you want to go grab something in an orchestration and pass it back into the glass all that can be done when you click in or out or go to a visual assist so you know everyone always talks about the clicking of the button and how that can you know process different orchestrations which once again is a great tool but also you can't have it be done if you click into a field or click out of a field which i think is really powerful so we're going to go ahead and say i'm going to take this so when i click on this button i now determine what orchestration do i want to run when i do that so you can see i have my orchestration here and then i determine which values from this form do i want to pass right so i want to pass my requested date from this field so this is the date that i'm going to be passing up to my user reserved field and then my sales holder number now if this was a specific orchestration to where maybe sales order number wasn't in the application or there was a value that's not in the view that you need you could leverage a data request to pull that information and use it but for today's purposes what's great is inside of additional system info it will give us our sales order number so i can also say i want to map the current sales order number and the current date in a specific version when i run this orchestration okay so just like that i have now associated to a button an orchestration to where when i click on it it's going to pull the date from my requested date in the work order update the user reserved field based on the sales order that is associated to it so once again when we think of this from a from a timing perspective in a use case perspective we can build something like this out in minutes not hours normally what takes the bulk of the time when people are building orchestrations is determining all the use cases or where it makes the most sense to leverage them building them out is is the easy part and this once again is it is an example of a very simplistic orchestration there's situations where we have some that have 10 15 components and those can run through different rules and different calculations but for this we're just trying to do a status update and also update a um a specific date on an order now the other key uh orchestration that i ran for bernie was when i did the issues so i'm gonna go over here and pull up a work order so in this example you're gonna see this is more uh me running something when i were to click on a value so example you don't see a button in here you don't see anything that would assume or give you the thought that there's an orchestration associated to it but when i click this ok button it's going to say hey if there is an issue that is done and it's associated to a specific sales order go in and update that sales order so by leveraging that form extension again and you'll you'll notice in here if i come in and look at my associate orchestrations i have this orchestration that runs and if i come in and look at it you'll see when i click the ok button i want to automatically run this orchestration which is production started i want to pass my work order number which is going to then give me uh my sales order number that is associated to it and update that specific sales order okay so this is doing that orchestration once again based on a click of the ok button versus a click of something like the button that is added to the screen now from a background perspective or what that function is actually doing if i jump back over here to my orchestration here is the production started so this is a great example of a form that doesn't have that sales order number but i need to still go and update a sales order so the first step of this orchestration is me going and finding that sales order number so i can come in and look up my work order number in the in the 4801 and pull back what sales order is associated to it so from that point now i know which line do i want to go in and update for that specific sales order so i pass in my sales order number into my order number field it goes through all the steps from updating my statuses updating my rows just like the the previous orchestration did so this is that example of me grabbing data before i run through my form request versus the previous example where everything that i needed was in that individual click so once again from a background orchestration perspective this is a very very powerful tool there's all different types of use cases that it can be leveraged for for today's example it was you know pretty simplistic of updating a couple of fields but from a power of not having an end user have to do it it adds a ton of automation so that's kind of talking through the guts of how this orchestration works and runs i'm going to go ahead and pass it back over to bernie to close us out and then answer any questions that you guys have thank you burn i always love how you make that sound so easy for anybody that doesn't think that it's that easy i i kind of concur i don't make it look as easy as brian does um so kind of uh just just wrapping this up a little bit and then we'll get to questions um the uh the the powerpoint that i'm using will get saved out to the um to the session so that you can access it if you're not able to get it please feel free to email either me or brain and we'll get it to you uh it does have a couple of simple flow diagrams in here showing um kind of the process that we went through and screenshots of what we showed you in jd edwards and what i wanted to uh to finish out by talking about was the fact that the same general concepts can be used in in some other situations uh and i'm talking specifically on the distribution side now because that's my happy place um some places that i have used and i'm planning to use the approaches that we've used today are with direct shipments one of the things that i ran across a lot are with direct shipments things like will will actually get the supplier invoice and uh will be charged freight from the supplier and based on the freight that we're charged from the supplier that will determine freight charges that need to be passed on to the customer there isn't an automated way without without using these kinds of tools to actually get that freight onto the sales order unless you have a standard freight calculation so if you're either passing along the freight charge from the supplier or if you're using that as the basis of your calculation you can now use an orchestration to pick up that freight charge from the od purchase order and use that to actually create the freight charge line on your sales order before you actually complete the update and send it onto invoicing transfers i i have run across all kinds of weird and wacky scenarios where where people either want to receive the transfer before they um complete the shipment on the the st or they want to do something with receipt routing on the ot that updates the st so it's just another situation where you've got related sales order and purchase order and and you could use either ux1 tools to to manage uh information between the two to to give you visibility or orchestrations to actually manage updates one of the ones that has kind of plagued me for years is if you use the standard rma process um when when you receive the om purchase order for returned product and you run the standard batch program the r400502 i think it is to update the credit order there isn't capability to um to put the return into receipt routing and not update the credit order to issue credit to the customer until you actually complete return to stock as soon as you receive it even if it's going through inspection um as soon as you complete that receipt even if you haven't put it back to stock it'll update the credit order and say issue credit to the customer personally i don't want to issue credit to the customer until we've inspected it we actually know that it's okay and we're going we're going to accept the return of it um so i would have capability to eliminate use of that batch program and wait until i actually put the inventory to stock and then use that return to stock now to trigger an orchestration to update the status on my credit order to um to actually trigger invoice to the customer and those are just the ones that i thought of as i was putting the slide deck together um i'm sure there's probably some things i've run across with uh with under company sales where you've got an sisk okay type situation um i know i've had funky requirements for markups on the inter company piece of it where i could probably use something like this and and you know that's kind of the thing with these kind of tools is you don't know that you need them until you actually need them and this is this has given us a place to go where in the past we probably would have been going down the road of of considering doing enhancements um so at that point um i'm gonna look i know we had at least um i know we had at least one question come in i'm going to turn my camera off so you don't see me looking at my other monitor and looking like a total here um all right so the first question that came in i'm not sure i'm gonna have a good answer unless brian does at least not right off the bat um so does this affect commitment flags of configured items in the past we've had issues when the dates were changed on the sales order line the commitments reverted from the work order back to the sales order and only when we re-ran work order processing did the commitments revert back to the work order um i know that for both kits and for configured items that the um that basically your child items the flag for commitments gets changed when um when the work order parts list gets run and that then if you do edit the sales order line again that it resets that commitment flag back to the sales order um and so i i think what your i think what you're describing is is actually what i would expect to happen that if you edit the sales order you typically would expect the commitment um flag to to update back on the sales order so i think i think with the as we were showing it today there's kind of a timing situation ideally you would be identifying that you couldn't meet the sales order date before you were running the r31410 and so you wouldn't have actually updated your commitment flag at that point um the the you'd run across that issue if you'd already attached your parts list in routing then subsequently you were identifying that you couldn't um meet the date i think that one possibility at that point that you could look at if you if you're using transportation you could possibly look at making a date update through um through a shipment rather than doing it through the sales order and see if that um see if that maybe doesn't affect your commitments the same way as it does through the sales order i'm not sure about that um but if you if you did uh make a change to the sales order after you had uh run for 31 410 i would expect it to um to reset those commitment flags on the sales order i think that that is the system functioning the way it's intended and if i'm misinterpreting that question i'm not sure whether the i'm not sure if the mics are open now to where you're able to jump in and clarify that um brian this one is probably one i need you to jump in on um the question is can you run the orchestration over multiple rows in the grid i.e repeat for the grid i want to say the answer is yes but yeah yep yep so um in this situation let's say it's a the sales order update bernie was talking or it was showing where she clicked the button and it automatically updated the user reserve date into the pick date you could if there was let's say five lines or five orders uh that had that situation to where the uh the date was updated you want to process them all at the same time you could select all the lines it would process them all thank you um and then uh question what tools and application release are most of these features in orchestration available on um update 22 or earlier versions i know definitely earlier than update 22. yeah yeah so um you know a lot of the stuff that we showed today you should be getting probably the 924s uh you know from adding something with on a from a personal form adding a button those are the later 924s 925s is when you should get to them you don't have to be on the the current release that we were showing was nine two five two uh was the environment that i was in so uh definitely doesn't have to be 22. okay uh that's that is all that i am seeing for questions right now um if you if you do still have questions please drop them in uh if you have questions and you you want to send them to brian or i or both of us right now i've got our email information up on the screen like i say i will make sure that the powerpoint slides get posted on the quest site along with the session so you can access it there if you would prefer to shoot one of us an email we'll be happy to send it to you and if you've got questions uh either about anything in today's session or if you've just got more general questions about anything to do with jd edwards and business situations that you are running into uh you might have got the sense we're me especially i'm kind of a nerd about this stuff i massively enjoy doing my job and um this is this is kind of my happy place talking about things that can help make your business run better so even if it's nothing to do with today's session and there's something that you would like to talk to um feel free to drop me an email and i would be happy to get on a call with you and talk through whatever you've got going on uh aside from that um oh hang on might have one more one more can you i think uh kind of following on from the previous question about updating multiple lines uh it was going into can you update multiple orders yep yep so multiple lines multiple orders um you can so ultimately once again uh you can if i pulled up a grid and it had you know three uh three different orders ten different lines across all those orders you can more or less pick and choose which ones you want to update thanks again everyone for joining us be sure to check your email for a qxw survey and check out the quest website for more qxw sessions thank you and have a great rest of the day [Music]