Prev
Next
Forums Lawson S3 Procurement

How can I test EDI?

Sort:
You are not authorized to post a reply.
Author
Messages
John Costa
Veteran Member
Posts: 154
Veteran Member
4/17/2012 12:46 PM
    To all,

    Forgive me, but I am not an EDI person nor have I been trained on the Lawson EDI product.

    I recently upgraded my DEV environment, removing MKS Toolkit and installing Lawson Unix Utilities.  Here are some further system details:

    Windows Server 2008 - Enterprise - 64-bit
    Lawson Environment 9.0.1.9
    Lawson S3 Applications 9.0.1.7
    Lawson EDI 9.0.1.5

    At this point, I am trying to test EDI.  I've verified that the Comm Server and Mail Agent are starting and I can execute ED330 with no issues.  Where do I go from here?  How can I test an EDI file of some kind to verify EDI is actually running and ready to process incoming files?

    Thanks in advance for any help / suggestions.
    _________________ John - Wichita, KS
    JimY
    Veteran Member
    Posts: 510
    Veteran Member
    4/17/2012 2:09 PM
      Hi John,
      If your EDI setups are the same on DEV as they are on production then you could copy the files from prod to DEV and run ED502 for 810 and 832 transactions. You would then run MA540 for the 810's to create the invoices and PO560 and PO150 for the 832's to load them. The files should be archived in $LAWDIR/logan/edi_arch_inb. For PO's you can create a PO using a vendor that is set up for EDI and then run PO120 and ED501. ED502 and ED501 would be in the LOGAN production line. Hope this helps.
      JonA
      Veteran Member
      Posts: 1162
      Veteran Member
      4/18/2012 6:25 PM
        Actually ED501, ED502 and ED330 should all be run in the DEV productline if that's where your setups are.
        Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
        JimY
        Veteran Member
        Posts: 510
        Veteran Member
        4/19/2012 9:55 AM
          I meant to say product line instead of production line. Sorry for the typo.
          You are not authorized to post a reply.