ARCUSTOMER trigger - LawsonGuru.com - LawsonGuru.com Forums -

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

DougAB

Advanced Member

Posts: 28

9/13/2012 5:00 PM

we are interfacing our AR customers from our OMS system to Lawson. We are looking for ways (from a Pflow concept, not a db concept) to identify when a customer record gets interfaced over from our OMS system to Lawson so that we won't resend it over again (conceding that there will be some fallouts from time to time).

We tried adding a field on the db to indicate when a record made it to Lawson okay, but soon realized it takes too much time to query these while trying to run the importdb to ARICST first. We're hoping for something a Pflow can do as a better approach.

Any ideas are greatly appreciated.

Thanks,
Doug

David Williams

Veteran Member

Posts: 1127

New Poster

9/13/2012 5:16 PM

Does your OMS system have a date stamp for when a customer record has been added?

DougAB

Advanced Member

Posts: 28

9/13/2012 6:58 PM

yes, it does.

reading the Lawson documentation, it mentions that there are built-in application triggers, but they don't mention what these triggers are specificallly. do you know what these application triggers are that are supposedly built-in?

David Williams

Veteran Member

Posts: 1127

New Poster

9/13/2012 7:25 PM

If you are interfacing from OMS into Lawson then you could run an SQL Query to get your new customers by a date range and import them into Lawson (by an AGS call to AR09 and/or AR10 or have ProcessFlow run an import job). The triggers you're referring to in Lawson are pre-built application based and wouldn't work for what you're trying to do. (These triggers are listed in the ProcessFlow Reference Guide, by the way.)

You can schedule your flow to run nightly via the ProcessFlow Scheduler tool.