Stuck working with year end inventory adjustments. The original data I was provided only showed the ON HAND value... As I created my inventory adjustment uploads, I'm now having issues with committed inventory causing adjustments to fail, as all of the on hand inventory is not available. I created a quick report showing bin: on hand vs bin: available.... but where do I get the date to use for effective dating it back to 12/31? Gahhhh

@Kristy Kapsner I do not envy you! From what I can see, this Report should help you (you can change the date at the bottom) "Physical Inventory Worksheet". This link might work: https://system.netsuite.com/app/reporting/reportrunner.nl?cr=241&whence=

Thanks @Lee Hopper! To make life more fun, we have 4 locations and we use Bins. The same item is often located in multiple locations & multiple bins... I have created a report based off of the inventory valuation report, which shows the bin locations and then the associated on hand & available fields. That's a start, I just wish I could as of date it...

Are you importing the IA's via CSV? A quick suggestion that I discovered that might help you: For each line of the CSV, create a unique "External ID" (I suggestion yyyymmddhhmm001, then yyyymmddhhmm002 - as it must be unique within the CSV AND within NS). When you import the CSV, map the field to the External ID and each line will be imported as it's own IA (yes you will have a load of IA's, so if that is an issue for you, don't do it). The advantage is that when one line on the CSV fails, the whole file doesn't fail. You will then be left with a list of lines that are the problem and you can easily (manually) fix those. I wouldn't do this for every import, but for IA's it works for us.

Yes, I did do that... I started with a huge file & then as things failed, moved to smaller & smaller files. It was nice when 200 records went in at one time... I ended up doing a hybrid of bulk files & small files. I only ended up having to do the single transaction files on probably 80 of the 3000 rows, so I felt like that was a win.

If you use the external ID trick, you can import the 3000 rows in one file and only the SKU's with an issue will fail.