Andrew Karasev

Great Plains Consultant News: Intercompany Transactions Integration

If your Microsoft Dynamics GP environment contains several companies and you deploy GP Intercompany module, and your Vendor Invoices are coming through external system, integrated with Dynamics GP, then here are highlights for consultant on designing integration in GP Integration Manager. 

As you will need to build AP transaction GL distribution lines, this integration is not recommended for initial introduction to IM and probably should be trusted to Dynamics GP consultant or better to say – Great Plains Technical Consultant.  If you have external EDI system, or you will need to pull records via SQL queries, available in Advanced ODBC data source, chances are high, that you will have to use one table, where you will have to group records for invoice header and then use SQL union to add second half of the distribution, usually AP account

1.       Intercompany Transaction flag.  If you want to enable cross company posting, then you should set intercompany flag in Invoice header to true.

2.       Intercompany Distribution.  As you know, in AP intercompany invoice, you add company ID in the GL distribution line, and usually for Purchasing account, while Accounts Payable account remains in the source company

3.       Adding AP account.  In your advanced ODBC source you can select existing records, and AP account you add through union addition to your normal select statement.  If you use text file driver – this work is extremely buggy, but if you use ODBC connection to MS SQL Server table, then union addition should be relatively easy programming routine

4.       Additional Notes.  If your export file is text EDI code, you may try to first import it to SQL EDI tables to resolve text driver limitations and then work with more established SQL Server Advanced ODBC source

Article Tags: Great Plains, Advanced Odbc

Source: Free Articles from ArticlesFactory.com

ABOUT THE AUTHOR