Bank Rec Interface

 3 Replies
 3 Subscribed to this topic
 44 Subscribed to this forum
Sort:
Author
Messages
mcl
Advanced Member
Posts: 29
Advanced Member

A Lawson newbie, so be easy, please.  Thought easiest interface to tackle would be flat file .txt from bank to Lawson Bank Rec.  On LSF9 so I see two options--CB185 flat file  and  CBSTMTREC database file.  Any suggestions?    With importdb, do I list all fields in header record, comma separated, or just the fields I want to upload?  Would Add-Ins be a better upload option?  Thanks

John Henley
Posts: 3364
New Poster
New Poster
Congrats on posting!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
Go easy? No way!
I've seen clients do a number of different approaches, but you're on the right track.

Depending on what format the file is from the bank, you can either
1) use CB185 flat file format (most of the times I "clone" this program for clients and tweak it to bank's spec)
2) use Excel addins to upload to CB80. The trick here is that you don't have anywhere to key in the transaction number on the form, so you are uploading to a number of hidden "PT" (position-to) fields in order to "position" to the correct row. It sounds difficult, but it's really not that hard. And, once you set it up, you can save and re-use the upload .UWF file each month.
Thanks for using the LawsonGuru.com forums!
John
Sam Simpson
Veteran Member
Posts: 239
Veteran Member
We do use PFI on this. We use a combination ScanFileClient and Datastage to transform
the input into a 71 length flat file (CB185-TAPE). Then sent an email to the users to run
the CB185 upload program. any error found on the input file is sent back to the bank.
SYED
New Member
Posts: 1
New Member
John,
When I use CB 80.1 to upload, the return message is this transaction does not exist which is not true. You mention that there are hidden fields. Can you explain how to get to those transaction number rows.

Thanks
Attachments