Managing GL,AP, AR interface fallouts

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.