Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Financial Management
Lawson S3 Financials
ARCUSTOMER integration
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
160
Members:
0
Total:
160
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Financial Management
Lawson S3 Financials
ARCUSTOMER integration
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
45 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Todd Mitchell
Veteran Member
Posts: 87
New Poster
Congrats on posting!
3/8/2011 3:18 PM
I am wondering if anyone has developed a best practice for continuous integration with customer related information. We are integrating from another system that is and will continue to be the owner of the data. We need to interface with this data and using deltas (for both adds and changes) update Lawson.
Right now we are developing a process to use ARICST and AR550 as an ongoing integration point. My main question is if anyone has developed a better ongoing process?
John Henley
Posts: 3366
New Poster
Congrats on posting!
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader art thou!
3/8/2011 4:22 PM
Split
Another alternative is AGS/Transaction calls (often done using ProcessFlow) against AR09/AR10 (and BR forms if appropriate). This is more "real time" but needs more logic/error checking. =
Please
login
to post a reply.