Book Image

Microsoft Dynamics GP 2010 Implementation

By : Victoria Yudin
Book Image

Microsoft Dynamics GP 2010 Implementation

By: Victoria Yudin

Overview of this book

Microsoft Dynamics GP 2010 is a sophisticated Enterprise Resource Planning application with a multitude of features and options. The implementation of Dynamics GP is usually considered to be complex, and can be very confusing for users and consultants. This step-by-step guide will show you how to effectively implement Dynamics GP 2010 with ease.This focused, step-by-step tutorial covers the basics of Microsoft Dynamics GP, from licensing, to design, before moving on to more complex topics such as implementation and setup. You will learn how to install and configure Microsoft Dynamics GP 2010 from start to finish.This book will enable you to master the implementation of Microsoft Dynamics 2010 effectively. This book starts with how to plan and complete a successful Microsoft Dynamics GP 2010 implementation. You will then move on to learning who should be on the implementation team, what important questions should be asked and how to plan your infrastructure for Dynamics GP 2010. Detailed descriptions of all the setup options for the core Dynamics GP modules as well as practical advice on setup will help guide you through the myriad of options available in this powerful application. As you reach the end of the book you will learn how to import your initial data with illustrations and practical examples.
Table of Contents (18 chapters)
Microsoft Dynamics GP 2010 Implementation
Credits
About the Author
About the Reviewer
Preface
General Ledger Account Categories
Microsoft Professional Services: Additional Tools Available
Index

Customers


Similar to vendors, when importing customers into Dynamics GP you can decide to bring in just the minimal information or a lot of details for each customer. This is another example where classes can be used to default most of the details about a customer to save a lot of work during the import. The following example shows a customer import with just a few basic fields of data and one address.

Columns used for import:

Field

Max. Length

Notes

Customer ID

15

This is required and must be unique. It is recommended not to use special characters in IDs. Customer IDs should be all in caps.

Customer Name

65

Required field—this will automatically copy to the Statement Name and the first 15 characters will copy to the Short Name.

Class ID

15

Optional, but recommended. This should be a Class ID that is already created in Dynamics GP.

Primary Address ID

15

Required. Even if there is no address for some customers, import an Address ID to avoid errors. The Ship To, Bill...