Prev
Next
Forums Enterprise Resource Planning & Manufacturing Lawson S3 Procurement

GHX EDI options

 1 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages
Jenna
Posts: 5
3/13/2008 2:15 PM

    Is anyone using GenTran and GHX instead of Lawson & GHX?

    We already have a few partners set up with GenTran, and would like to avoid purchasing the Lawson EDI in order to connect with GHX.  Our main concerns are the level of effort involved and stability.  Does anyone have tips/experiences they would be willing to share?

    Thank you,  Jenna

    Robert Herron
    New Member
    Posts: 1
    New Member
    5/29/2009 2:22 PM
      I am certified and have used Gentran and Websphere (Mercator) inside and outside of Lawson. Also was original part of the Lawson three person TCS EDI product development team and am currently using TCS at the company I am currently working with. Have evaluated and used the WebSphere messaging product (MQ series) integrated with WebSphere

      One should be able to connect to GHX using the communications component of Gentran.

      The following are my opinions based on experience in EDI and Data communications (around 30 years).
      Real question revolves around three separate parts -
      1. EDI data structures and data transformation.
      2. Data Communications.
      3. Job Scheduling.

      At this point - no matter which product is used, the level of complexity is high in all three parts.

      1. EDI data structure complexity.
      GHX supports multiple types of "supplier" specified EDI data structures because they just pass the data on.
      Gentran - a user can develop and support supplier EDI data structures.
      Lawson Websphere Mercator - a user can develop multiple EDI data structures.
      Lawson TCS - comes with a set of defined supplier EDI data structures however capability is limited and support is limited as Lawson laid off the TCS development team.

      Summary - Complexity is high. Stability dependent on suppliers - not GHX. Flexibility - High except for Lawson TCS.

      2. Data communications.
      - GHX uses a WebSphere "messaging" data communications type of product called WebMethods however not totally compatible with the WebSphere.
      - The Lawson connection to GHX uses a FTP data communications connection via the Lawson TCS Cleo component. Reliability - low due to GHX data comm resources and commitment to FTP. (Learned that from GHX).

      - Summary Complexity High and Stability High - Control - Low.

      3. Job scheduling.
      Job scheduling dependent on Lawson and inter related components PO120 runs, Gentran / Mercator/ TCS data transformation speeds, connectivity and internet transfer/ acceptance facilities at both ends (Yours and GHX).
      Experience has shown that Lawson user problems have occurred in the timing of transmissions
      .
      Summary - Complexity Low. Stability high. CONTROL - low.

      Again these are opinions based on experience and I do not need employment.

      Hope this information is of help.