This keeps coming up with clients who have multiple locations within the same facility and want to do combined planning, so before we start the customization process I would like to know if anyone else has customized the planning worksheet to consider multiple locations as one during the PW regeneration? This is in a non-warehouse environment, however, there is tracking involved. In this case, it is not feasible to use SKU's as the supply paths are many-to-many. I know how NAV works and have implemented planning successfully at other clients with different environments, but unfortunately the business requirements are different with these clients.
Thanks for your help.
Karen
0
Comments
I had similar requirements a few years ago. The customer had several stores/location close by and they wanted MRP to run as one. So that it suggest transfers from one location to the other. Etc.
I decided to not modify MRP. Instead my idea was to setup SKU and set replenishment method to Transfer from other location. That way I would loop through each location and suggest anything available from other locations. Afterwards I would set the planning resiliency to non on the created req lines. Afterwards update the SKU transfer from location code to a second location and run it for the second locations. Now this does increase the time by a lot. But it's much simpler modification. One new report.
Modifying MRP is a major modification. Another option you could do is this. Nightly copy the database to separate db. Merge the locations into One. There is a download link on how to merge customers/location/vendor. viewtopic.php?f=5&t=15580
Run MRP. It will create the Req lines. Export them from the db and import them into production. Very simple process.
Here is the report I mentioned.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
That is helpful. We have been trying to avoid SKU maintenance for this customer, but it may be unavoidable. We'll just have to automate as much as possible. The copy to another db is probably a good choice for a different customer.
Karen
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n