Book Image

Microsoft Dynamics GP 2013 Cookbook

Book Image

Microsoft Dynamics GP 2013 Cookbook

Overview of this book

Microsoft Dynamics GP is an enterprise resource planning system, essentially an accounting system on steroids, designed for mid-sized organizations. The implementation of Dynamics GP is usually considered to be complex, and people often realize there must be more efficient ways of working with the system. This book will show readers how to improve their use of Dynamics GP and get the most out of this tool quickly and effectively. "Microsoft Dynamics GP 2013 Cookbook" picks up where implementation training leaves off. Whether you are new or experienced you will find useful recipes for improving the way you use and work with Dynamics GP. The clear recipe steps and screenshots make implementing these solutions easy for users of any level and will be sure to improve your efficiency with the Dynamics GP 2013 system. The book starts with recipes designed to enhance the usefulness of Microsoft Dynamics GP by personalizing the look and feel of the application. Most of the recipes are designed to give tips for a typical installation of Dynamics GP, including core financials and distribution modules. The book then moves through recipes that include automating Dynamics GP to allow users or administrators to focus on value adding tasks, harnessing the power of SmartLists to leverage both simplicity and power, connecting Dynamics GP to Microsoft Office 2013, exposing hidden features in Dynamics GP, and much more! Through the final chapters, the book covers system maintenance and extending Dynamics GP with the Support Debugging Tool and Professional Services Tools Library.
Table of Contents (22 chapters)
Microsoft Dynamics GP 2013 Cookbook
Credits
About the Author
Acknowledgment
About the Author
Acknowledgment
About the Reviewers
www.PacktPub.com
Preface
Index

Reducing posting steps with better printing control


When posting a transaction in Dynamics GP, a series of posting reports print by default. Typically there is a posting report, with full posting details, a distribution summary report, a distribution detail report and, in many cases, a checkbook report.

Reports are often set to ask for the type of output (printer, screen, or file) each time. If this setting is turned on, each report will open a window allowing the user to change the report destination when the report is run. This significantly increases the amount of time it takes to simply start the printing process because the user has to make a choice each time. Additionally, reports set to print to a printer will open a window allowing users to set the number of copies or limit printing to certain pages.

This means that it's not uncommon to have eight windows open and four reports print every time a user posts. Even worse, the summary and detail distribution reports are subsets of the...