Did you like how we did? Rate your experience!

Rated 4.5 out of 5 stars by our customers 561

Video instructions and help with filling out and completing Which Form 2220 Corporations

Instructions and Help about Which Form 2220 Corporations

Hello good afternoon and thank you very much for joining this session which is called help MRP slow is it may or may not be obvious from the session title and the purpose of this presentation is to introduce you to a flow a sort of methodology that you can use whenever you are experiencing MRP runtime issues my name is Roxana Diaconu and I am the the program manager Dynamics AX program manager responsible for master planning and today with me is my colleague Dennis Conrad who is a developer in the team that is developing and maintaining master planning in Dynamics AX before we begin I would like to to mention that we would like to take questions at the end of the session and that there is a mic so you can I would like to ask you to go to the to the mic and ask the question in the microphone so before we begin there is a some things that I would like to to make sure are understood by everybody first of all runtime and performance is not the same thing and this is not a session about MRP performance it's a session about MRP runtime what I'm trying to say is that for example you could have an MRP run and that lasts for let's say five hours you could say the runtime is not good but taking into account the BOM complexity the number of items the run being intercompany or not it could be a run that is performing well also I'd like to mention that this is not a session where we will be presenting let's say sort of benchmarking in the sense of if you have this many items if you this hardware if this is your average bomb level this is how long your MRP should be it's very hard to do that and we're not going to to go there at all first thing that's important to mention and important to acknowledge is that Mr P is a engine that is very generic it's made to support multiple industries and business processes what I mean by that is if you look at the actual code let's get that gets run you may see that there are routines that make might make no sense from your perspective but some parts of it are needed in order to keep the engine versatile and keeping the engine usable in different industries and so on second thing that we should get straight is that when you are implementing the enemy's ax you should think of MRP run time from the early stages of the implementation why is that it's primarily because improving the MRP run time is a trial and error game there is no silver bullet and in troubleshooting the run time reducing the run time is a process that can last up to a month maybe even more so please think about it as early as possible something else also related to the implementation of Dynamics AX implementation project please Fink a please set aside time during the implementation for evaluating and improving the MRP runs so kind of set a goal for your run time how long should it take based on your business processes for example if you know you need to replant twice a day of course it cannot take longer than a couple of hours and after you have set these goals set aside time during the project to track against these goals what I'm saying is probably for a lot of you you know very obvious and you may not want you may wonder why do I keep talking about it but we've had a lot of cases with Microsoft when customers call us I don't know three weeks before go live that the runtime is very long and there's really not much we can do at that point although we we really do try but it is like I said a trial and error game it takes time and basically what I'm also trying to say is that you also they're also asking you to be patient with us when such a case get gets to us and also be patient inside your own organization things take time and last thing before we begin data composition and business needs change and so does your MRP runtime so this flow that we are going to to present today this methodology is most likely not something that you will do once when you implement the eggs and then forget about it it's something that you have to go through every time you upgrade new see you the more items you add to master planning the more warehouses the more bombs you add you will have to go through this process over and over again now that said the agenda for today is basically this flow that I mentioning the steps you have to go through when troubleshooting MRP run time so first we're going to talk about a set of steps that we call out-of-the-box meaning that we're going to start by presenting a set of parameters a set of how to run MRP rules but nothing that has to do with sequel server queries changing the code customizations so just out-of-the-box solutions the methodology would be that you go through each and every step that we're going to present each and parameter you apply this parameter on a test environment which preferably is very close to the production environment in terms of data setup but also volumes of transactions now after you have applied this parameter you should check the effect it had on the MRP runtime if it has a positive effect you should also do a set of functional testing to see that nothing has changed functionally on the environment and then it's a good idea to if if the runtime was improved it's a good idea to apply the parameter.

If you believe that this page should be taken down, please follow our DMCA take down process here.