Book Image

NetSuite for Consultants

By : Peter Ries
Book Image

NetSuite for Consultants

By: Peter Ries

Overview of this book

NetSuite For Consultants takes a hands-on approach to help ERP and CRM consultants implement NetSuite quickly and efficiently, as well deepen their understanding of its implementation methodology. During the course of this book, you’ll get a clear picture of what NetSuite is, how it works, and how accounts, support, and updates work within its ecosystem. Understanding what a business needs is a critical first step toward completing any software product implementation, so you'll learn how to write business requirements by learning about the various departments, roles, and processes in the client's organization. Once you've developed a solid understanding of NetSuite and your client, you’ll be able to apply your knowledge to configure accounts and test everything with the users. You’ll also learn how to manage both functional and technical issues that arise post-implementation and handle them like a professional. By the end of this book, you'll have gained the necessary skills and knowledge to implement NetSuite for businesses and get things up and running in the shortest possible time.
Table of Contents (27 chapters)
1
Section 1: The NetSuite Ecosystem, including the Main Modules, Platform, and Related Features
5
Section 2: Understanding the Organization You Will Implement the Solution for
11
Section 3: Implementing an Organization in NetSuite
21
Section 4: Managing Gaps and Integrations
Appendix: My Answers to Self-Assessments

Using custom record types to store additional non-standard data

I've had many reasons to create custom records in the past. For instance, a client wants to keep track of warranties on a certain range of products they sell but NetSuite doesn't have a warranty record type. We can create a new type, consisting of fields and forms and subtabs, and assign it specific permissions by role very quickly, all via the NetSuite point-and-click interface.

We can define just the fields we need on that record as well, of course. Using the warranty example again, we might add fields for a customer such as an item, a serial number, and possibly a link to a sale, and a few dates we need to keep track of. If there can be multiple items linked to one warranty, we might want to use the very handy Record is parent feature, to link one field on the parent record type to a field on a related child record type. With this, the users can create one of the parent records, representing the warranty...