Lawson Integration

Elam:

I do not know if this is the "best way" but one solution is to write scripts that call the "importdb" and "rngdbdump" utilities.

"importdb" moves data into Lawson tables, provided that the import files are properly set up, properly scrubbed to prevent bad data from entering, and, will not screw up relationships to other tables. I can't tell you off the top of my head what issues would come up, that will take you some study. Use the utility "dbdoc" to dump the table ("file") definitions for the various files, and check on the relationships.

"rngdbdump" can dump a Lawson file in various ways to output csv files. Check on its functionality. Using indexes, it can dump specific ranges of data, and it can dump only specified fields if you want it to.

I have written interfaces which work both ways, using those utilities. A more elegant method is to "importdb" into a specific import table, then finish the import by running the import program. Again, off the top of my head I don't know if there are such import pathways for Contract, Item Master, or Vendor Catalog. If there are, they should be used instead of a direct "importdb" into the actual tables used. One the other hand, "rngdbdump" has no impact on any working files, since it's essentially read-only.

For the Item Master export FROM Lawson, I can help. IC52x are some jobs that you should look at. Here we use a modified IC527 feed from Lawson out to Cerner's Surginet piece. If you'd like, I could share scripts.
https://www.lawsonguru.co...h-ge-centricity-dms/