Sage 100

Import to IM_ItemCost (4.50) the test runs fine but the import throws ""HS Record invalid or Write Failed. The record is not in an editable state."" Any ideas?

Are you adding or editing records? I've seen that message lately on files that will let you edit records via vi but you can't add new records.

Importing to the IM transaction file does work for FIFO/LIFO (sadly not lot). Is this feasable?

@MoiraGoggin - If you search on ""IM_ItemCost"" there is a thread started by Jane Scanlan with a comment by Alnoor with instructions on how to fix that. If someone could tell me how to actually retrieve links to prior SocialCast posts I would appreciate it.

@PhilMcIntosh If you search on links, you will find a post where I described such request.. Unfortunately, I can't narrow it down to under 500 hits so, here it is again. Click on the date time stamp of the original post and the browser wil display the exact URL necessary to copy and past. See example.

Jane's post: https://90minds-com.socialcast.com/messages/14408130

Thanks, @JeffSchwenk

I thought about including that tip in the Sage 300 webinar last week @PhilMcIntosh because I know I've seen it several times. Fortunately, Jeff always responds.

Your kind words are appreciated. I am happy to assist when possible.

Thank you all - the data is alpha for the serial number, yes I'm trying to add records, the IM Transaction file actual has the transaction as well as IM ItemWhse, it just missed the cost file and there wasn't anything in the Activity Log showing an error. I'll test out the suggestion from Alnoor and see if that works. I love this group - what a great response, thank you again.

Well, that didn't work. The providex.dde file already has extn.FormatType$="""". (This is version 4.50) I poked around and see that the Warehouse Code record on this file has extn.FormatType=""CHARNUM"" and the warehouse code I'm importing is alpha. So I tested using a numeric warehouse code and it still failed with the record not in an editable state. it's getting intense now, this is holding up shipping for the customer. I'm tempted to import these serial numbers via a physical and then later run the Item balance utility, the costs are zero so we don't need to worry about that.

This is a different issue because you are trying to add records. I will PM you.

Thank you all - here's the fix I came up with - ran Inventory Balance Utility (File, Run, *Utl), ran Recalc Item History and then imported the serial numbers via physical count. The costs changed (picked up std cost on the physical) but the client was okay with that change.

@AlnoorCassim - I have a similar issue where I need to import new records into lot serial transaction history and AR invoice history lot serial. Please let me know how to get VI to cooperate when you have a chance.