Creditor Contains EFT Bank Details For A Different Creditor

Microsoft Dynamics GPI have just recently finished the implementation of a new client on Microsoft Dynamics GP. While I was there during the go-live week, one of the finance team reported a problem whereby they opened the creditor (vendor to the American readers) record the EFT Bank details for a different creditor were displayed.

I immediately started investigating to see if I could find out why this was happening as it is not something I have seen before and was rather concerning.

Ten minutes later while I was still poking around the database, the user came back with further information. When they were originally entering the creditors whey had entered one of them under the wrong creditor ID (they were using the ones from their old system).

After entering the creditor and EFT details they had realised their mistake and deleted the creditor; they then entered the correct details, but this creditor did not have EFT details on record so the EFT details window wasn’t opened at that time.

A few days later, once the creditor supplied details they went to enter them and found the details from the original incorrectly entered creditor and reported the problem. It was only ten minutes later they remembered about the incorrect entry.

I have been able to reproduce this error with 100% success on several versions of Microsoft Dynamics GP. It appears that Dynamics GP is not deleting the creditor bank details when the creditor, or the address, are deleted.

Error Printing Batch Of Cheque Remittances

Microsoft Dynamics GPI recently assisted a client with an upgrade of Microsoft Dynamics GP 10 to GP 2013 R2. As part of the upgrade we assisted the client to create some Word Template versions of sales invoice, purchase order, and cheque remittance (or check remittance to the American readers).

Everything appeared fine during development and initial testing. Fine that is until we tried producing a batch of twenty remittances which produced the following two error messages:

Microsoft Word - The file Check Remittance~2 cannot be opened because there are problems with the contents.Microsoft Word – The file Check Remittance~2 cannot be opened because there are problems with the contents.

Continue reading

MS Connect Suggestion Sunday: Fix Print Icon In Print Payables Checks

Microsoft Dynamics GPMark Polino posted a suggestion to the MS Connect site asking for the print icons on Print Cheques (or Print Checks for our American readers). The details of the suggestion are:

When you select a batch of checks to print in the Print Payables Checks window GP 2013 R2 shows 2 icons labeled “Print” in the center of the Action Pane. The left icon has a printer with a document behind it that resembles a report. The right icon displays a plain printer. It’s very confusing to users to decided which icon to pick to print checks.

The left most icon, the one with an apparent report behind it actually prints checks. The right icon, the one with a plain printer, prints reports. This is not intuitive at all. Neither the icon nor the label indicate which print icon does which. Since the primary function of this window is to print checks it needs to be very obvious to users what to do.

Please clarify both the icon and label to make this easier to use.

This suggestion can be found here; please take a look and add your vote.

MS Connect Suggestion Sunday: AP Invoice Approval Workflow

Microsoft Dynamics GPIt seems that quite a few of the MS Connect suggestions I am selecting to post about are in the area of Workflow 2.0 which was a fantastic addition to Microsoft Dynamics GP; I’ve expressed before my delight at the retirement of Business Portal and the original Workflow modules. Workflow 2.0 was introduced in Dynamics GP 2013 R2, was then further enhanced in GP 2015 and the roadmap shows further enhancements will be coming in future.

However, there is always room for user suggestions for improvements to functionality which is where the MS Connect site comes in. Jared Hall has logged a suggestion that approval workflow be added for individual Payables Management invoices; this is a feature that I know several of my clients would be interested in this function as invoices need to be approved by different budget holders and it isn’t always easy to separate these invoices into batches by budget holder.

The suggestion can be found here where you can also cast your vote.

If you have an MS Connect suggestions you want publicised, contact me with details.

MDGP 2015 Feature of the Day: Existing Purchase Order Warning

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.

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 roles targeted by this feature are:

  • Payables Clerk, Accounting Manager
  • Purchasing Agent

Click to show/hide MDGP 2015 Feature of the Day Series Index

Professional Services Tools Library – DBMS Error 4920

Microsoft Dynamics GPI 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:

Microsoft Dynamics GP - The stored procedure failed to enable taVendorInsert returned the following results: DBMS: 4920, Microsoft Dynamics GP: 0Microsoft Dynamics GP – The stored procedure failed to enable taVendorInsert returned the following results: DBMS: 4920, Microsoft Dynamics GP: 0

Continue reading

MDGP 2015 Feature of the Day: Edit Email on Historical Transactions

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.

The thirtieth Feature of the Day is Edit Email on Historical Transactions. In Microsoft Dynamics GP 2015 when you want to send an e-mail for a historical document you can add additional e-mail addresses and choose which e-mail addresses you wish to send to.

On Navigation Lists, you can mark a group of historical documents and e-mail them to a different e-mail address. So, if a customer wants a copy of a number of invoices, you can mark them, and e-mail them to the specific address.

Edit E-mail Detail is available for Receivables statements, Sales Order transactions, Purchase Orders and Payables remittances:

Reprint Statements

Continue reading

MDGP 2015 Feature of the Day: Payment Terms – Discount Date Calculation

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.

The twenty second Feature of the Day is Payment Terms – Discount Date Calculation. With the changes for the transaction due date, we’ve extended the options for the discount date also in Microsoft Dynamics GP2015.

Now you have the same calculation options for discount date that you do for transaction due date. You choose among calculation options like annual, next month or month/date and being able to add days, months, or years to the calculation gives you greater flexibility when setting up your payment terms:

Payment Terms Setup

Continue reading

MDGP 2015 Feature of the Day: Payment Terms – Transaction Calculation

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.

The twenty first Feature of the Day is Payment Terms – Transaction Calculation. In Microsoft Dynamics GP 2015 you now have greater flexibility to configure payment terms for the transaction due date.

A new selection was added to calculate the transaction due date from the transaction date or from the discount date and additional calculation options like annual or month/date and being able to add days or months to the calculation gives you greater flexibility when setting up your payment terms:

Payment Terms Setup

Continue reading

MDGP 2015 Feature of the Day: Vendor Approval

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.

The fourth Feature of the Day is Vendor Approval. This feature is an enhancement to the new Workflow 2.0 module introduced in Microsoft Dynamics GP 2013 R2 which allows users to control the setup and maintenance of vendors.

Vendor Approval allows users to create mandatory workflow processes around the setup and maintenance of vendors. These mandatory processes need to be completed before transactions can be posted. The workflow processes are defined in Workflow Maintenance (Administration area page >> Setup >> Company >> Workflow >> Workflow Maintenance):

Workflow Maintenance

The workflow status appears on the window and actions can be taken directly from those windows, from an email or from a Navigation List.

I want to see more details about this feature as I am very much hoping that the workflow has been extended to include the EFT Bank details.

The new Workflow 2.0 is far, far simpler and easier to implement and use.

The roles targeted by this feature are:

  • All

Click to show/hide MDGP 2015 Feature of the Day Series Index