Microsoft Dynamics GP Archives - Page 12 of 12 - FMT

Which ISV tools will work best with my Dynamics GP customization and applications?

The GP functionality of adding the appropriate sales tax and freight to the matched invoice document in POP does not take into consideration adding the value of those additional costs to the fixed asset that is being purchased when using the Fixed Asset module. The steps below will get those costs into the fixed asset module as well into the individual assets that they are associated with. 1. First, create a purchase order with one line and a quantity of more than one for assets, generate a shipment record with the Create Multiple Fixed Assets checkbox checked in the FA PO Additional Information window and post the document. 2. Next, create a matched invoice record against the shipment document and modify the extended cost of each line item with the appropriate amount of tax and or freight and delete the amounts from the Freight and Tax fields at footer of […]

The Dynamics GP Field Service Series is a very useful set of modules for any service organization. These powerful modules benefit service companies of all sizes by integrating essential accounting, distribution, and service processes. Contract Administration Whether you’re an ongoing equipment maintenance company or a provider some type of recurring service, the Contract Administration module provides the means for your organization to enter contract details, track specialized coverage for parts and labor, automate your periodic contract billing, track the revenue recognition process, and renew a customer’s contract with plenty of time to break for lunch! Contract profitability has never been so simple to see as associated revenue and expenses are easily tracked and presented to the end user. Service Call Management The Service Call Management component is one of the most powerful applications within Dynamics GP Field Service Series. With this module, you can track all technician service activities for […]

Previously, in Part 1 we discussed Batch Edit Lists and how they can help you, including preventing batches that get stuck because of a transaction-level error. Sometimes, however, batches stick for an entirely different reason. During posting, the bulk of the processing actually takes place on the SQL database server rather than on your workstation. But at several points in the process, the server needs to communicate back to your GP client to pass the results back and send any instructions for the next steps back to the SQL server. And then in some modules (GL in particular), a final necessary step is sending the report data back to the client to print the posting journals – and if they don’t print, it doesn’t finish posting. It’s during those back-and-forth periods that the process becomes vulnerable. If communication is interrupted, even very briefly, the posting process can fail or only partially complete. […]

Though every module of GP can be set to allow individual transaction posting, most users can benefit from batch posting. A batch is a group of transactions that will be posted all at once.  Once you have a certain quantity of transactions, it just isn’t feasible to post one-by-one anyway, but for consistency of process even single transactions can also be put into and posted in a batch. But if you’re using batches and not using Batch Edit Lists, you’re losing a lot of benefit.  The Batch Edit List can be printed from any module’s Batch Entry window from the printer icon on the top right of the window: The Edit List can be printed to screen or printer and checked for accuracy or error messages before the batch is posted: If you’ve ever had a transaction or batch fail mid-posting, leaving you with a stuck batch that can’t be […]