Month: November 2014

We have been doing some work for a client who is merging two Dynamics GP implementations into one and during testing found that new orders being entered in the newly merged system were showing notes for previous orders.

The reason is that the next number to be used is an entry on the SY01500 (Company Master) table. When the systems were merged, it was done by creating a new company in Dynamics GP, restoring the source systems database over the top and then configuring the setup stored in the System database, such as the Company Setup (Administration area page » Setup » Company » Company).

So we had a database which had notes attached, but a brand new entry in the Company Master (SY01500) table. As we still had the DYNAMICS for the source company database it is a fairly easy job to identify the correct value and update into Company Master.

However, should you want to automate this process, there is a KB article from Microsoft available: Cross-linked or incorrect notes indexes in Microsoft Dynamics GP. The KB article contains a SQL script which is run against the company database and identifies the highest used Notes Index and then resets the Company Master value.

David’s contributions to the Dynamics GP community are one of the main reasons why I started blogging (his posts were so damn useful I decided to offer back whatever I could), so I am delighted to see that he will be continuing to contribute to the community following his departure from Microsoft.

If there are other blogs out there I should have listed, please let me know.

We had a user recently who wanted to quickly see which users had access to which companies and the Security Roles which had been granted. While Dynamics GP does have a number of security reports, they are the standard ones which, while readable in the usual screen or printer output, cannot easily be exported to Excel. However, the client is on Microsoft Dynamics GP 2013 R2 and therefore has access to SmartList Designer.

While I could have done this entirely as a SmartList Designer report, I already had the majority of the SQL needed to generate this as a SQL View which SmartList Designer can access:

Of course, the other reason I used the SQL rather than recreating entirely in SmartList Designer is that I can use this SQL in future, but a SmartList Designer is only usable on the system on which it is created as there is no import/export functionality.

A client on Dynamics GP 2010 R2 has been configuring email for the RM statements recently, but after configuring the system were still receiving an error message:

Path for the E-mail Status Report is Not Setup

When we were assisting to diagnose the problem, we found that while they did have the EmailStmtStatusPath line in their Dex.ini file (as detailed in this KB article), the specified path did not have a trailing slash; as soon as this was done the report started working without issue.

The thirty fifth Feature of the Day is Existing Purchase Order Warning. A new warning message has been added to the Payables Transaction Entry form to prompt the end-user if they attempt to post or save an invoice for a vendor that already has an available Purchase Order in the application:

This new functionality will be disabled by default on upgrades but can be enabled by selecting the Warn if Vendor has Existing Purchase Order checkbox on the Payables Management setup window. For new installs, the functionality will be enabled by default.

It has always been a bit of a debate as to how non-PO invoices should be entered into Dynamics GP; do you use Payables Transaction Entry (Purchasing area page » Transactions » Transaction Entry) or enter a Shipment/Invoice in Receivings Transaction Entry (Purchasing area page » Transactions » Receivings Transaction Entry). Most clients have opted to use Payables Transaction Entry which means this new warning message could be very useful for preventing the entry of payabes invoices when there is an outstanding PO.

The thirty fourth Feature of the Day is Employee Self Service Purchase Requisitions. Dynamics GP 2015 Purchase Requisitions lets a user enter a requisition which ties in with Purchase Order Processing functionality.

As part of the Employee Self Service functionality, navigation is streamlined for the requester to see a requisition status or enter a requisition.

Users are able to quickly see important information right from their Home Page using the Saved, Ready for Purchase, Pending User Action, Rejected Workflow, and Approval tiles:

The thirty third Feature of the Day is Management Reporter Data Integration. In Microsoft Dynamics GP 2015, the user can determine the data that is available to the Microsoft Dynamics Management Reporter DataMart, improving the performance and giving the user control over the data selected.

The user can choose per company (including sample company) if they want the General Ledger data available for reporting.

The user also has the ability to include or exclude Analytical Accounting data for each company:

I am slightly puzzled by this feature of the day as you can simply not import a company into Management Reporter if you don’t want to report on it. While I steer clients away from AA where possible, I am not entirely opposed to it, but I do wonder who would want to report on AA without also wanting to be able to report on the GL.

The thirty second Feature of the Day is Project Employee Expense Entry. Project Accounting employees can create expense reports for any projects to which they are assigned. Employees can also be set up to allow delegates to enter expense reports on their behalf.

Workflow approvals and task assignments are defined for expense reports; workflow actions are executed on the documents from the Expense Entry window or from the Navigation lists.

The thirty first Feature of the Day is Void Intercompany Journal Entries. In Microsoft Dynamics GP 2015, one of the improvements to the intercompany functionality is the ability to view the intercompany distributions of a journal entry from another company.

Having the Intercompany Journal Entry Inquiry window eliminates the need for users to switch between companies to view all originating- and destination-company distributions of an intercompany journal entry. All distributions can be viewed from one company.

The Intercompany Journal Entry Inquiry window is launched from the Journal Entry Inquiry (Financial area page » Inquiry » Journal Entry) using the Intercompany button at the bottom of the window:

I ws recently doing some work for a client, one part of which was to configure Microsoft Dynamics GP to duplicate creditors created in one company into another using the PM Master Trigger functionality in the Professional Services Tools Library (PSTL).

When I tried to enable the trigger I received the following error message:

Dynamics GP Community

Login

Map of Visits

Disclaimer

This blog is a personal project; all opinions are my own and do not necessarily reflect those of my employer.

This blog and its content is provided "AS IS" with no warranty of any kind, either expressed or implied, made in relation to the accuracy, reliability or content of the information herein. The author shall not be liable for any direct, indirect, incidental or consequential damages arising out of the use of, or inability to use, information or opinions expressed in this site and confers no rights.

The links in this blog may lead to third-party Web sites to provide access to third-party resources to assist you in finding other services and/or technical support resources. Information at these sites may change without notice and azurecurve is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.