We tried to use that CSV method as well. It took many hours and was prone to failures. I imported with jobs that I wrote using text files exported from our old system. These included: Items, Trade agreements, QOH, vendors (including contacts and addresses), AP and AR aging (with the original due dates). Open orders/purchase orders were entered by the users so they could "clean up" the old ones and it is good training. We felt if we imported everything they wouldn't get enough experience and the users would have problems on the go-live day.
I could provide sample XPOs, you'd have to modify them as we have some custom fields in Axapta and you'd have to create the text files from your old system (which you must have done to create the CSVs). We used the Axapta csv import customers before we found the new way. Doing it again I would use jobs for everything. --- In development-axapta@yahoogroups.com, "rwbowersox" <[EMAIL PROTECTED]> wrote: > > I am importing a large set of ERP data into an Axapta database via > Definition Groups and CSV files. I would like to know any tips or > techniques that would bump my performance on this process. > > For example, I am importing 53,000 part numbers which is taking me > about 11 hours to import. I recently divided the datafile into 2 files > and it helped immensely. Altogether I am importing around 464,000 > records between customers, vendors, addresses, contacts, items, SO's, > PO's, Inventory, AR, AP, and GL journals, and Notes. The process is > taking about 48 hours. We would like to decrease it to 24 hours. > > Any suggestions? >
