Export the IM_ItemCosting file and see what it shows for that item and serial number.  run the transaction detail report for that item for the date range involved and see what comes up. When an item is first serialized the qty committed field has a value of 1.  If that field is cleared then when posting happens that costing tier is not relieved.  This happened on older versions when rebuilding the inventory sort files.

Unfortunately I have no idea how to get into the 'IM_ItemCosting file'. 

I did run the inventory detail transaction report and it does show a cost for receipt and the same cost for the issue.  I'm just going to have to pay SWK for the correction, but I do appreciate your assistance.

Use Excel and Get Data and pull the file.  This can happen when you enter an invoice which puts a value in the Qty Committed field and the field is cleared before posting.  What version of Sage 100 are you on?

Use Excel and Get Data and pull the file.  This can happen when you enter an invoice which puts a value in the Qty Committed field and the field is cleared before posting.  What version of Sage 100 are you on?

Sage 100 Advanced 2017 (Version 5.40.1.0)

I found this when I went to the Cost Detail tab in Item Maintenance.  I see the SN is entered twice, one is available and one is not.  I checked my receipts registers and I only received that SN once.

It could have been received in, sold and then received in again. If you use a third party to bring in inventory or purchase order transactions it could have been received twice.  If it is gone just adjust out.  Also run a Transaction Detail Report in Inventory for that item for that date and see what you get.

Receipts are done within Sage 100, not 3rd party.  Transaction detail report for that date and item shown only one receipt of that SN.  Also Lot/Serial Transaction Inquiry for that SN only shows 1 receipt and one shipment. No IA's or IT's.  Waiting for for someone above my pay grade to decide if I should just adjust it out or call for help.  Thank you.,

Look at the Excel query data, as I suggested above.  If my theory is correct (bad TierType), normal Sage transactions will only make it worse.

HI Kevin,

Unfortunately, this is as far as I can get:

I tried to search for the SOTAMAS90* file, but I can't find it.  I also tried to search for IM_ItemCosting, but that just gave me a bunch of files ending in .MT4 - none of which were valid for the query - so I don't know how much further tmy superiors are going to want me to go.  I AM NOT an IT person at all (as I'm sure you are aware) so we are either going to call SWK to fix it or adjusts it out.  I do thank you for your time. 

That is Sage 100's ODBC DSN name not a file.

That's odd. The SOTAMAS90 DSN should exist on any workstation running Sage 100. Is the workstation with Excel have Sage 100?

jms329 might be using 64 bit Excel without the 64 bit ODBC driver installed.

64-bit driver would be my guess as well.  DSN list in Excel is filtered by architecture.

I've stayed 32 bit Office for OLE support.