Hello Richard,
Thank you for another post! To answer your questions, I have included some information below.
1. There is not an example in the eConnect examples, but there is some XML schema references that you may want to review for this. The example schema below shows that we need to pass the distributions and then the header. Since we are not able to save entries in Bank Rec, it should post through Bank Rec to the GL after you do distributions, then pass through a header. Once the header is passed in, the entry should processes through Bank Rec to GL, into the Batch Number that you use.
<eConnect>
<BRBankTransactionType>
<eConnectProcessInfo />
<taRequesterTrxDisabler_Items>
<taRequesterTrxDisabler />
</taRequesterTrxDisabler_Items>
<taBRBankTransactionDist_Items>
<taBRBankTransactionDist />
</taBRBankTransactionDist_Items>
<taAnalyticsDistribution_Items>
<taAnalyticsDistribution />
</taAnalyticsDistribution_Items>
<taBRBankTransactionHeader />
</BRBankTransactionType>
</eConnect>
2. As I mentioned above, the distributions will post once you pass a header in after that, so there is no need for a CMTrx Number, you just need to make sure that the distributions before the header are for that particular entry.
Also, I wanted to note the following from the eConnect Programmers Guide on Bank Reconciliation under the XML Schema Reference section.
============================
The bank transaction entry is a posting window and it does not allow you to save batches. When you use eConnect to enter a bank transaction, it generates a batch in the General Ledger. eConnect does not post through the General Ledger. You must verify and post all the batches generated by eConnect to the Microsoft Dynamics GP General Ledger.
If your Microsoft Dynamics GP setup allows posting through the General Ledger, this does not apply to eConnect.
Microsoft Dynamics GP requires a distribution when you enter or void a transaction. To ensure the distribution is included, eConnect automatically supplies the required distribution. You cannot change how eConnect automatically creates this required distribution. If you configure eConnect to not automatically create distributions, eConnect still creates these required distributions.
At this time, the <taBRBankTransactionDist>, <taBRBankTransactionHeader>, <taBRBankTransactionVoid> XML nodes do not use the RequesterTrx element.
============================
Let me know if that helps!
Thanks,
Share
Report
75,730
All responses (
Answers (
