Join us while we present this overview on best practices in Lawson PAR Management. This webinar includes IC12/IC81 maintenance, managing par levels, removing obsolete items, communication, reporting and MSCM configurations.
Keith Wayland: Good morning everyone. My name is Keith Wayland, managing partner with RPI Consultants. I want to thank you for taking the time to attend this morning’s webinar on Par Management Best Practices. This presentation was originally delivered at the request of the Keystone User Group earlier this year. I’m very excited to be able to assemble the group that delivered it. Mr. Jason Kwasnik, Ms. Stephanie Kowal, Mr. Dan Farruggio to deliver it via webinar. Great presentation today and I am going to hand off to them in just a second.
First I have a couple of housekeeping notes. Number one, this webinar is being recorded and it will take us a week or so to get it edited and loaded up to YouTube and hopefully it will be there for reviewing. Number two, please do take advantage of the fact that our presenters are here and this is interactive and you can ask questions through the go-to webinar chat or questions modules. When we did this in … At the Keystone there was a lot of interaction that was super helpful so please if you have comments, suggestions, questions just throw them out there and without further ado I will hand it off to our presenters.
Jason Kwasnik: Thank you, we are here for pumpkin chunkin … Par management best practices and about us. We were formed in 1999, now we are a total of sixty plus nationwide consultants around the country. We do a lot of presentations and this is of course our team pictures and our … Three of us aboard. Now our agenda. First we are going to be talking about Par setup in Lawson. Then we will be going on to managing Par levels, the integration of Pars with MSCM, reporting, and some best practices. Following the end of that, we will be doing our Q and A. Now the item location versus par location. When you think of par locations … Par locations also besides adding an IC12 builds IC02 ship-to-location for your non-stocks, builds an RQ04 for your internal delivery addresses for your delivery packages and for your stock items. But when you build out your IC81 it builds an IC12 record in the background. Now you have to realize that all modifications are done through IC81 not through IC12. It is just a record that is viewable but not editable.
Stephanie Kowal: As Jason mentioned, IC81 creates that RQ01 automatically so you have to remember as part of your setup and maintenance to go back into that record and add that account unit so you are able to process requisitions. There is also some ongoing maintenance that needs to happen to make sure that you are monitoring this setup from your end users. So when they are adding a vendor source sometimes it could not match the vendor that you are actually … Have a vendor agreement for, a contract for.
It is definitely helpful to build some sort of report to help compare the two and make sure you are staying on track. Another area to take into consideration is the unit of measure that is built and whether or not that is the unit of measure on the agreements so changing your default issue on IC11 can really help with that procure to pay process. There is also some MSCM errors that can hold up your requisition in RQ10, so if you have a request for ten items lets say and one of those items has an error that error will stay in MSCM, it creates an unrealized requisition in RQ10 which you then need to go view and release on your own.
We have worked with some end users that have actually built a process flow that will look for those errors and then automatically release that requisition but in the meantime just make sure you are monitoring those unreleased requisitions and you can pull from the source. It will say that it came from IC83. You can look for all requisitions that are unreleased that come from IC83 and make sure that they are being monitored.
Jason Kwasnik: Stop me if I am wrong but I do believe the newest version of Mobile Supply Chain will create the requisition and release it but create a separate record for the error?
Stephanie Kowal: I haven’t heard that but that would be great news.
Dan Farruggio: Yeah, I haven’t seen that either but that would be awesome if it were.
Jason Kwasnik: I heard that somewhere and just wanted … And not sure what version.
Stephanie Kowal: I’ll have to check that out. There is also unreleased agreements can cause some issues with requests going through as well, so making sure that you are monitoring when changes are made to those agreements, that they are being released. Here is this example of a custom report created with Crystal that was posted to LBI dashboard to help monitor them. It shows how IC81 was setup and who the default PO13 vendor is.
Managing par levels. IC03 is a really really helpful screen to utilize. This is report groups. Most likely you have multiple par locations for one account unit so you can utilize IC03 to build all of those pars in a group and then a lot of the Lawson reports you can run by report group. That will help speed up the process. Here in this table are some canned reports from Lawson and increase screens that can be really helpful to utilize but also do not forget that you can pull directly from the tables in Lawson to get some additional information and build some custom reports. Item location, item source, PO line, IC trans, your shipment details, invoice details, and also IC audit. If you have auditing turned on in IC01 this can be really helpful to build some KPIs, do some troubleshooting if you have had a system issue.
Here we have some examples of some reports that have been created. This is going through par analysis and giving you some recommendations if the par should be upped, decreased, or removed from the par cart. Here is one that is a little bit more complex showing the same similar type of information and my favorite, is this one that was created for item change report. Often times what can happen is … Why isn’t it showing up here? Do we have a freeze with our TV? Often times what can happen is your MMIS team is continually updating records. You could have gotten an order exception from the vendor, unit of measure change, description change, and it is very difficult to communication that to your end users at times. You may have had a process where you were manually keeping track of all of these but your materials team really needs to make sure that those labels are updated in the areas depending on what change has been made.
This report displays any item and it is run by … This one here was run by an actual par and will let them know any time a description either one or two par level bin unit of measure or manufacture detail has been changed. Here it will let them know to update the label. If they recently added it to their par cart or the MIS team may have made a replacement if you had a conversion, it will let you know to add a label and if it has been removed it will let them know to remove the label. Really really excited about this one if you utilize Crystal Reports just reach out to us, I’ll be happy to share it with you.
Dan Farruggio: Now we going to talk a little about managing your MSCM configuration to optimize some of your par management. The first thing you need to know about setting up MSCM is you need to have a Lawson security g