General Discussion Topics

[jrbanks]

In versions 6.x and 7.05 we were able to enter non-inventory items into the pricesheets and contract pricing. For the non-inventory items we selected a default warehouse when we set each item up. Then with a small change in the pricing stored procedure we were able to have pricesheet and contract pricing for non-inventory items. We have to have that for our business. I'm shocked that Sage hasn't thought to allow this as a feature. Now in 7.4 I can no longer enter a non-inventory item in price sheets or contract pricing. The easy solution to not having a warehouse was to look up the default warehouse set up with the item and use that whsekey. Below is the change to spimIMSItemGetItemPrice that makes this work. Now we are stuck and will not be upgrading to 7.4 because Sage broke the pricing by not allowing us to enter non-inventory items. This capability is extremely important. We have many non-inventory charges that are specific to a customer such as fuel surcharge, unloader, etc. I went in behind the scenes and entered a non-inventory item directly into the tables and this still works. Now we are looking at either having a source code level change to 7.4 or going to a competing product that allows more pricing flexibility than MAS500. This small change by Sage would make life much easier for the MAS500 community. This should be a feature that is implemented by Sage and not something Sage is trying to stop. We are trying to avoid having to have source code changes to the UI as these get in the way of applying upgrades and service packs.

/* IF Warehouse Key is passed in as 0 (zero), then check for a defualt whse key in item file. */

IF (@_iWhseKey = 0)

BEGIN

/* SELECT @_iWhseKey = NULL Sage Code Commented out by Jim Banks */

/* Get default warehouse key for item to pass in so Non-Inventory item pricing works */

SELECT @_iWhseKey = DfltWhseKey

FROM timItem WITH (NOLOCK)

WHERE ItemKey = @_iItemKey

END

/*I am aware that this could be improved on to set the @_iWhsekey to null if no DfltWhseKey exists, but I didn't need that so I didn't add code for that.*/

[MCarlise]

MAS 500 has never supported pricing for non-inventory items, which is why you had to make your modification. There was a defect in version 6.30 (if not before) and reported to Sage from a customer using version 7.0. At the time it was deemed a medium issue and scheduled to be corrected in the next version, since the actual pricing of the non-inventory item was correct (Standard Item Price) in Sales Order Entry. The fix was released with version 7.30

We do understand your frustration and have been reviewing the enhancement request. I do see that it is on the Ideas site (if initials mean anything, it could have been you that entered it). Since we cannot put every enhancement in the next product version due to resources (as much as we would like to) we review the enhancements and work with Product Management, Support, the forums and contact customers directly to select the enhancements that will help the most customers.

I would recommend anyone who finds this enhancement important to log onto the Ideas site and vote and write comments for this idea.

https://www11.v1ideas.com/SageERP/MAS500/Idea/Deta​il/2456

Thank you,

[jrbanks]

Please look seriously at my solution to the non-inventory item pricing.  It is a good design for basic pricing functionality.  I wouldn't expect Sage to support something as complex as Matrix pricing or price groups with non-inventory items, but at least give us the ability to have different fuel surcharges, pallet charges, fees, etc. on a customer and address basis with the pricesheets also working.  Often times we have fees like pallet, shrink or fuel charges that will go up for some customers and not others on a specific date.  That's why the bare minimum of one warehouse (with the default warehouse in non-inventory items set) would at least allow adequate support that your competition already has.  If you are a design analyst and know anything about business in the real world you would move this to high priority.  

Again, thanks for costing us more money.  Sage is way too costly to do business with.