issueinventorynumber refers to lots/serial numbers
# general
b
issueinventorynumber refers to lots/serial numbers
m
There are no items with lot/serial 22677 in the system 😕
b
there is a difference between the internal id of a lot and the internal id of an item
are you using lots or serialized inventory?
m
Yes.
do you know a good way to search for the incorrect item?
alternatively create an Inventory Numbers Search
m
okay, so that should be the incorrect item. But I still dont see what the problem is with it
b
your inventory count is trying to use that lot/serial when it cant
z
are there any <0 qtys of that item?
SA 79442
m
hmm, i just dont see any problem with that record. Any suggestions of what the problem could be?
b
create an inventory count manually and try getting an item to select that lot/serial
k
I'm guessing you have negative inventory somewhere and postive inventory elsewhere related to that serial/lot number
I normally do a "not equal to 0" inventory number or inventory number/bin on hand search filtered down to the item involved
z
that SA also mentioned it could be caused by a fulfilled/committed item on a closed sales
tho SA seems to be down atm
k
Oh that's another good one I had forgotten about. If you manually assign them to sales orders/transfer orders/etc, you could still have them on hand but not be able to adjust them
same would be true of item fulfillments that are partiallyc ompleted
i.e. picked/packed but not shipped. Thanks for making me remember some bad memories zengs...
lmfao 1
m
this is a mess. Im not even sure where to start fixing that
k
I think there's a NetSuite bundle for lot tracking that you can install to find it if it's a lot numbered and not serialized
your best bet is to start doing transaction searches that have that internal ID in the inventory detail - but that's gonna be a fun one.
m
ill check the suite answer whenever its back up.
After going through the suite answers mentioned earlier, there is a new error.... but for a different item.
Invalid binnumber reference key 1138 for issueinventorynumber <NULL>
The binnumber seems to be correct why would the issue inventory number be null?
z
it's not possible to have a non-number inventory amount right?
that would make something
<NULL>
in a generic sense...
k
Sounds like perhaps need to record less items on your transactions at a time in order to get your inventory issue cleaned up
Not fun, but not sure how else you're gonna get past all your issues
m
Guess so. Main goal is to figure out why this happened to start with so it can be avoided.
k
don't allow people to delete transactions, or back date transactions
a good portion of your problems tend to go away. In general if someone is editing inventory it needs to be -"as of right now"
so if you screw up an inventory transfer - and realize it 5 days later, you don't edit the first inventory transfer, you perform a second one.
to undo it.
m
That's a good point. I'll try to get the no edit/delete rule in effect. Thanks.