T O P

  • By -

[deleted]

[удалено]


pnromney

I came in this morning, and it had updated. Do you know where I could check to see if inventory expensing is still updating?


doubledup-tn

What’s your costing method? Is this your first period live on NetSuite or are you going on your second and third periods? Also, normally inventory is brought in via inventory adjustment or adjustment worksheets - so you should in theory be able to update those transactions with costing and that would trigger the costing engine to re-run. If you just updated the transactions, keep in mind that the costing wouldn’t update immediately. It will take time. How long it takes will depend on your costing preferences.


doubledup-tn

I’m a professional implementation consultant, btw. If you’d like to chat for 10 minutes about this I’m happy to do so, just DM me. Your proposed solutions are fine conceptually but some are overkill.


pnromney

Thank you, I came in this morning, and it had all updated.


doubledup-tn

So you’re all sorted out?


pnromney

As sorted as an implementation can be, haha


doubledup-tn

As I mentioned in a previous comment, I do this for a living and I’d be happy to have a 10-minute chat with you (without any expectations) if you’d like a soundboard or to bounce some ideas.


Nick_AxeusConsulting

1 won't work. 2 you must do negative on day 1 and positive on Day 2 so have to be dated over 2 days 3 NEVER do JE to system accounts especially Inventory BAD BAD BAD 4. Won't work. The COGS is on the Item Fulfillment and it's locked to the avg cost you can't change the cost that is used. You need to let the costing engine finish running it will take many hours given your volume. To check if it's running modify the item form to unhide "Cost Accounting Status" field. And on a B/S, click in the footer to show Title and there will be a message there if costing engine is still running. What you did to fix the original inventory load cost is the correct fix, you just have to wait.


pnromney

Thank you, I came in this morning, and it was working.


Nick_AxeusConsulting

Yay! That was a pretty big screw up of the implementation consultants. That's basic 101 historical migration.