[pbrennan]

With 2014.2 Netsuite now allows serialized items to have average cost. Nice, but there can be only one default costing method for items and we want serialized items to continue to have specific cost but create far more non-serialized items than serialized ones, and we create something like a dozen items a day. (Yes I have filed a case/enhancement request about this). In the meantime some % of the time our people don’t change the costing method and create an item incorrectly – *and it cannot be corrected by edit*.

I created a workflow to catch this issue. At present time the only action it can perform is to return a user error, not allowing the item to be saved. I would like to have the workflow set the field value for the Costingmethod to be Specific.

The issue is that in the workflow the Costingmethod field is accessing a list of options that does not match what the UI requires. In the UI the dropdown options are: Average, Specific, Standard. In the Workflow the options are: Average, FIFO, LIFO, Lot Numbered, Serialized, Standard.

Selecting Serialized throws an error. I’ve tried putting in a formula to set the static value to be Specific but the workflow just created an error,

.

Ideas?

Thanks,
This is a cached copy. Click here to see the original post.

[julien.bissonnette]

pbrennan,

for serialized items, you can choose the static value “LIFO” on the workflow screen, once the WF starts on the item record, it will set the “Specific” costing method.

[pbrennan]

Oh thank you that worked!

[Author]

Posts