Hardware

Great Plains VAR News: Intercompany Transactions Integration - Alba Spectrum

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 /Software News Articles/ - NAPERVILLE, IL, September 14, 2008 - 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. Microsoft Text Driver known issues. When you create new ODBC DSN, based on the text file, there seems to be problems, and they are consistent for Windows XP, Vista, Windows 2003 and R2. We recommend you - if you face these problems - do not use column type and width guess wizard 5. 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


Add your comment:
Name:
Site address: http://
Your message:
Enter today\\\\'s date, 2 digits
(spam protection):

News of the day
ATI and Nvidia said to be uncertain about 80nm production.
ATI Technologies and Nvidia will focus on graphics chips manufactured on a 90nm process technology rather than migrating their production to 80nm this year, due to yield and technology issues for wafer manufacturing, according to first-tier graphics card makers. Although ATI initially planned to launch graphics chips (RV570, RV560, RV535 and RV505) that adopt an 80nm manufacturing process in the third quarter of this year, the makers expect ATI to first roll out 90nm versions of those chips, as the company has been able to improve its yields on 90nm technology production.
Popular Articles

Blu-ray Growing, but 58% Still Confused.
Some people still think standard-def DVD is "good enough" compared to Blu-ray Disc.

dbx repair - repair Outlook Express dbx files.
EA Releases SecuROM De-Authorization Tool.
Electronic Arts is trying to make things right again with the release of the SecuROM de-authorization tool.