Sage 100

We are working with Sage (Case:  8008816234) regarding a problem with PM Work Tickets closing items into inventory at the wrong cost.  Client is AVERAGE Unit Cost and has been using WO for 20-years.  Problems now exist with PM, that did not exist prior.  An item that has been manufactured and sold in a single warehouse for 20 years, has gone from an average unit cost of $ 8145 to $9820.  Looking at all the transactions and the details of all the work tickets closed in PM, the cost could have changed a few dollars.  Looking at all transactions from 01/2020 through today, the Min IM Transaction is $8297. and the Max IM Transaction is $8332.  Nothing explains the average cost "rising" to $ 9820.  

They use four decimal precision, it almost looks as if the Closing Transaction is summarizing "all" extended decimal precision from the beginning of time (2014 for this item). and "adding the extend decimal costs" to the average cost calculation with each transaction.  (not confirmed, but looks like this). 

Work Order, it appeared to on occasion produce WZ Neg Qty Adjustments, that accounted for the over distribution timing transactions. PM does not produce any Negative Quantity Adjustments.  When discussed with Sage Software they point us to this document were we need to request an "enhancement request".  

Client Inventory (which is all average); is now a complete mess.  Average Utilities were used and it fixed some items, until the next transaction occurred.  The utility is not an answer to the problem.  

1. Is anyone experiencing similar issues, so we can link cases? 
2. Did you know that now PM is 100% in the hands of Sage Software?  I attempted to get Scanco Involved and Andrew Neal explained Scanco completed their last training class and turned over 100% code to the Sage Development Team.  

​​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

This should be a front burner issue in Sage engineering!  Hard for me to recommend a client switching to PM if this is not an isolated issue.

------------------------------
alan niergarth
Velosio LLC
------------------------------

Hi,
  Just had a client report this issue last week.  In my clients case it is not available at their level. Hopefully you have a more recent install

 

I kept digging and was able to find the original case where this issue was reported and here is the scoop. The issue was reported after the hotfix bundle had already been released. Neither Sage nor Scanco were able to duplicate it on a system that had the hotfix bundle installed. We had the customer install the bundle and confirm for us that the issue went away in their system. This is why I and my colleagues could not find a Scanco defect for this issue. Because the issue went away after installing the hotfix bundle, that became the official fix for the issue. This means that I can conclusively say that you need to go to at least 6.10.4.0  and install that bundle. Best to go higher if possible.

Below is the writeup pointing to the hot fix bundle

Wrong unit cost for Serial items in IM_ItemCost.m4t and IM_LotSerialTransactionHistory.m4t

------------------------------
Bob Osborn
Consultant
ACI Consulting
------------------------------

Closing the loop on this one.  The client needed to move to PU3, to install a poorly documented fix for Production Management that resolved the issue of components at a cost that is "different" than the Item Current Average Cost on Average Cost component usage/completion.  

Be aware:  PM does not handle negative cost tiers.  It does not create a WZ or IZ or BZ the way the other modules do.  If a component that is Average Costing, goes negative (due to timing) at say $ 10.00 a unit, then the completion of that item is at $ 11.00, you will wind up with Zero Quantity on hand and an Extend Unit Cost of $ 1.00.  Sage and Scanco point fingers as to why they did not include a Negative Tier Adjustment.  It is "scheduled" for the March/April time frame.  Unit then, if a client accidently goes negative in PM and subsequent receipt is at a different unit cost, then it has to be "fixed" manually with a series of inventory adjustment transaction.  

Also, our client is now trying to fix all of their average unit costs since they use them for developing new sell prices on final assemblies which can incorporate many sub-assemblies.  They need to adjust out all quantity on hand and receive in again at a corrected average unit cost.  To say this is a mess, is an understatement.  Luckily, this is a client that knows their costing, almost never goes negative (even because of timing issues); and have the staff to make these corrections.  Although they have been a Sage users since 2002, Sage's slow response time, as well as asinine responses, does not sit will with them.  i.e. "change from average unit cost to another cost method", or "sorry, it will need to be a paid enhancement to create PM Negative Cost Tiers".  And the fact that for 6-weeks, they never mentioned it was critical to get a "patch installed" or to move to PU3 where the patch was included.  

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------