Inter-store transfer problems. Becoming a big problem.

We have HQ and Store Ops here in the office. Our warehouse manager uses Store Ops to transfer out inventory to the various store locations. We've been experiencing some unusual problems. For example, a transfer out request was made here using Store Ops last week but I don't think it went through, yet the HQ transfer reports states that order number is closed. The store we transferred to, their store ops does not even list the that order number in their "transfer in" list even if I filter the status to all and set the dates accordingly. Meanwhile the store ops in the office has that order number listed as closed.

We've experienced this a few times now and I think it is really starting to screw our inventory levels up which could be a big problem. Any ideas? These little bugs here and there with RMS is starting to drive me crazy. =( Thanks for any help.

Reply to
trae78
Loading thread data ...

I feel your pain. Store-to-Store transfers have always been a problem with us. In fact I just posted yesterday about the exact same issue and nobody here seems to know a solution to this issue. Let me at least give you some information that I got from opening a ticket on the issue at Microsoft:

1) Transfers don't go through unless a 401 worksheet for both stores is created and deployed after/during when the worksheet is deployed. This means that you can create a transfer out, force a connection with HQ Client and still the transfer won't go through--if you force a connection using HQ Client at the store level, this is ok but you have to manually create a 401 Worksheet in HQ to go along with it. The 401 Worksheets are automatically created in HQ before all "scheduled" connections, but you have to create your own before manually connecting. 2) You have to be careful that EVERY item in the transfer has the same HQID in both stores and in Headquarters. Each item has a unique ID number at the store level and also a unique HQID number so that Headquarters can identify it. The Microsoft tech I spoke to said that if the HQID's don't match for even 1 item in a transfer then the whole transfer won't go through and no errors will show up to tell you why. This mismatch could happen he told me if items were created at the store level instead of at HQ. If you have HQ--DO NOT CREATE ANY ITEMS IN STORE MANAGER EVER, JUST DISABLE THE NEW BUTTON IN ALL OF THE STORES!! The hardest thing is that you have to use SQL to look at the item table in both of the store databases and the HQ db, and this can be hard to do if your stores are physically far apart. Good luck with this one. 3) We never got to the bottom of why our transfers weren't going through. This was as far as I got before I just gave up and started doing our transfers in HQ instead of at the store level. It's bad but I just haven't had the time to re-addres the issue yet. So, it's still a problem for us and no one in the newsgroup seems to know what's up. I'm surprised that more people haven't had this problem.

If the info above doesn't fix the issue, I'd suggest contacting Microsoft and opening a ticket--then please post up the solution!

thanks, kamal

wrote in message news: snipped-for-privacy@c13g2000cwb.googlegroups.com...

Reply to
Kamal Hood

I have not seen this in the stores I have installed. mte

Reply to
Master T Excellante'

Yes we have seen this as well at many places as well as other problmes with transfers. Here are some issues with possible resolution:

1- If the Transfer number is manually alterred and is bigger than 14 charcters Alpha Numeric (system allows up to 20) then at HQ the system adds 5 chaacter (store Id) followed by a dash - to the store transfer number. Result is that transfer id 12345678901234 from store 1 becomes 00001-12345678901234

If on number from store is bigger this create a programming error and the transfer To Store never receives the transfer. [BUG Reported to Microsoft months ago - NO RESOLUTION]

2- Items Must be created ONLY at HQ [preferably send all items to all stores and make them display or not display at the store level if you don't use them]. When you go to Item Selection screen you can see on top right total number of items. Verify with HQ and all other stores make sure you havethe same number of Items.

If you do not look at the store database and find all items where HQID is blank - Those are the items ceated at store. Recreate those items exactly as they are at store in HQ. Run Workeheet 101 and then worksheet 250 and the item missing will now be at all other stores.

3- ALSO sometime the item exists at HQ but NOT in the dynamic table. [Retail Realm has a fix for this - RR HQ Misc]

4- Make sure that collation setting for all stores are the same and match the collation setting of database at HQ

5- Make sure all your computers have the same date / time settings and are the same.
Reply to
afshin

Thank you much for the additional info. I'll definitely try some of this out (time permitting). Can you explain what you mean by "collation settings" in #4 below?

thanks again, kamal

Reply to
Kamal Hood

Hi Guys, Don't be panic, solution is here for bug till Microsoft fix it. Step1:Goto the database of Store1 (Transfer Out store).Please mark the transfer number which is not reached store2.Goto Store Administrator and then goto New query and then run this Script.

Script1: update Purchaseorder set status = 0 where ponumber = '(Transfer out Number here)'

Script2:update hqmessage set status = 1 where attachmentID = (Select ID from purchaseorder where POnumber = '(Transfer out Number here)')

Now goto Store Manager you can find now status for the Transfer out is showing 'Open'. Goto Issue and click 'Ok' button.Now the status is again changed to closed.

All these steps must be done in the store databse.

Step2: Goto HQ Database issue this below script from HQ Administrator then New Query.

update HQMessage set status = 1 where attachmentID = (select ID from purchaseorder where POnumber = 'Transfer out Number here' and StoreID 'Transfer out Store Number here')

This Script must be issued in the HQ database.

Step3:Now run the Worksheet Style 401: Request data upload for the transfer out Store and manually connect the store to update the changes in the HQ.

Step4:Issue the Worksheet Style 401:Request Dataupload for Transfer In store and manually connect the store to download the transfer.

This will solve your problem of inter-store transfer issue.Till Micorsoft going to find the solution for this bug.

Regards,

Preetham Pinto Certified MRMS Consultant Email: snipped-for-privacy@yahoo.com

Reply to
Preetham Pinto

Thanks for the tips! I will try to use all of this information and do some more research and test it out. I hope MS releases a bug fix for this problem as it seems pretty significant.

Matt

Reply to
trae78

All the tips here are GREAT. I had only one issue when I created the inter-store order and did not set it as "inter-store" type I left it as "Standard", so I think everything works fine as long as you do it right.

Thanks Jamil Rumaileh MiCom Systems, > Thanks for the tips! I will try to use all of this information and do

Reply to
Jamil

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.