Mirating non-Lawson data into Lawson

Welcome to LawsonTalk. We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it.

Join our community!

If you're already a member please log in to your account to access all of our features:

Mirating non-Lawson data into Lawson; Migrating into Lawson
Topic Started: Sep 14 2009, 11:46 AM (261 Views)
mh53j_fe	Sep 14 2009, 11:46 AM Post #1
Newbie Posts: 6 Group: Members Member #10,810 Joined: October 1, 2008	B) I am wondering if anybody has any experience migrating non-Lawson data into Lawson. We plan to migrate the financial data (in Solomon) of another company into our Lawson financials (9.0.0.4) I found a couple of migration documents in myLawson.com, but I am hoping that there are others out there that have done this and can help me with some best practices. Thanks in advance for your help.



MichaelLandis	Sep 14 2009, 12:12 PM Post #2
Member Posts: 17 Group: Members Member #14,907 Joined: July 14, 2009	I'd start off by getting acquainted with the Financials Conversion documentation. Lawson provides a wide variety of batch update programs specifically for this purpose. GL165 for GL transactions; AP510 for AP Vendors; AP520 for AP invoice data; etc, etc. You'll have some work to do to get the data in the right format for these various programs, but that's still a whole lot easier than having to write it all from scratch. I've done several acquisition-related implemenations using the standard Lawson apps. G'luck! Michael L.



georgegraham	Sep 14 2009, 01:50 PM Post #3
Super Member Posts: 122 Group: Members Member #529 Joined: March 29, 2006	I would agree and recommend using this far above trying to push the data in yourself with any other tool or ETL. These programs offer features such as being able to run the jobs in preview mode to make sure your mapping is correct as well as appl[ying all of the standard Lawson business rules and logic as if they were entered by hand - that way when you do run it in update mode if you have certain records that do not load it does not impact the others - then you can simply make your corrections to the remaining data and push that in. These program update any ancillary and related tables - trying to map that yourself may be a very dificult task.



mh53j_fe	Sep 15 2009, 06:08 AM Post #4
Newbie Posts: 6 Group: Members Member #10,810 Joined: October 1, 2008	Mike and George, Thank you for your insight. Michael, you mention that we will have some work to do get the data in the right format. Do you place the data in a csv or in a flat file and then use the DB utility to upload the data into Lawson?



MichaelLandis	Sep 15 2009, 07:26 AM Post #5
Member Posts: 17 Group: Members Member #14,907 Joined: July 14, 2009	Most of the Lawson interface programs use CSV-formatted data, and are very straightforward to use. A couple of them DO require a preliminary importdb into DB staging tables (GL165 uses GLTRANSREL; AP510 uses APCVENMAST; AP520 uses APCINVOICE/APCDISTRIB; etc, etc). But some of the others read directly from the CSV file. The GL165 can be a little tricky if you use the old-company/old-account fields to translate from old GL structure to an entirely new one in Lawson - but these features are also very helpful/powerful. Search MyLawson for "Conversion" documents. There should be one for HR, one for Financials, etc.


« Previous Topic · Other · Next Topic »