Sage 100

Client on 4.40 PU5. They have qtys on lot items (left over after production entries) that are out past the number of decimal places. I.E. they are setup for 3 decimal places and they will have a qty hanging out there of .0005 which shows as .001. SOOOO - the new physical count is not clearing those out, even though it shows a variance on the register. I also tried importing into Invt Adjustments, but same thing - it lops off that extra decimal place and assumes 0. And you can't import directly into the ItemCost file - at least not into the Qty field. Sage created a case for it, but RELUCTANTLY. They wanted to know why we couldn't just change the number of decimal places, after arguing with me as to how it could never happen in the first place. Actually, I wonder if she even created a case. ANYWAY - does anyone have any suggestions as to how the client can clear these little qtys?

DFDM is my first thought.

Woud like to keep away from that - too many and it's constantly happening

Crazy as this sounds, we always used BarCode module to import into the Lot Field. My recollection is that the hard coded imports included a Lot Field. You just have to format the input file accordingly. Layout for Physical Counts looks like this: Transaction Type (hardcode - ""8"") 1, 1 Warehouse Number 2, 3 Item Code 5, 30 Quantity (########.0000) 35, 13 Lot/Serial Number (if applicable) 48, 15

See the thing is - the physical count register looks like it is going to do the adjustment. It shows a variance of .001. But it doesn't end up posting anything. So I'm not sure that importing into it will change that, because I would import in the same number that is already in the file.

how about a different type of transaction via import like a sale?

So do you know why it is constantly happening? Is one of the modules not rounding properly which is creating the 4th decimal position? Unfortunately, it seems like there are two issues here.

It's production, like when the qty in a raw material is .377 and the qty produced is .5. And it has been happening forever - client just recently upgraded from 4.20 to 4.40 and the only problem is that the physical count register is no longer clearing out those little amounts. Used to work just fine.

FORGET IT. How annoying - gave the client this option - do physical count, change decimal places to 4 from 3 right before updating register, change it back after update. Client had a fit over it. But apparently had a fit before actually trying it - tried it and said that's a FINE FINE workaround for now. So just forget the whole thing. *SIGH*

beautiful

I've had situations like that. Gave the client a write-up on how they could clear a file they needed to clear on a periodic basis. Yet they would always email us to do it for them. Finally sat down with them and had them try it. She said, ""That's it?"" when actually doing it herself. Now they do this process themselves instead of always asking us to do it.