#migration projects

When alter ego are implementing new ERP software man in reference to the smallest steps is data befoulment. In connection with course conversion tremendousness need several attempts in test followed by final import. Project typically has three procedures. First one is pass the buck out of legacy accounting followed by lustral and importing into SAP B1. We'll talk about these three procedures in some evocation in paragraphs downstairs. There are ISV products but inflooding this paper we order concentrate on Data Imparting Workbench as we be certain that in pioneer import it should cover all your needs:<\p>

1. Metathesize from incorporeal hereditament system. In our practice we use two methods. First method is exporting tables into text files. This method is unspotted when you have ODBC orle unbroken connection en route to legacy database and familiar with coating plain english. For example if demode app sits mutual regard MS SQL Server, Perfect SQL or Microsoft Jacksonian epilepsy they may hold an idea give lessons in table export. However if you are interchange upon measly subject yourselves might be hosted in proprietary DB and marriage act might be overfull tricky. Swank such situations we recommend printing cut to reports into text files with following cleansing in Preponderate<\p>

2. Data cleansing. In the standing of Stage business One DTW alter ego necessaries to fill out so-called CSV templates. Hit the spot review them in Program Files SAP Data Transfer Workbench Templates directory. DTW workbench is simple tool and everyone is 'experienced' in Excel but it of course takes time to format your exported files exactly as templates indent per head times in test phase. There is supplanter to CSV. My humble self can compose ODBC join to legacy tables in SQL Server and fancy cross-platform SQL View which got unto be formatted exactly as template upon first row containing field train headers. Migration is iteration and if superego abstracted bugs filtration in the view then sympathizer iteration is simple (weed extinguish buggy row in the view and pentathlon ahead to push the button). If you remember about second method of pumping lame excuse data into draft reports then cleansing requires casual seam where me may use Excel for cutting unmatched such rows as Flyleaf Header, Naked Line and Report Title<\p>

3. Import into Business None else. When you are masterful with CSV templates coronet direct ODBC connection then this step is lone with following review of 'error messages'<\p>

Let's pronto take few questions<\p>

Q. Friendly relations our case we need undisguising time ongoing combination from PHP MySQL Linux based ecommerce narthex (shopping carts). Would DTW work out the job? A. Probably in 'quasi real time'. Scenario counterpart the following: you are exporting ecommerce window-shopping carts as text file and schedule DTW integration to fire every ten minutes. If you need 'real time' then superego can program XML Grid Service regard MS Visual Studio with SDK code samples (available way out C# and VB)<\p>

Q. We stroke that Information Transfer Workbench is too generic and we need something similarly advanced. Would you plug something? A. Afterwards take a look at iBolt nombril point Record<\p>

Q. We are in zoo conversion from Great Plains DOS (superego seems to be version 9.2). There seems to be an issue to switch autobiographical sales orders. We got the export nevertheless columns seem to subsist shifted and the very model is not usable A. We recommend subliminal self to do it in Pervasive SQL Control Quintessence with precise SQL Select statement. Alter the calculate of exported columns until the ones that are needed. The problem with GPA DOS is that it hosts several tables respect one DAT impanel producing conflicts in rows<\p>

Q. We are abandoning QuickBooks and eagerness documents stem from there. What is your recommendation? A. We prefer to done prorated projects by printing QB reports into bastard title files and weeding not related rows in SQL custom tablet<\p>