Sage 100

For the items with 0 qty on hand and an extension value; use a transaction adjustment.  Add a quantity of 1 at 0 cost then print and update.  Then, enter another transaction adjustment for a quantity of -1 at whatever "orphaned" cost is, then print and update. 

This, apparently, does not work with average cost.  It's what I've always done to clear up stranded FIFO/LIFO/LOT/Serial costs, but Average - ixnay.

What I did do that worked, though, is change the valuation method to standard, then receive one item in to reset the cost, then change it back to average.

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989
------------------------------


Original Message:
Sent: 04-06-2025 11:57
From: Doug Higgs
Subject: Total forked Average costs

For the items with 0 qty on hand and an extension value; use a transaction adjustment.  Add a quantity of 1 at 0 cost then print and update.  Then, enter another transaction adjustment for a quantity of -1 at whatever "orphaned" cost is, then print and update. 

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

Beth I highly recommend using the Balance Quantity and Average cost *utl utility as there could be other problems, and it will make correcting IX transactions where needed.

This, apparently, does not work with average cost.  It's what I've always done to clear up stranded FIFO/LIFO/LOT/Serial costs, but Average - ixnay.

What I did do that worked, though, is change the valuation method to standard, then receive one item in to reset the cost, then change it back to average.

For the items with 0 qty on hand and an extension value; use a transaction adjustment.  Add a quantity of 1 at 0 cost then print and update.  Then, enter another transaction adjustment for a quantity of -1 at whatever "orphaned" cost is, then print and update. 

Ah, @Jane Scanlan - none of these items show up in the utility.

Beth I highly recommend using the Balance Quantity and Average cost *utl utility as there could be other problems, and it will make correcting IX transactions where needed.

This, apparently, does not work with average cost.  It's what I've always done to clear up stranded FIFO/LIFO/LOT/Serial costs, but Average - ixnay.

What I did do that worked, though, is change the valuation method to standard, then receive one item in to reset the cost, then change it back to average.

For the items with 0 qty on hand and an extension value; use a transaction adjustment.  Add a quantity of 1 at 0 cost then print and update.  Then, enter another transaction adjustment for a quantity of -1 at whatever "orphaned" cost is, then print and update. 

Did you run the recalculate IM history?  The ByPeriod tables don't get recalculated if you skip that step.

Ah, @Jane Scanlan - none of these items show up in the utility.

Beth I highly recommend using the Balance Quantity and Average cost *utl utility as there could be other problems, and it will make correcting IX transactions where needed.

This, apparently, does not work with average cost.  It's what I've always done to clear up stranded FIFO/LIFO/LOT/Serial costs, but Average - ixnay.

What I did do that worked, though, is change the valuation method to standard, then receive one item in to reset the cost, then change it back to average.

For the items with 0 qty on hand and an extension value; use a transaction adjustment.  Add a quantity of 1 at 0 cost then print and update.  Then, enter another transaction adjustment for a quantity of -1 at whatever "orphaned" cost is, then print and update. 

@Kevin Moyes - I'm thinking they get recalculated when I change the cost to Std...? 

Did you run the recalculate IM history?  The ByPeriod tables don't get recalculated if you skip that step.

Ah, @Jane Scanlan - none of these items show up in the utility.

Beth I highly recommend using the Balance Quantity and Average cost *utl utility as there could be other problems, and it will make correcting IX transactions where needed.

This, apparently, does not work with average cost.  It's what I've always done to clear up stranded FIFO/LIFO/LOT/Serial costs, but Average - ixnay.

What I did do that worked, though, is change the valuation method to standard, then receive one item in to reset the cost, then change it back to average.

For the items with 0 qty on hand and an extension value; use a transaction adjustment.  Add a quantity of 1 at 0 cost then print and update.  Then, enter another transaction adjustment for a quantity of -1 at whatever "orphaned" cost is, then print and update.