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

Collecting information about and documenting integrations

Some NetSuite clients just need to integrate with one other application, for some relatively small part of their business. We always start to help these clients by searching the SuiteApp Marketplace to find out whether the other business already has a package for accomplishing this. With things such as taxes and warehouse integrations, as well as invoicing and payment handling, there are usually multiple options. But when we find that no app exists for their use case or the client needs to define and create integrations with multiple endpoints, we must take a couple of additional steps to make sure the work is planned and executed properly.

First, we must build a document listing all of the endpoints and their most important details. I usually do this in a spreadsheet since this allows me to easily build a table of information and I can extend the listing any time I need. We always want to be able to refer to each endpoint...