You’re offline. This is a read only version of the page.
We are working with GP 2013 with manufacturing and with multi-bins implemented.
Since initial implementation of GP in 2008 the company has used numerous sites as virtual warehouses in a single physical buillding location. Now we desire to change to a single site for the entire physical building to allow us to implement MRP.
We have identified the below tables with a view to update the various site and site-bin names. Additionally we want to delete the sites and site-bins we will not being using going forward.
We want to leave the historical data intact.
I would appreciate any ideas to accomplish this and also any pitfalls to be aware of.
Thank you in advance
Randy
IV00101 --item master
IV00102 --item quantity item-site-bin master
IV00111 --Site additional defaults
IV00112 --Non-Serialized item-site-bin
IV00117 --Bin priorities
IV00200 --Serialized item-site-bin
IV00300 --Lot tracking item-site-bin
IV40700 --Site master
IV40701 --Site-bin master
*This post is locked for comments
Our practice of using multiple sites and transferring between has resulted in our IV30300 table being inundated with entries that would have to be deleted. Plus my finance and material planners are not crazy about the idea of deleting.
Looking closer at the IV30300 table I couldn't see any constraints or primary keys tied to the two site fields. Began to wonder if using SQL to update the site fields in the IV30300 table to the new scheme and then ran the Site Combiner would result in a successful outcome.
I tested just updating a few records through SQL and it appeared fine. Haven't yet tried a test scenario to change a specific site and then run combiner.
What are your thoughts about such a scenario?
Thank you again
Correct. Failure to remove the history records results in Primary Key violation.
In my case, since the two "virtual" sites were really 1 physical site the bin setups were the same - no duplicates were generated.
Tim
Thank you Tim. I read the other post.
If I understand correctly, before combining sites I need to filter IV30300 for any transactions between the site(s) that I wish to combine. Then delete those transactions from IV30300 before running the combine.
This does seem like a smooth way to go. However I am concerned with the duplicate multi-bins that would result in IV40701, Site-Bin master and in history. Suppose history would be fine but there will be dups in IV40701 that would need to be deleted.
Since we want to restructure our bins as well, possibly if updates to bin names are run with old sites before combining sites that would take care of issues.
Your thoughts Tim?
Thanks again
I used the Site Combiner in Professional Services Toolkit (PSTL) to accomplish this (merging sites). There was on small problem that wasn't addressed in the guidelines - you have to remove history transactions that move Inventory between the two sites being merged. There is another thread here on the forum about it:
community.dynamics.com/.../205737
There was no loss of history. I tested (a lot) in a test company before I executed in production.
Tim Foster
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,104
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (