ED02 Setup..What is best practice

 5 Replies
 1 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
Patricia Mane
Basic Member
Posts: 24
Basic Member

    We went live with Lawson 01-05-2015 as well going EDI with all our vendors via GHX.  For the last week we would receive the EDI Processing Error emails from Lawson:  Attempting Connection to 'GHX Server IP Address'..  I entered a ticket to support for GHX and they came back saying that my ED02 was possibly incorrect.  Which now leads me to wonder, if the information given by the consultant for our edi setup was correct. 

    I currently have the following on ED02 in UDF2 "1:a" they are saying it should be "1:b".. 

     

    May I ask what others are doing that use GHX....  When we converting our conversion specialist with GHX wasn't as helpful as I would have hoped and over the past 5 months we have struggled some with our EDI...  Things have improved tremendously and then to see we have things set up incorrectly, makes me wonder. 

     

    Thanks

    Trish

    JonA
    Veteran Member
    Posts: 1163
    Veteran Member
      We don't use GHX but it sounds like they want the transfer in binary which should be 1::b (two colons between the 1 and the b). 

      FTP CONNECTION OPTIONS
      User field 2 is can be used for specifying the FTP connection parameters: debug, active or passive ftp connections, ascii or binary data transfers, and an ftp timeout parameter.   Parameters are delimited by a colon (:).  If a parameter is blank the default value will be used.

      The order of the parameters is debug:connection:mode:timeout.

      VALID VALUES:
      Debugging: "d" or "debug" or "1" to enable, "0" or "off" to disable.  If blank, defaults to 0;
      Connection: "1" or "p" or "passive" for passive connections, "0" or "a" or "active" for active connections. If blank, defaults to "1";
      Mode: "0" or "a" or "ascii" for ascii transfers, "1" or "b" or "binary" for binary transfers.  If blank, defaults to "binary".
      Timeout: specify a time out in seconds, the default is 120.

      Examples:
      To enable only FTP Debug Trace, enter just a 1 in User Field 2. This is equivalent to "1:p:b:120"
      To enable only an active FTP connection, enter ":a" in User Field 2. This is equivalent to "1:p:a:120".
      To enable debug with a ascii transfer:  enter "1::a" in User Field 2. This is equivalent to "1:p:a:120"
      To change only the timeout to 3 minutes (180 seconds): enter ":::180" in User Field 2.  This is equivalent to "0:p:b:180".
      To enable debug, with an active connection, ascii transfer and 4 minute time out: enter "1:a:a:240" in User Field 2.

      Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
      Bev Edwards
      Veteran Member
      Posts: 366
      Veteran Member
        We have GHX, but the User Field2 value tht Jon is referring to is different than what we have on our ED02 forms. Maybe you have a different version of Lawson? We're on 9.1. I'm not able to attach screen shots to show you our set up. LawsonGuru is giving me an error.
        We have 2 ED02's.
        First one:
        Carrier:GHXTCP
        Method: TCP Provider: GHX
        Host:The GHX server IP addess
        User Field 1: 31234
        User Field 2: 41234
        User Field 3: 30
        User Field 4: 10

        The 2nd one:
        Carrier : NEOFTPGHX
        Method: FTP Provider: LAWS
        Host: Our ftp address
        Login: ghxftp
        Access: ftp2ghx
        User Field 1 and User Field 2 are both blank.
        User Field 3: in
        User Field 4: out
        JonA
        Veteran Member
        Posts: 1163
        Veteran Member
          Bev, the numbers in your user fields for your GHXTCP carrier are specifically for sending and receiving data across TCP for GHX ConnectPlus. User Field 1 and User Field 2 are the socket numbers for sending and receiving, respectively. User Field 3 is the maximum number of retries the system will attempt to send or receive data. User Field 4 is the connection time-out in seconds.

          Your NEOFTPGHX carrier is a straight forward unsecured FTP connection. User Field 3 is the directory to which the system puts the purchase orders (850s) and User Field 4 is the for the directory from which the system picks up acknowledgements (855s), invoices (810s) and other inbound files.
          Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
          Bev Edwards
          Veteran Member
          Posts: 366
          Veteran Member

            Thanks Jon!!

            Saving this and adding to my EDI notes. I'm learning as I go along!

             

            Bev

            Kat V
            Veteran Member
            Posts: 1020
            Veteran Member
              We're neoftpghx as well:
              Carrier : NEOFTPGHX
              Method: FTP Provider: LAWS- Lawson
              Host: IP address
              Login: ghxftp
              Access: ftp2ghx
              User Field 1 blank
              User Field 2 1
              User Field 3 in
              User Field 4 out

              Jon is correct - GHX is telling you they want it binary. But as GHX has been migrating in the back to amazon cloud, your consultant may have been right at the time, it's just changed.