The serial number is probably committed on another sales order or invoice.  Go to Item Inquiry, tab 7 Cost Detail and see if it is committed. You can also export the SO_InvoiceTierDistribution and SO_SalesOrderTierDistribution and see if the serial number is listed.

Hi BigLouie,

I see that it is shown in 'other committed' on tab 7.  How do I correct this?  We are a small company and our IT person is on vacation until June 1?  

It gets committed when you select it in Invoice Data Entry or Commit in Sales Order if you have that feature turned on. Your first step is to see if you committed it somewhere else which is why I told you to export those to files and see if the serial number had committed on another order.

Unfortunately, I don't know how to run those reports and as I stated previously, our IT person is out.  I believe what happened was that the order was pending shipment and entered into Invoice Data Entry & got cancelled before shipping but was not deleted properly so the SN is stuck.    Will either have to wait for IT to get back or pay Sage Support and have them go in the back door to fix it.  Thanks for your help.

Do you know how to use Excel? Then just PULL the files into Excel.  Go to Date, Get Data, use ODBC and pull the files. If the serial number is not in there then you will need to use DFDM to go into the costing table and clear the field.

Try a rebuild sort files on IM, SO and PO.  One of those has an option about clearing/recalculating items committed (sorry, I don't remember which).  With any luck that should fix it.

DO NOT try this method if you have open invoice batches or serial numbers committed on sales orders. Inventory will not be correctly relieved from inventory.

Good thought BL.   I just checked this out in the knowledgebase and confirmed what you said.  They say that "if lot/serial numbers are NOT committed to any unposted data entry" you can use the rebuild sort files in IM.

The odd part is that the prompt in rebuild sort files says "Do you want to RECALCULATE committed lot/serial quantities?"  That seems to contradict what they say in the KB article?

I'm going to have to test that.  We use Rebuild on IM regularly at a couple clients with repeated issues in committed lot quantities, and haven't had issues with bad transactions being posted.

Did you test to confirm it can issues?

We just ran into this issue, which looks like it was caused by cancelling a shipping invoice after assigning a lot number.  We've not had this happen before, so not sure what the real cause is - but is there a proper way to cancel an invoice with lot numbers assigned so that this issue will not occur?  Thanks.