Kase,
Do you have Price Point A, B or C established? This could be one cause: If within Registers you changed the level from Standard to Price A, B or C. Does the qty tendered for a specific item equate to one of those price points?
What version are you running??
1.3.1009 is the latest version, this could also be where the problem is comming in. There is a massive bug in Version 1.3.1002.HELP!!! Does any one know why the RMS General pricing changed from the original price to some funny pricing!!! It caused huge problems now as the software now is working on the store and customer suppose to pay for the label price but when it scan from POS it show something else? Why and what went wrong???
UNGENTLY NEED HELP.
Regards
Kase
Watch out for the bug in 1.3. It changes the price of the item to the last item you opened.
I've experienced the same with 1.3. I thought I was going crazy. Any work arounds or patches? It does prompt you that changes have occured before saving, but if you've updated the inventory items and not the price, you may not realize the price had changed and saved it. This is a big deal in Michigan where we have scanner laws and are penalized if the price marked on an item is different that what it scans as.
Scott
"Greg Williams" wrote:
The current build for 1.3 is 1.3.1010 You need to contact MS to get the hotfix. Craig
Thank you. We're on 1.3.0203. Does 1.3.1010 hotfix specifically address this issue?
Thank you, Scott
"Craig" wrote:
That build is pre 1.3R so you aren't effected by the bug that came with
1.3.1002 I'm not sure about your issue, but I believe by bringing the product up to 1.3.1010 you will fix your issue since I haven't seen anything like your talking about happening and that's the version we run. If you pay for maintenance you already have access to it. CraigCraig,
I think it is important to know that 1.3R is riddled with numerous issues, and 1.3.1010 is not the most current build, 2.0 is.
My company is running 1.3 flat because of the issues with 1.3R and the rapid rate of hotfixes that were issued because of it. I am sure you are fully aware that if you are 1 store who is a part of a larger operation, you can not run different builds without risking entire database corruption.
Additionally, before pumping 1.3R up, I would make sure the audience is fully aware that if they are using: POs, xfers, AR, holds, recalls, work orders, backorders, ship charges, matrix items, kit items, securities then make them aware of the effects upgrading to 1.3R will have on their system and these daily tasks.
jocelyn,
I had no intention of 'pumping 13.R up' I have experience in using RMS so if I think I can help I speak up. I am no means an expert, but I thought this forum was to try to help each other. The build for 1.3R is 1.3.1010 ,
2.0 has an upgraded database. To me that means it's a different build. I'm sorry if my lack of database experience shows, but at least I try to help. I run 1.3.1010 and I haven't experienced the issue that he was talking about so that's what I said. CraigI hear you and respect completely what you are saying 100%. It is just difficult knowing all of the flaws 1.3R carries with it, that suport will soon die off with it and that you can not purchase 1.3R after the end of this month. Those are some of the major points that kill me.
My last company promptly lost $74,000 in 7 months due to various bugs in
1.3R, and I think I was literally going crazy for a good copule of weeks trying to get those monies back. It is crippling to POs and wicked on the AR.Definitly not good to lose money because of software you're using. It's hard enough to make a living at retail. What are the issues you have with the PO's and AR? The reason I'm asking is that with the licensing change I am investigating whether or not it's worth upgrading to 2.0 or just waiting for
3.0 next year(if that holds true). CraigBeanSmart 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.