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.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe 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!
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.

Invalid shipmethod reference key (WSDL)

edited Dec 2, 2019 3:06PM in SuiteCloud / Customization 13 comments

When trying to mark Drop Ship Purchase Orders as shipped via WSDL I'm receiving the following:
"ERROR: INVALID_KEY_OR_REF - Invalid shipmethod reference key 3"

A similar same issue was reported as an issue with the UI here:
https://usergroup.netsuite.com/users/showthread.php?p=103266

The process I am running was originally developed on WSDL v2.6. It ran without issue or change since v2.6. I updated it today to v2009.1 and received the same error.

I've tried forcing the shipstatus via:
oItemFulfillment.shipStatus = ItemFulfillmentShipStatus._shipped

Next I will try forcing the shipmethod based on what is defined on the PO.

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