There is a massive bug in Customer Items.
Did any of the programmers never consider the likelihood that a customer would have the same item number as the Accpac item for a different product??
Given the significant additional cost of 500 series to gain this functionality is it too much to ask that it works properly.
For an example. Out item is ABC123 - 12 Pack of Tissues. In the customer item table we have a customer Bill, who uses the code ABC456 for this product.
When entering an order for this customer we can use ABC456 which will automatically order our ABC123. Perfect??
Now we add a new Accpac item, ABC456 which is 1 pack of Nappies.
Next time we process an order for Bill for ABC456 he gets 1 pack of Nappies because O/E uses the Accpac item NOT the customers item..
This needs to be fixed or don't charge extra for this functionality and point out that it doesn't work properly...
by: Tim M. | over a year ago | Operations Management
Comments
"Massive bug" is a bit hyperbolic, don't you think? A simple workaround is to add a character like "X" to the front of the customer's number. Then edit the forms, and remove the X from the item formula.
Perhaps bug is the wrong word but I don't think it's hyperbolic at all.
There's a significant price jump to get Customer Items and the business logic is simply really poor for customer items.. and it shouldn't be complicated.
We know who the customer is for each order, so it's logical that the first place Accpac should look is for a customer item code.. if there's one there use it..