Prev
Next
Forums Lawson S3 Financials

Issues with AP 161 generated file and ED501 translation for 820

Sort:
You are not authorized to post a reply.
Author
Messages
UD
New Member
Posts: 2
New Member
7/29/2019 6:22 PM
    We are having issues getting the Lawson generated AP161 PAYMENT file to translate into an 820. There was no REMIT file generated. Is that an issue? Or should we keep looking at trading partner setup? In the AP161 flat file, where is the trading partner ID located, and would it make a difference if it was not found? The error we get is simply, no data to be translated.

    Anyone have experience with an issue like that? Not attaching the file for obvious reasons, but can answer questions about specific lines and locations of data.

    Also, it looks like the preloaded trading partners vary based on the implementation. Are the 820 maps delivered with Lawson? Is there more than one? I saw one for BoA, but not sure if the WF would be similar. Or same. Either way, it would get us closer to a resolved issue.
    UD
    New Member
    Posts: 2
    New Member
    7/30/2019 2:19 PM
      In lieu of this answer, does 820 have to look at the remit file ? And is that file only generated for ETEBAC format, per documentation? What is the optimal way to setup an outbound 820 in a different format, through Lawson?
      You are not authorized to post a reply.