Afternoon Everyone.... Was hoping someone could help with an inventory issue. NetSuite is trying to commit more than what I have on hand for a specific item. We are only having this issue with one item. I have zero in stock and it says zero on hand but 2 committed. When I go to reallocate items I can not reassign them to other orders. I can uncheck them and then if I try to check any orders it says none available to commit. However, when I hit save it still has two committed towards orders when there are none in stock.

Is this a lot numbered or serialized item?

@KevinJ of Kansas No. We do not use Lot or Serialized items

special order or dropship?

@Sandii I'm not finding any drop ships or special orders with this item. We do adjust it often though and there are tons of inventory adjustments. So I figured that is what caused it to be off. But I am not sure how to fix it. Even when I am on the inventory item page it says Zero on Hand, Zero Committed. But when I go to Allocate Items it says two are committed and when I go to pick the order they are committed to it's listed on the item fulfillment.

can you remove that line from the SO and re-add it?

The easiest way is close the problem line on the SO and make a new one, I would suspect the commitment problem to go away.

Semi-jynx.

Now you owe me a semi-coke

I would also think that marking it as do not commit and saving should clear the commitment as well... my memory is rusty though

I considered suggesting that - but my expectation would be that they probably want it to commit when they get additional inventory in stock in the future.

then you can change it back 🙂

@KevinJ of Kansas @Sandii @Automatech But the problem is it just commits the 2 to another order. It just keeps jumping from order to order. I went ahead and built enough for fulfill the first order it did it too and it just recommitted his random 2 to another order LOL

oh

Yeah that kinda sounds like a different problem blobthinkingeyes

I even tried to just fulfill it on our test account but it wont actually let me submit the item fulfillment because there are none in the bin. Tried doing a bin putaway and nothing there either

i'd be curious to hear how long you would need to be on with netsuite support to track this one down

I've seen similar issues caused by deletion... maybe.. once upon a time. I think I played around with adjusting the inventory up and down. However, before going that route I'd go through the transaction history (related records) and try to track down when this became an issue.

message has been deleted

What does the line on 75539 look like

message has been deleted

while that may solve your technical issue, you'd just be pushing it (the problem) somewhere else. I suppose if that's fine you could then use a JE to correct any impact. Again, I'd start with trying to figure how how this occurred. 1. So you can prevent it from happening again 2. It may help with identifying a solution

yeah find the transaction that brought it into inventory, and see if bin detail was entered on it

Any suggestions on what I should be looking for to identify when it occurred? I have been looking through the related records. I looked at all item receipts and they had bins (also none for only a QTY of 2). I looked at all item fulfillments and they have bin numbers, I first noticed the issue around the 7th of this month but went back further incase it was going on longer than I knew. I know this was not an issue before Christmas though because I was out of stock of this item back then as well. I also checked all sales orders to make sure none were in a closed status after already being picked as I have seen inventory get really messed up from that before.

@Nichole Broom We had an issue similar to yours about a year ago, except the system kept committing a negative quantity. When I spoke to NS support about it, there is a tool that NetSuite uses in the backend database that runs on some kind of schedule. After a week or two, the problem went away.

@wes_w thats so odd... I have had issues with my inventory being off in bins before but nothing like this.

@Nichole Broom The scary part was that NS Support didn't seem overly bothered that the inventory was behaving badly. Their mysterious 'tool' fixed the problem. It seems like this 'tool' just runs on its own and 'fixes' these types of DB errors.

@wes_w yea that doesnt sound good. Im kind of hoping I am over looking something because if it is the issue you had then I am worried it will happen again and I have finally got this warehouse's inventory issues under control lol. I never seem to get much help from NS Support though. They gave me a temp fix to one issue I had and then I never heard from them again about the issue. Another time they sent me an email to let me know an issue was fixed two weeks after it was fixed, I had already figured out it was fixed on my own.

@Nichole Broom, it sounds like you were pretty thorough with your investigation - so, unfortunately, this might just be a situation where NS has to resolve it (e.g., back-end cleanup like wes_w mentioned). I suppose you could rule out "deletion" as a root cause if you confirm 0 inventory impacting records were deleted in that timeframe (deleted record saved search).

@Automatech good thought. I did look at was in related records but did not look to see if any records were created then deleted. I will check that. We are getting this item back in stock tomorrow so I am hoping once we fulfill all open orders it will resolve issue on its own since inventory is reflecting correctly everywhere else

@Nichole Broom That looks familiar :(

any resolution from NS yet?