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!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
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

SuiteQL - accessing QuantityOnOrder and QuantityAvailable fields with Multiple Locations Enabled

edited Oct 28, 2021 8:12PM in Ask A Guru 6 comments

Hello! I'm trying to dredge data out of NetSuite using SuiteQL, and it's going great except for these two fields -- Quantityonorder and Quantityavailable. I can use both in an Item saved search by way of {quantityonorder} and {quantityavailable}, but in SuiteQL these fields give an error. Here is my query:

    SELECT 
        Item.id,
        Item.itemid,
        Item.displayname,
        Item.cost,
        Item.upccode,
        Item.totalquantityonhand,
        Item.quantityonorder,
        Item.quantityavailable
    FROM 
        Item
    WHERE
        Item.isinactive = 'F'

This works perfectly except for the last two columns, which return the error: "Field 'quantityavailable' for record 'item' was not found. Reason: REMOVED - Field is removed". I believe it is the same issue mentioned at the bottom of this article under the "Multi-Location Inventory" heading, which states that it's the result of having Multiple Locations enabled:

Feel free to ask me anything about Python :)

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 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders