Hi Tbarna

As a general rule there is no 'undo' button

But, via the back end you can undo the bank rec.

I strongly recommend that you first try this out in a test environment. Or if you do not feel comfortable, this would be a good time to enlist the services of your Microsoft GP partner.

1) Determine the Recon# of the reconciliation to be un-done (replace XXXXX with the appropriate Checkbook ID):

select * from CM20500 where CHEKBKID = ‘XXXXX’

order by RECONUM

2) Change the transactions in that recon to not reconciled (replace the ##.##### with the exact RECONUM determined in #1 above):

update CM20200 set Recond = 0 where RECONUM = ‘##.#####’

update CM20200 set ClrdAmt = 0 where RECONUM = ‘##.#####’

update CM20200 set clearedate = 0000-00-00 where RECONUM = ‘##.#####’

update CM20200 set RECONUM = 0 where RECONUM = ‘##.#####’

3) Remove the Recon from history (replace the ##.##### with the exact RECONUM determined in #1 above):

delete CM20500 where RECONUM = ‘##.#####’

4) Update the Checkbook Master with the revised Last Recon Date and Last Recon Amount (Replace MM with the desired Month and DD with desired day. Replace #######.## with the appropriate amount – no commas. Replace XXXXX with the appropriate Checkbook ID):

update CM00100 set Last_Reconciled_Date = ‘2010-MM-DD 00:00:00.000′ where CHEKBKID = ‘XXXXX’

update CM00100 set Last_Reconciled_BALANCE = ‘#######.##’ where CHEKBKID = ‘XXXXX’

I received the following from GP Tech Support today pertaining to both the web client and the traditional workstation client, including GP 2018.  How can Microsoft not be working to fix this for GP?

Thank you for your time on the phone today! We discussed the issue you are having after disabling TLS 1.0, and I informed you that GP is not a part of the movement to use a more modern security protocol. If you disable TLS 1.0 in a GP environment - any existing version - the GP login will not work. This is written up and is pending with development, but you cannot currently disable TLS 1.0 and still log into GP.

I currently have GP 2015R2 and web service in my company. If I disable TLS 1.0 on the server(Windows 2012) that has the web service installed, the web service breaks and users can't access it. If I can disable TLS 1.0 in GP 2016 R2 then I'll probably look into upgrading. Thanks.

Thank you so much Derek.  I appreciate everyone's feedback.  

Is it also possible that the client needs to allow/trust a certain web address (URL)?  I have been trying to determine what the connect URL is so that I can give that to him.  Maybe when you come back with news that this issue is fixed you can also give me the URL.

Thanks for everything.

Sheila

My client is running GP 2013.  They want to be able to use Connect on the Home Page to follow when Payroll Tax Updates become available.  When Connect is shown on the home page (all computers in the office) we get an error that the navigation was canceled.  If I click on Refresh Page I get the following message:

Hi - No, I’m sorry. The issue still exists for me but if you figure it out, please let me know how you did it! Thanks!

Hi there. We have a Smartlist under Purchasing that shows us all of our unapplied documents like payments, credit memos, etc. It has suddenly stopped showing unapplied payments and I can't even find them under a regular Payables transactions smartlist even when I run a query search for the specific vendor. I can see credit memos and misc documents, but not payments. I know they should be there as I have to reconcile them yet, but I'm not sure what happened..they seem to have disappeared from the Smartlist universe. I was able to pull the list from SQL by using "select * from P20000 where DOCTYPE = 6" but I do not want to go into SQL every time I need to reconcile our unapplied. 

Any ideas on what to do or what happened?

I don't really think you are paying attention to what I wrote or are simply reading over it.

As I said before, there isn't a node to do the apply. You need to extend the stored procedure I previously indicated to do the apply yourself and use the User Defined fields in the node to pass in the invoices you are going to apply against.

M.O., you will need to prove to me that this is an issue. I have been deploying web client for years now - probably one of the first in doing so and have not experienced any issues. I also know an entire organization built around hosting GP in the cloud and using nothing but the web client to deliver the UI to end-users.

Maybe one day you can explain to us all what issue you are having and not just point to an issue you had that none of us here can recreate.

From your earlier responses I understand that we can use taPMManualCheck node to import the payments (payment entry types: 0=Check; 1=Cash; 2=Credit card).

And later use the taPMManualCheck_POST SQL Server stored procedure to create the apply record(s) for the payment. (Infact, today we use Precipio APApply library to do this).

I just wanted to confirm if taPMManualCheck_POST SQL Server stored procedure can also be used to create the apply records for the payment which are made using CREDITS.

Since I do not see a payment entry type as Credits (we see only payment entry types: 0=Check; 1=Cash; 2=Credit card) for taPMManualCheck I am unsure if this can be done.

Apologies if my understanding is wrong and if I am putting too many questions..!

Thank you Leslie for your response..!

I'm currently importing the Bulk Gl from Excel using Add-in, it is working fine in my local environment.

but i'm facing a issue in Client's place.

Can any one please help me... Thanks in Advance :)

Herewith i attached the xml Schema for your reference which is created in my local machine

<?xml version="1.0" encoding="UTF-8"?>
<eConnect xmlns:xsd="www.w3.org/.../XMLSchema" xmlns:xsi="www.w3.org/.../XMLSchema-instance">
<GLTransactionType>
<eConnectProcessInfo xsi:nil="true"/>
<taRequesterTrxDisabler_Items xsi:nil="true"/>
<taGLTransactionLineInsert_Items>
<taGLTransactionLineInsert>
<BACHNUMB>PMCHK</BACHNUMB>
<JRNENTRY>31949</JRNENTRY>
<SQNCLINE>16384</SQNCLINE>
<CRDTAMNT>0.00</CRDTAMNT>
<DEBITAMT>555</DEBITAMT>
<ACTNUMST>000-1102-00</ACTNUMST>
<DOCDATE>12/29/2018 12:00:00 AM</DOCDATE>
</taGLTransactionLineInsert>
<taGLTransactionLineInsert>
<BACHNUMB>PMCHK</BACHNUMB>
<JRNENTRY>31949</JRNENTRY>
<SQNCLINE>32768</SQNCLINE>
<CRDTAMNT>200</CRDTAMNT>
<DEBITAMT>0.00</DEBITAMT>
<ACTNUMST>000-1106-00</ACTNUMST>
<DOCDATE>12/29/2018 12:00:00 AM</DOCDATE>
</taGLTransactionLineInsert>
<taGLTransactionLineInsert>
<BACHNUMB>PMCHK</BACHNUMB>
<JRNENTRY>31949</JRNENTRY>
<SQNCLINE>49152</SQNCLINE>
<CRDTAMNT>0.00</CRDTAMNT>
<DEBITAMT>200</DEBITAMT>
<ACTNUMST>000-1105-00</ACTNUMST>
<DOCDATE>12/29/2018 12:00:00 AM</DOCDATE>
</taGLTransactionLineInsert>
<taGLTransactionLineInsert>
<BACHNUMB>PMCHK</BACHNUMB>
<JRNENTRY>31949</JRNENTRY>
<SQNCLINE>65536</SQNCLINE>
<CRDTAMNT>555</CRDTAMNT>
<DEBITAMT>0.00</DEBITAMT>
<ACTNUMST>000-1120-00</ACTNUMST>
<DOCDATE>12/29/2018 12:00:00 AM</DOCDATE>
</taGLTransactionLineInsert>
</taGLTransactionLineInsert_Items>
<taAnalyticsDistribution_Items>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1102-00</ACTNUMST>
<aaTrxDimCode>EMP001 </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1102-00</ACTNUMST>
<aaTrxDimCode>COST001 </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1102-00</ACTNUMST>
<aaTrxDimCode>LOC </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1102-00</ACTNUMST>
<aaTrxDimCodeNum>45</aaTrxDimCodeNum>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1102-00</ACTNUMST>
<aaTrxDimCodeNum>55</aaTrxDimCodeNum>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1106-00</ACTNUMST>
<aaTrxDimCode>EMP001 </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1106-00</ACTNUMST>
<aaTrxDimCode>COST001 </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1106-00</ACTNUMST>
<aaTrxDimCode>LOC </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1106-00</ACTNUMST>
<aaTrxDimCodeNum>46</aaTrxDimCodeNum>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1106-00</ACTNUMST>
<aaTrxDimCodeNum>56</aaTrxDimCodeNum>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDimCode>EMP001 </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDimCode>COST001 </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDimCode>LOC </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDimCodeNum>47</aaTrxDimCodeNum>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>200</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDimCodeNum>57</aaTrxDimCodeNum>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1120-00</ACTNUMST>
<aaTrxDimCode>EMP001 </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1120-00</ACTNUMST>
<aaTrxDimCode>COST001 </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1120-00</ACTNUMST>
<aaTrxDimCode>LOC </aaTrxDimCode>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1120-00</ACTNUMST>
<aaTrxDimCodeNum>48</aaTrxDimCodeNum>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31949</DOCNMBR>
<AMOUNT>555</AMOUNT>
<ACTNUMST>000-1120-00</ACTNUMST>
<aaTrxDimCodeNum>58</aaTrxDimCodeNum>
</taAnalyticsDistribution>
</taAnalyticsDistribution_Items>
<taGLTransactionHeaderInsert>
<BACHNUMB>PMCHK</BACHNUMB>
<JRNENTRY>31949</JRNENTRY>
<REFRENCE>JL</REFRENCE>
<TRXDATE>12/29/2018 12:00:00 AM</TRXDATE>
<TRXTYPE>0</TRXTYPE>
</taGLTransactionHeaderInsert>
<taMdaUpdate_Items xsi:nil="true"/>
</GLTransactionType>
</eConnect>

I'm currently importing the Bulk GL from Excel using Add-in, it is working fine in my local environment. but I’m facing an issue in Client's machine.

Error Number = 9398  Stored Procedure= taProcessAnalytics  Error Description = error processing taAnalyticsDistribution Node Identifier Parameters: taProcessAnalytics

Error Number = 9415 Stored Procedure= taAnalyticsDistribution Error Description = Transaction Dimension code does not exist for this dimension
Node Identifier Parameters: taAnalyticsDistribution
Related Error Code Parameters for Node : taAnalyticsDistribution
aaTrxDimID = Note: This parameter was not passed in, no value for the parameter will be returned.

XML Schema for your reference.

<?xml version="1.0" encoding="UTF-8"?>
<eConnect xmlns:xsd="www.w3.org/.../XMLSchema" xmlns:xsi="www.w3.org/.../XMLSchema-instance">
<GLTransactionType>
<eConnectProcessInfo xsi:nil="true"/>
<taRequesterTrxDisabler_Items xsi:nil="true"/>
<taGLTransactionLineInsert_Items>
<taGLTransactionLineInsert>
<BACHNUMB>CMXFR00000001</BACHNUMB>
<JRNENTRY>31963</JRNENTRY>
<SQNCLINE>16384</SQNCLINE>
<CRDTAMNT>0.00</CRDTAMNT>
<DEBITAMT>123.45</DEBITAMT>
<ACTNUMST>000-1105-00</ACTNUMST>
<DOCDATE>12/29/2018 12:00:00 AM</DOCDATE>
</taGLTransactionLineInsert>
<taGLTransactionLineInsert>
</taGLTransactionLineInsert_Items>
<taAnalyticsDistribution_Items>
<taAnalyticsDistribution>
<DOCNMBR>31963</DOCNMBR>
<AMOUNT>123.45</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDim>EMP1</aaTrxDim>
<aaTrxDimCode>EMP001 </aaTrxDimCode>
<aaTrxDimID>1</aaTrxDimID>
<aaTrxCodeID>0</aaTrxCodeID>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31963</DOCNMBR>
<AMOUNT>123.45</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDim>COSTCENTER</aaTrxDim>
<aaTrxDimCode>COST001 </aaTrxDimCode>
<aaTrxDimID>2</aaTrxDimID>
<aaTrxCodeID>0</aaTrxCodeID>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31963</DOCNMBR>
<AMOUNT>123.45</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDim>LOCATION</aaTrxDim>
<aaTrxDimCode>LOC </aaTrxDimCode>
<aaTrxDimID>3</aaTrxDimID>
<aaTrxCodeID>0</aaTrxCodeID>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31963</DOCNMBR>
<AMOUNT>123.45</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDim>QTY</aaTrxDim>
<aaTrxDimCodeNum>55</aaTrxDimCodeNum>
<aaTrxDimID>6</aaTrxDimID>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31963</DOCNMBR>
<AMOUNT>123.45</AMOUNT>
<ACTNUMST>000-1105-00</ACTNUMST>
<aaTrxDim>QUANTITY</aaTrxDim>
<aaTrxDimCodeNum>65</aaTrxDimCodeNum>
<aaTrxDimID>7</aaTrxDimID>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31963</DOCNMBR>
<AMOUNT>123.45</AMOUNT>
<ACTNUMST>000-1120-00</ACTNUMST>
<aaTrxDim>EMP1</aaTrxDim>
<aaTrxDimCode>EMP001 </aaTrxDimCode>
<aaTrxDimID>1</aaTrxDimID>
<aaTrxCodeID>0</aaTrxCodeID>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31963</DOCNMBR>
<AMOUNT>123.45</AMOUNT>
<ACTNUMST>000-1120-00</ACTNUMST>
<aaTrxDim>LOCATION</aaTrxDim>
<aaTrxDimCode>LOC </aaTrxDimCode>
<aaTrxDimID>3</aaTrxDimID>
<aaTrxCodeID>0</aaTrxCodeID>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31963</DOCNMBR>
<AMOUNT>123.45</AMOUNT>
<ACTNUMST>000-1120-00</ACTNUMST>
<aaTrxDim>QTY</aaTrxDim>
<aaTrxDimCodeNum>56</aaTrxDimCodeNum>
<aaTrxDimID>6</aaTrxDimID>
</taAnalyticsDistribution>
<taAnalyticsDistribution>
<DOCNMBR>31963</DOCNMBR>
<AMOUNT>123.45</AMOUNT>
<ACTNUMST>000-1120-00</ACTNUMST>
<aaTrxDim>QUANTITY</aaTrxDim>
<aaTrxDimCodeNum>66</aaTrxDimCodeNum>
<aaTrxDimID>7</aaTrxDimID>
</taAnalyticsDistribution>
</taAnalyticsDistribution_Items>
<taGLTransactionHeaderInsert>
<BACHNUMB>CMXFR00000001</BACHNUMB>
<JRNENTRY>31963</JRNENTRY>
<REFRENCE>SIX</REFRENCE>
<TRXDATE>12/29/2018 12:00:00 AM</TRXDATE>
<TRXTYPE>0</TRXTYPE>
</taGLTransactionHeaderInsert>
<taMdaUpdate_Items xsi:nil="true"/>
</GLTransactionType>
</eConnect>

 Can anyone please help me... Thanks in Advance :) 

we have GP 2010 and we change the windows from 7 to windows 10

i cant install the GP 2010 in windows 10 .

how i can install GP 2010 in windows 10

Hi Steve,

This DDR (Direct Debit product), I have found that DDR was designed a long time ago and was designed to work with a 3rd party product named Albany Software’s ‘eBank’ product to generate the DDR file.  That is why you are not finding a path or functionality within Dynamics GP to generate the DDR file out of the box.   Albany has since discontinued this product, and so Microsoft redesigned the RM EFT functionality (in GP 10.0 version), so you can just use our RM EFT functionality instead.

The DDR functionality was left within Dynamics GP, in case customers were still using it or had customizations for it, etc., but there is no functionality in GP at this time to generate the DDR file (from the DDEU007/DDEU008 tables).    

The RM EFT functionality updates the CM20202/CM20203 tables, which are populated by keying a cash receipt and marking it as ‘EFT’ type.   (The DDR functionality will also update the CM20202 only, in case customers wanted to point any customizations to this table.   But there is not path to  generate the DDR file from within Dynamics GP now.  You could insert a header record in to the CM20203 table and then you could use our EFT functionality to generate an EFT file, but that is not supported. )  

In current versions, I recommend to use ‘RM EFT’ functionality instead of the old DDR functionality for generating this EFT files.  

However, I think this would be a great Product Suggestion! and have observed a there are few suggestion already created

connect.microsoft.com/dynamicssuggestions

Hope this answers you question.

Thanks and Regards,

Shabareesh.

Hi,

I need to setup direct debits for my customer.  My customer expects invoices setup for Direct Debits to be automatically paid using the direct debits process.

My question is does direct debits create an output file?  I've setup EFT for payables several times.  This involves running a check batch, then generating an EFT file.

I see a similar process for EFT for receivables.  I can create cash receipts, then generate an EFT file for receivables.

My questions is does the Direct Debits module create any sort of file that gets sent to the bank?  I've read through the eBanking manual and it seems to me like Direct Debits and EFT for Receivables are two different things.

Any clarification would be appreciated!

Thanks,

Steve

This DDR (Direct Debit product), I have found that DDR was designed a long time ago and was designed to work with a 3rd party product named Albany Software’s ‘eBank’ product to generate the DDR file.  That is why you are not finding a path or functionality within Dynamics GP to generate the DDR file out of the box.   Albany has since discontinued this product, and so Microsoft redesigned the RM EFT functionality (in GP 10.0 version), so you can just use our RM EFT functionality instead.

The DDR functionality was left within Dynamics GP, in case customers were still using it or had customizations for it, etc., but there is no functionality in GP at this time to generate the DDR file (from the DDEU007/DDEU008 tables).    

The RM EFT functionality updates the CM20202/CM20203 tables, which are populated by keying a cash receipt and marking it as ‘EFT’ type.   (The DDR functionality will also update the CM20202 only, in case customers wanted to point any customizations to this table.   But there is not path to  generate the DDR file from within Dynamics GP now.  You could insert a header record in to the CM20203 table and then you could use our EFT functionality to generate an EFT file, but that is not supported. )  

In current versions, I recommend to use ‘RM EFT’ functionality instead of the old DDR functionality for generating this EFT files.

How do you create the EFT file for Direct Debits for Receivables? In particular, we need to manage the transaction codes easily and create an EFT file.

GP Direct Debits used to do it all. But now it is a module with significant limitations without a processor of the payment portion (EFT transaction). 

Currently, we have 3 file formats in EFT for Receivables (Prenote, 1st draw, and ongoing).  This is not dirt simple to manage.

Any suggestions are welcome.

Hello everyone,

A receipt was in the process of posting, the system hung and the job was terminated. The job went into batch recovery where it stated 'posting interrupted', the batch was recovered and posting went through successfully.

I am seeing the entries in the GL and Payables, what I also have is the same batch in Purchasing waiting to be posted, not sure if they attempted to re-enter before they informed us of the problem. If I try to post it says the vendor document exists, which is correct. 

When the item numbers are checked it is saying 'in-transit'. We have never used the in-transit document type in Receiving, so I am not sure how to approach this as Payables and the GL have been updated. 

Regards

Rosemary

Hi everyone

I need to find out the table that contains invoices in GP

Regards

Thuli