Integrating with Lawson

It depends. Some modules, GL for instance, have defined interface tables and programs, which will work just fine for what you are proposing. For those you can write directly to the database, understanding that there are differences across versions, database vendors, etc. I personally have written components that abstract some of that away. In some cases, it's better to interact with a Lawson form. In that case, you can use ProcessFlow (or the new "Process Automation" tools which, by interacting with the form, implement business logic and security. None of it's trivial. Trust me. I've been there. Here are some articles to give you some ideas.
https://www.lawsonguru.co...wson-Interfaces.aspx
https://www.lawsonguru.co...ation-Adventure.aspx
https://www.lawsonguru.co...tegration-Nodes.aspx

I have found the easiest way to do this is through ProcessFlow. I have files coming from our clinical systems daily which we had formated to match the GLTRANSREL file layout provided by Lawson. With the files in this format I just run an importdb command to load the file into GLTRANSREL (GL65) and run GL165 in non-update mode to report any errors and place the report in multiple users print manager for review. The users then run GL165 once they validate the all records are clean.

We are doing it via PFI and lawson Job scheduler. In some cases job runs in every 2 hours and some import programs (like MA531- Receipt import) run from within a flow from integrator and data gets automatically loaded into Lawson.

Hi @JeffR I too am looking to use GLTRANSREL on iSeries. Am finding that IMPORTDB works on QSH but that it does not work for my users on the LID. Any ideas why IMPORTDB would work through QSH but not on LID?
Much Thanks,