Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Integration / Customization
S3 Customization/Development
Integrating with Lawson
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
LindseyC
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5183
People Online:
Visitors:
201
Members:
0
Total:
201
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Customization/Development
Integrating with Lawson
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Art
New Member
Posts: 1
2/1/2012 1:28 AM
I am looking for the best way to help a client automatically import data into lawson on a regular basis, for example monthly journal entries for various accounts. What is the best way to do this? Is their an API that we can use, or can we connect directly to the lawson database via ODBC? Does lawson have any SDKs or kits for developers? What is best practice? Any help anyone can provide would be greatly appreciated. Thank you.
John Henley
Senior Member
Posts: 3348
2/1/2012 11:13 AM
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
JeffR
Advanced Member
Posts: 22
2/1/2012 5:45 PM
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.
Vijay S
Veteran Member
Posts: 174
4/10/2012 8:50 AM
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.
Ariel
New Member
Posts: 3
8/1/2013 2:28 PM
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,
You are not authorized to post a reply.