A colleague is currently working on some development for Microsoft Dynamics GP and needs to create a journal.

I did some digging around the company database looking for the correct way to get the next Journal Entry number and found a function called glGetNextJournalEntry.

A little work and I was able to supply the following to the developer for him to wrap into a stored procedure to get the Journal Entry number and make sure there were no issues in GP;

/*
Created by Ian Grieve of azurecurve | Ramblings of an IT Professional (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).
*/
DECLARE @l_tINCheckWORKFiles tinyint = 1
DECLARE @I_iSQLSessionID int = USER_SID()
DECLARE @O_tOUTOK tinyint
DECLARE @IO_iOUTJournalEntry int = 1
DECLARE @O_iErrorState int

EXECUTE glGetNextJournalEntry
   @l_tINCheckWORKFiles
   ,@I_iSQLSessionID
   ,@IO_iOUTJournalEntry OUTPUT
   ,@O_tOUTOK OUTPUT
   ,@O_iErrorState OUTPUT

SELECT @IO_iOUTJournalEntry AS 'NJRNLENT', @O_tOUTOK AS 'OUTOK', @O_iErrorState AS 'ERROR'

I did a bit of searching and couldn’t find a specific declaration of the upgrade path from Microsoft Dynamics GP 9 SP3 to Microsoft Dynamics GP 2010 R2.

After reading around and trying to work out the correct path, I decided the likely upgrade path would be GP 9 SP3 > GP 10 SP5 > GP 2010 R2, but I would try GP 9 SP3 > GP 2010 R2 and see if it would work (although I was extremely skeptical) as this would save some time on the upgrades if it was possible. Continue reading “Microsoft Dynamics GP 9 SP3 Upgrade Path To 2010 R2”

In two previous posts I discussed testing Microsoft Dynamics GP 2010’s new Email Remittance functionality; first, by setting up creditors with an internal email address and, then, by transferring the email address from the INET1 field to the new EmailToAddress field.

The other script which I used, and forgot to post, was the one which configures all of the creditors, who are not currently configured for email remittances Continue reading “Enabling Email Cheque Remittances For All Suppliers”

The morning opened with a feeling of déjà vu. A client testing Microsoft Dynamics GP reported that transactions they were posting in an external system were not appearing in GP.

After checking out the other issues I’ve seen recently (Domain Trust issues, Windows Updates restarting MSMQ and timeouts) without luck I expanded the investigation. Continue reading “eConnect Messages Not Posting To GL”

I dealt with an issue yesterday where a manual payment had been entered into Payables Transaction Entry (Transactions » Purchasing » Transaction Entry) but was not showing up in Bank Management’s Reconciliation screen (Transactions » Financial » Bank Management » Reconciliation).

The reason for this is actually quite simple, but I can’t help but feel it is a little bug like. Only payments made directly via Transaction Entry or those produced during the payment run (Transactions » Purchasing » Select Cheques) are posted to Bank Management. If you need to do a manual payment into Payables, or a manual receipt into Receivables, then this needs to be done via CBM Batch Entry (Transactions » Financial » Bank Management » Batches) Continue reading “Missing Transaction In Cashbook Bank Management?”

In this post I discussed changing the password in eConnect 10. However, changes were made to eConnect 11 which means the password is not changed in the same way when using Microsoft Dynamics GP 2010.

eConnect 10 is a COM+ application while eConnect 11 is a Windows Communication Foundation (WCF) service-oriented application. This means the password change is a different process although it must still be done in two places. Continue reading “Changing The eConnect Password In Microsoft Dynamics GP 2010”