Book Image

Microsoft Dynamics GP 2013 Implementation

By : Victoria Yudin
Book Image

Microsoft Dynamics GP 2013 Implementation

By: Victoria Yudin

Overview of this book

Microsoft Dynamics GP 2013 is a sophisticated Enterprise Resource Planning system with a multitude of features and options. The implementation of Dynamics GP is usually considered to be complex, and can be very confusing for both end users and consultants. Microsoft Dynamics GP 2013 Implementation will show you how to effectively implement Dynamics GP 2013 with ease. "Microsoft Dynamics GP 2013 Implementation" is a focused, step-by-step tutorial covering the basics of Microsoft Dynamics GP, from licensing to design, before moving on to more complex topics such as implementation planning, installation, setup, and training. Learn how to plan and execute your Dynamics GP implementation from start to finish. You will start off by learning how to plan a successful Dynamics GP 2013 implementation. You will then move on to learn the important questions to ask, the key setup details that should be decided upfront, and how to plan the infrastructure. Detailed descriptions of all the setup options for the core Dynamics GP modules as well as practical advice on setup will guide you through the myriad of options available in this powerful application. This book will also cover how to import initial data and how to find out what additional resources and tools are available for Microsoft Dynamics GP. With many detailed and practical examples, "Microsoft Dynamics GP 2013" Implementation will help you plan and complete a successful Microsoft Dynamics GP 2013 implementation.
Table of Contents (18 chapters)
Microsoft Dynamics GP 2013 Implementation
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
General Ledger Account Categories
Index

Vendors


Importing vendors into Dynamics GP can mean bringing in just the minimal information or a lot of details about each vendor. This is a great example of a situation where vendor classes can help enormously, as most of the details about a vendor can be defaulted from the class and there is no need to import them. The following example will show a vendor import with just a few basic fields of data and one address.

Columns used for import:

Field

Max. Length

Notes

Vendor ID

15

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

Vendor Name

64

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

Class ID

10

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

Primary Address ID

15

Even if there is no address for some vendors, import an Address ID to avoid issues during transaction entry. The Purchase...