Prev
Next
Forums Lawson S3 Financials

Managing GL,AP, AR interface fallouts

Sort:
You are not authorized to post a reply.
Author
Messages
DougAB
Advanced Member
Posts: 28
Advanced Member
10/3/2013 6:53 PM
    We are interfacing transactions over from our OMS system to Lawson every 5 mins. There, of course, will be fallouts from either the importdb's or the interface programs themselves - AR550, AR560, AP510, AP520 and GL165. We are planning to gather all of the log files (.prt's) that have errors in them and put them in a central repository so we can easily identify the issue and resolve them.

    Couple of questions here:

    1) are the output files from either the importdb's or the interface programs stored in a table in Lawson at all? The output files differ in format a bit from AP to AR to GL.

    2) if not, has anyone built a process that extracts/parses the data out of these files? if so, what tool did you use?

    Thanks.
    Ragu Raghavan
    Veteran Member
    Posts: 468
    Veteran Member
    10/3/2013 7:12 PM
      At one instance where we were interfacing requisitions via RQ500, I had a script that would scan the RQ500.prt file for the word ERROR and if found, email the report to certain users.
      John Henley
      Senior Member
      Posts: 3348
      Senior Member
      10/3/2013 9:04 PM
        Most organizations that I've worked with that use the batch interfaces and want to archive them use shell scripts and/or ProcessFlow integrator, as well as the loadrpts utility to create an archive of print file history. Not a great solution, but it does work. I have worked with a couple of organizations that have used Monarch (don't know if it's still viable or not) to parse the reports into a database.
        Thanks for using the LawsonGuru.com forums!
        John
        You are not authorized to post a reply.