PAR Management Best Practices

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 t