Creating a Microsoft Dynamics GP Integration with eConnect and a SQL Stored Procedure
This is third in a series of articles covering eConnect for Microsoft Dynamics GP. Part 1 explained that the business logic for eConnect exists in stored procedures within the Dynamics GP company database. Part 2 created an eConnect integration utilizing the .NET API's within Visual Studio.
This post examines using eConnect directly from a SQL stored procedure. The stored procedures are utilized by the .NET APIs to perform business logic verifications on the data being integrated. Next, transactions that pass the verification are inserted into the appropriate transaction work tables within Dynamics GP.
Find requirements and names of stored procedures by referring to the XML Node reference within the eConnect Programmer's Guide and Reference document found on MSDN.
Step 1 - Determine which Stored Procedures to Utilize
In this example, a receivables invoice transaction data with accompanying GL distributions will be integrated into Dynamics GP Receivables Management work tables as a batch. To determine the necessary stored procedures to use, look at theRMTransactionType schema found in the eConnect Programmer's Guide:
<eConnect><RMTransactionType><eConnectProcessInfo /><taRequesterTrxDisabler_Items><taRequesterTrxDisabler /></taRequesterTrxDisabler_Items><taUpdateCreateCustomerRcd /><taCreateCustomerAddress_Items><taCreateCustomerAddress /></taCreateCustomerAddress_Items><taRMCommissions_Items><taRMCommissions></taRMCommissions_Items><taRMTransactionTaxInsert_Items><taRMTransactionTaxInsert /></taRMTransactionTaxInsert_Items><taRMDistribution_Items>
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here