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

Documenting customization requirements and solutions

When we work with scripts in clients' accounts, we usually need to create a couple of types of documentation to support our work. It's not enough to just have automations running in the account – users need to know how they affect their work, and administrators need to know how to maintain/change them in the future. The first document we typically provide to clients is a requirement and design document. This should be a very plain English document which any user can make sense of. This isn't the place for a lot of technical terms or code samples or even what we sometimes call pseudo-code. Instead, I like these documents to have at least three sections:

  • A clear statement of the problem we're trying to solve with the customization.
  • A detailed functional description of the client's requirements for it.
  • A good understandable description of the solution we'll create to meet the requirements...