With the release of Microsoft Dynamics GP 2016 R2 it’s time for a series of “hands on” posts where I go through the installation of all of it’s components and also look at the new functionality introduced; the index for this series can be found here.
In this post, I’m going “hands on” with the sixth of the Microsoft Dynamics GP 2016 R2 Feature of the Day posts, Display Tax Percent for Historical Sales Transactions.
To test this feature, I created a new Tax Detail in Tax Detail Maintenance () for a Sales series Standard Rated UK VAT at 20% and created a related Tax Schedule:
Integration Log Integration: Eriks SO Integration (ID: 8) Action: None Start Time: 23/12/2016 11:05:38 23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0 Opening source query... 23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0 Initializing Source... 23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0 Establishing source record count... 23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0 Beginning integration... 1: Order Insert Failed 5. Seconds DOC 1 ERROR: The Sales Intrastat Entry window is open. - The Sales Intrastat Entry window is open. 23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3 Integration Failed 23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3 Integration Results 1 documents were read from the source query. 1 documents were attempted: 0 integrated without warnings. 0 integrated with warnings. 1 failed to integrate. Finish Time: 23/12/2016 11:05:43 Source Total: 1 Successfully Integrated: 0 Integrated With Warning: 0 Failed: 1 Completion Status: Completed Integration Status: No Documents Succeeded
The Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2016 R2; as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily.
The series index for this series of posts is here
The sixth Feature of the Day is Display Tax Percent for Historical Sales Transactions.
When drilling into the Sales Tax Summary Enquiry, the tax percent used at time of transaction displays instead of the percent that is setup on the tax detail maintenance window.
Microsoft Dynamics GP 2015 R2 saw the introduction of the Purchasing All-In-One Document View, and Dynamics GP 2016 R1 sees the introduction of an Inventory equivalent:
The main features of Inventory All-In-One Document View are:
- View quantity in and quantity out transactions for one item in one window
- Accessible from Item Maintenance, many item inquiry windows, navigation lists and the home page
As with the Sales All-In-One Document View I am prepared to be underwhelmed by this feature of the day based on the Purchasing one introduced in Dynamics GP 2015 R2.
Microsoft Dynamics GP 2015 R2 saw the introduction of the Purchasing All-In-One Document View, and Dynamics GP 2016 R1 sees the introduction of a Sales equivalent:
The main features of Sales All-In-One Document View are:
- View all related sales documents for a single transaction in one window
- Accessible from Customer Maintenance, many sales inquiry windows, navigation lists and the home page
When I heard of the Purchasing version of this in 2015 R2 I was looking forward to it, but found the reality to be a little underwhelming as the window isn’ the friendliest around and is a little clunky. The screenshot above shows that the Sales All-In-One Document View is very similar to the purchasing one so fear I will find this equally clunky.
On this one I am open to someone telling me that there is actually a way to do this out of the box, but I haven’t been able to find it. On a SmartList I was creating, I needed to pull the customer item number and description through to a SOP transaction SmartList, but couldn’t find any table to link with.
As a workaround, I created this view which contains the required link using the CUSTNMBR from SOP10100 (Sales Transaction Work) and the ITEMNMBR from SOP10200 (Sales Transaction Amounts Work):
CREATE VIEW uv_AZRCRV_CustomerItemLink AS /* Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk) This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int). */ SELECT SOP102.SOPNUMBE ,SOP102.SOPTYPE ,SOP102.LNITMSEQ ,SOP101.CUSTNMBR ,SOP102.ITEMNMBR FROM SOP10200 AS SOP102 WITH (NOLOCK) INNER JOIN SOP10100 AS SOP101 WITH (NOLOCK) ON SOP101.SOPNUMBE = SOP102.SOPNUMBE AND SOP101.SOPTYPE = SOP102.SOPTYPE INNER JOIN SOP60300 AS SOP603 WITH (NOLOCK) ON SOP603.CUSTNMBR = SOP101.CUSTNMBR AND SOP603.ITEMNMBR = SOP102.ITEMNMBR GO GRANT SELECT ON uv_AZRCRV_CustomerItemLink TO DYNGRP GO
This one came up from a query a client had about linking a sales order transaction line to the customer item in SmartList Builder. The problem is that to join two tables together, you need all of the key fields to be on the same table; unfortunately, with the SOP Transaction table, this isn’t the case when you want to link to the customer item.
SOP10100 (Sales Transaction Work) holds the CUSTNMBR (Customer Number), but SOP10200 (Sales Transaction Amounts Work) holds the ITEMNMBR (Item Number) which are both needed to link to SOP60300 (Sales Customer Item Cross Reference) which holds the customer item number and description.
While there may be a way to do this in SmartList Builder I’ve not been able to work it out (other than using two calculated fields), it is easier, quicker and more reusable, to create a simple SQL View which returns the relevant information.
In this case the view I created works only for transactions which are at a status of work:
CREATE VIEW uv_PI_SOPCustomerItemLink AS SELECT SOP101.CUSTNMBR ,SOP102.ITEMNMBR ,SOP603.CUSTITEMNMBR ,SOP603.CUSTITEMDESC FROM SOP10200 AS SOP102 INNER JOIN SOP10100 AS SOP101 ON SOP101.SOPNUMBE = SOP102.SOPNUMBE AND SOP101.SOPOwner = SOP102.SOPOwner INNER JOIN SOP60300 AS SOP603 ON SOP603.CUSTNMBR = SOP101.CUSTNMBR AND SOP603.ITEMNMBR = SOP102.ITEMNMBR GO GRANT SELECT ON uv_PI_SOPCustomerItemLink TO DYNGRP GO
The SQL above includes the Grant statement used to add select permissions for the DYNGRP.
Microsoft Dynamics GP 2015 R2 has been released and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.
The twenty fourth Feature of the Day is Customer Credit Limit Visual. In Microsoft Dynamics GP 2015 R2, you have additional options that determine how and when you are notified of a customer who is over the credit limit you set for them.
In Receivables Setup, you can select to display an icon or give a warning message for a customer who is over their limit.
The existing process for an existing credit limit password will still be asked when entering a line item or saving a transaction.
The warning message:
Microsoft Dynamics GP 2015 R2 will soon be released (due late May/early June and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.
The twenty first Feature of the Day is Enable Email on All Sales Order Document Formats. The Print Options for Sales Orders currently only support email for ‘Blank’ document formats. This feature will support email for any document format for all Sales Order documents.
This feature is supported when printing from the Transaction Entry Window, Navigation Lists, and Print Sales Documents window.
While being able to all PO documents is a welcome feature, it is even more welcome on the Sales Order Processing side of things as I have a number of clients who need to produce a proforma invoice when the order is raised and this is typically done using one of the other document formats such as the Despatch Note Blank Form which can be emailed. It is going to be good to be able to configure the SOP Short Order Form as the proforma invoice and be able to use the despatch note for its intended purpose.
I recently implemented Microsoft Dynamics GP for a client who is a UK subsidiary of an American company. This client is a heavy user of the Inventory Control module with over 30,000 items (you’ll see the relevance of this soon).
Shortly after the go-live, users started reporting that windows were opening very slowly; for example, it was taking almost 2 minutes to open the Sales Transaction Entry window. I sat with one of the users and looked at the problem with them; it took a few minutes, due to the slowness, of checking various windows before realising that it was the windows with an Item Number field on them which were slow opening.
I did a quick search online and found a post on Dynamics Code Blocks by Tim Wappat where he had encountered a similar issue which was being caused by the AutoComplete function; this would make sense as by default the AutoComplete will remember 10,000 entries per field.
Which with over 30,000 items and a couple hundred sales orders being processed everyday meant the AutoComplete was quickly building up for each user.
Tim’s solution seemed to be a little more convoluted than I woulr have expected and involved deleting files in the Windows profile. I did a test with one of the users, by deleting the AutoComplete entries via User Preferences () and clicking the AutoComplete button (ringed in red):