Dynamics GP Bank Transfer Node for SmartConnect using Multi-Entity Management
Why should you care about a Bank Transfer Node for SmartConnect? If you ever run into the need to create a map in SmartConnect for Bank Transfers you will notice there isn’t a node available for that. You can create your stored procedure and register the Bank Transfer Node.
In this blog, we will go over a quick guide to help get you started on what you would need to register the Bank Transfer Node for SmartConnect.
Create your procedure with the validations, inserts, and updates needed on your environment. The one I created was for Dynamics GP 2016 R2 using Multi-Entity Management (MEM). Here is a list of the tables affected by the stored procedure:
Insert into the following tables:
Depending on the table you’re inserting and the intercompany distributions, you might need to insert one, two or four lines. I would suggest that you create a test transfer on your test company for reference. Inserts:
The number of inserts will also be affected by MEM and whether you’re are using intercompany distributions or not.
Updates to Dynamics GP 2016 R2:
Update your current balance on CM00100 for both checkbook ids
Create the stored procedure with all the parameter start with I_v
Add the last two expected by SmartConnect as:
@O_iErrorState int output,
@oErrString varchar(255) output
Create the stored procedure Post and Pre even if they are empty.
Grant execute on your stored procedure so that eConnect can use it:
GRANT EXECUTE ON BankTransferProcedure TO DYNGRP
By following this quick guide, should be ready to register the node on SmartConnect and create a map.
This Bank Transfer Node for SmartConnect was created on Dynamics GP 2016 R2 using MEM, some changes might apply depending on the version of GP you are running and third-party products.
If you are having difficulty getting started and would like some additional help please contact FMT Consultants by filling out the form below.