You can write more sophisticated code that uses reflection to manipulate the item’s properties without knowing the type. As you can see in line 77, you need to set the item type of the item you’re fixing. My code simply reads the existing item using its internal ID. So let me share with you the fix which I employed. They said that that request is currently being evaluated and at this time they intend to add that feature to some future release of NetSuite, but there is no target date for that change. There are related transactions that include cost, and there is no mechanism to go back and correct erroneous cost on items that have already been invoiced.įor the record, I contacted NetSuite and asked if it would be possible for them to change the costing methods on items that have never been sold out of inventory.
![netsuite turn off inventory status netsuite turn off inventory status](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/img/InventoryManagement/StatusStateList.png)
And for parts that have been sold out of inventory, it’s a problem. And when you originally configure NetSuite, you can set the default which gets assigned to new parts as they are created.īut what if you get it wrong? It seems like it shouldn’t matter on parts that have never been sold out of inventory. Here are some examples: “First in First Out”, FIFO, “Last In First Out” LIFO, Average, By Lot, By Serial Number, etc. What is “Costing Method”? Its the way costs are assigned to inventory.
![netsuite turn off inventory status netsuite turn off inventory status](https://firebearstudio.com/blog/wp-content/uploads/2020/09/Forms.jpg)
Once an item is created, the costing method is set and cannot be changed. One of the problems we’ve faced after implementing NetSuite is having to fix an incorrect Costing Method on an item record.