Pretty much every client we have of Microsoft Dynamics GP uses the EFT Payment Register Report; a number of the save the file instead of printing it as the report has been customised to generate the EFT payment file for upload to the bank.
The clients who do this are either those whose installations of Microsoft Dynamics GP predate version 10 when the EFT for Payables Management module was made available to the UK market or they implemented before the EFT File Format was enhanced to allow a CSV output.
While some clients have created or amended a file format since the above, not all of them have been willing to spend the time (or money) to make the change.
As such, when they copy live to test they need to amend the path to which the report is being output, to ensure that a live file is not accidentally overwritten.
To faciliate this for users who have automated the live to test restore I created a script they could build into the process:
/* 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). */ UPDATE SY02200 SET FILEXPNM = 'C:\BACS OUTPUT\BACS.TXT' WHERE PTGRPTNM = 'EFT Payment Register'
The highlighted section is the path name which needs to be changed depending on where the test file is to be output.
One of the really nice new features in Microsoft Dynamics GP 2013 SP2 is the SmartList Designer. This is, to an extent, a cut down replacement of SmartList Builder, which includes much, although not all, of the functionality and is more user friendly.
It also affords the opportunity to all clients to create a report which has long been missing from Microsoft Dynamics GP; a Vendor EFT SmartList which shows the EFT details against the Vendor Remit To Address.
In this post I am going to step through the process of creating this report.
To start, open SmartList () and you will see two new buttons at the left of the toolbar; New and Modify (ringed in red):
I’ve recently been creating an HSBC Standard 18 BACs file format for a client in Microsoft Dynamics GP 2010 R2.
Unfortunately, once I released it to their system, they reported an error with the import where the Creditor’s Cheque Name wasn’t being output on the resulting file.
I did some testing and it turns out to be a bug in the export function of the EFT File Format () window in Microsoft Dynamics GP 2010 R2; I have subsequently tested on GP 2010 SP3 and GP 2013 and the import/export works fine. I realised something odd was going on when I looked at the template in the EFT File Format window ( ) and saw that while the Series was defined as Purchasing in the header, the scrolling window for the Data Field only had Receivables Management tables and fields available to it and not the Payables Management tables and fields I would expect;