This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This post is a public service announcement for those customers and partners using the free customization from Microsoft, Purchase Order Returns Modification (Product ID: 4159) for Microsoft Dynamics GP versions 9.0 and 10.0.
Note: The functionality of this customization has been incorporated into the core Dynamics.dic dictionary for Microsoft Dynamics GP 2010 and so is no longer required.
The customization provides a number of business logic tweaks to improve the functionality of Purchase Order Returns, such as making sure that the returned items use the same Unit of Measure as the received items. Also some of the reports and inquiry windows have been updated to include the return transactions.
So, why I am posting about this customization?
Last week, I had a support case for a site using this customization for an issue with the Purchase Order Received Not Invoiced (RNI) report, where the return transactions were not calculating the extended cost correctly and the Unit of Measure was not shown on the report.
I could not replicate this issue on my installation with the customization installed. Then I remembered that these issues sounded like some of the problems I fixed in the code back in September 2010. I then realised that the site was not running the latest code as I could see data that was missing on a screenshot.
The problem is that with free code like this, there is no mechanism to tell the customers and partners if there has been an update to the code, so all the sites who obtained the older “pre-fix” code will still have that older build.
While I am mentioning this customization, I will also say that in July 2008, I also added functionality that makes sure that the quantity returned against a shipment line is not greater than the quantity original shipped. To enable this check, you will need to add the following line into the Dex.ini file (as explained in the documentation):
So, check if you have the latest version of the code by printing the Purchase Order Analysis report for Received Not Invoiced and check if the return transactions are indicated with an asterisk (*) at the end of the transaction number (as long as the transaction number is not the maximum character length) and that the Unit of Measure is shown.
The above report adds the return transaction to the report but has a number of issues (highlighted): The Unit of Measure is missing. The returned quantity shows in the Qty Invoiced field. The extended cost field is not multiplied by quantity. The amount returned is treated as a negative invoice rather than a return. The Amount Not Invoiced Less Returned on the original transaction has been cleared to zero. The totals are not correct and do not match the original report.
The fixed report now has the following fixes (highlighted): The Unit of Measure is now included. The returned quantity shows in the Qty Returned field. The extended cost is now multiplied by the quantity. The amount returned is shown as the Amount Not Invoiced ($0) less Returned (which is why it is negative). The Amount Not Invoiced Less Returned on the original transaction shows the amount of the transaction less returned ($0), because the returned amount is now on a separate line. Finally, the totals are now correct and match the original report.
The fixed report also includes a couple of additional features (highlighted): Return transactions will have an asterisk (*) added to the transaction number (space permitting). The quantity returned from each receivings transaction is shown on the receivings transaction in the Qty Returned field in parenthesis, this figure is for information only and is not used on the report.
Note: This report is not a modified or alternate report. It is still the original report, however the data in the temporary table used to generate the report has been manipulated by the customization just before the report is printed to add the return transactions into the report and adjust the receivings transactions accordingly.
If you don’t have the latest code, please contact Professional Services (mbsprosv at microsoft dot com) to obtain the update.
This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on http://www.winthropdc.com/blog.