I am in the midst of our first physical inventory on RMS. I have 13 retail stores running RMS POS and 2 warehouses also running RMS POS...all report to a RMS HQ server. I initially started keying bin locations for items at the store level for the warehouse but then decided to perform a mass edit via sql. What I thought was going to be a simple sql edit to add bin locations to my warehouses during this inventory has appeared to be somewhat puzzling instead. I have run an sql query to update items for two bin locations. I have then gone into store ops mgr for said warehouse and looked up the items and verified that the bin locations showed up correctly in the application both by pulling up individual items and by running a report for each bin to verify the counts were correct for each. I performed this at around 4pm this afternoon. I logged in from home to do some more work on this(I wanted to create a 3rd bin location in the same warehouse.) Before doing so I checked through both store ops manager and through sql on the bins created earlier today and much to my surprise they are no longer there.
The only thing that I can think of that may have caused this is a worksheet. I did have a 250, a 304, and the regular 401s run after I set this up this afternoon. Could this in fact be what blew out my newly created bins?
From what I've read the proper way to create bins is by entering the information into a PO however we are essentially setting up our inventory for each of our warehouses and retail shops. SQL seemed the logical most efficient way to do this but it appears that somehow in synchronizing with HQ my work as been undone.
I see that HQ has a bin location field in the item table however it seems that there would be a store level function to create and maintain bins as each store wouldn't necessarily have the same bin information.
Any help is greatly appreciated.
Sincerely,
Chris
*This post is locked for comments
I have the same question (0)
