• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Human Capital Management Lawson S3 HR/Payroll/Benefits

PR160 ACHFILE formatting change on 9.0.1.x

 5 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
TBonney
Veteran Member Send Private Message
Posts: 281
Veteran Member
1/13/2012 2:59 PM
We are upgrading from Lawson 9.0.0.x to 9.0.1.x and have noticed that when the PR160 is run, not only has the PMTOUT file changed, but so also has the ACHFILE.

One step forward...
They have fixed the PMTOUT file from 9.0.0 to 9.0.1, from a single line flat file to multiple records per employee/transaction, which was a blessing.

...Two steps back???...
However, did they also change the ACHFILE to the exact opposite??? On 9.0.x, there were carriage returns & line feeds in the file. However, the new 9.0.1.x file appears to be a continuous, single line, flat file now.

I thought that an ACHFILE was in a universally accepted format, regardless of bank. So, am confused as to how Lawson can change the output format/layout.

Does anyone know of any patches released for 9.0.1.x to correct this issue?

Thank you in advance!
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
1/13/2012 7:15 PM
You could always run it through the Lawson utility cnvexp
cnvexp -f ACHFILE 94 > ACHFILE_w_cr

The above will put in carriage returns/line feeds at position 94... adjust the number for record length.
TBonney
Veteran Member Send Private Message
Posts: 281
Veteran Member
1/13/2012 7:41 PM
Thanks Greg! (Although we shouldn't have to take the extra step), will do...
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
1/13/2012 7:54 PM
Well, there is THAT.... ("we shouldn't have to take the extra step")
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
1/18/2012 12:59 PM
You shouldn't - check the KB - there is a workfile setting that will fix this for you

HTH,
Karen
TBonney
Veteran Member Send Private Message
Posts: 281
Veteran Member
1/18/2012 1:08 PM
Thanks guys...I did find how to set it in the workfile instead...

It is referenced in Lawson KB article #71213.

Thanks for the suggestions!