My Stuff
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
No Limits. Just possibilities.
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Comments
-
Thanks I'll look into that
-
Thanks that is what we are doing.
-
There are two internal ID's in the error message Asset Values and Asset, I tried both in the saved search and both did not return any results. The error was generated in process stage 1/7 generate depreciation schedule values.
-
I can't uncheck that box, we are on a 4-4-5 calendar. When that box is unchecked it uses the last day of the month when it calculates depreciation so some months the je would be in the wrong period.
-
The last depreciation date was 11/27/2021 the last day of the November accounting period.
-
Yes we tried to run depreciation. It won't even generate the depreciation schedule. The error is When I combined the two depreciation history records into one record for the entire time period the depreciation schedule generates when I run pre-compute depreciation and the depreciation je is created when I run depreciation.
-
We did import them using the csv import. Looks like the issue was that we imported two history records one for 2014-2020 and one for ytd 2021. When we combined them all into one history record we don't get the error.