megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Don't miss out on our Question of the Week ! You only have until tomorrow, March 12, 2026, 2:00PM ET to comment your answers.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here!
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
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. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.

Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!

FAM Depreciation Error SSS_MISSING_REQD_ARGUMENT:search.lookupFields: Missing a required argument:id

edited Dec 31, 2025 2:52PM in Ask A Guru 4 comments

Hello all - tried looking for this error in the community, but it seems to be dependent on what you're trying to do in FAM. I have also submitted a support case since this is impacting our month-end close: 6595719

But hoping I can get some guidance here.

It may be a coincidence, but our FAM bundle was updated on September 26, 2025 to 25.1.10. However, when we try to depreciate assets, we are getting an error in Step 2 Create Journal Entries: SSS_MISSING_REQD_ARGUMENT: search.lookupFields: Missing a required argument: id.

I tested this in Sandbox, where we are on bundle 25.1.3.c and it worked as expected. Was there a change in the bundle to initiate the error we are getting in Production?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders