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.

New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.

Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.

Save $30 - limited to first 1,000 registrants
Join the NetSuite community to innovate, connect, and discover what’s next.

SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now

NSC | Ensuring Approval Routing for Purchase Orders

May 27, 2025 6:58PM edited Aug 19, 2025 7:52PM in Accounting / ERP

Scenario:

When a user with an Employee Center role enters a Purchase Request, the Employee field is automatically set to the currently logged-in user, and this field is non-editable. This helps maintain the correct approval hierarchy, as routing is tied to the Employee field.

However, when a user logs in with roles other than Employee Center (e.g., Purchasing, Admin), and creates a Purchase Order, the Employee field does not auto-populate. This is due to a current system limitation and is tracked as an Enhancement Request #97543. As a result, users often forget or omit selecting an employee in this field.

Trixie Amora-Oracle|Ask A Guru?️