IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Trading Networks using Wrong Delimiter for Processing

  • 1.  Trading Networks using Wrong Delimiter for Processing

    Posted Sun December 24, 2017 10:30 PM

    Hi All,

    I am new to TN. Need some help. I set up 2 partner profiles, one for my enterprise and the other for partner. I have also set up an EDITPA for the sender, receiver combo.

    However, whenever I submit documents to TN for processing, it never takes the proper record delimiters and is not able to recognize the document.

    I have also defined the required document type in Document Types tab in MWS.

    Could you please help me trouble shoot?

    Below is the content that gets saved in TN. It is considering 1 as the record delimiter.

    ISA*00**00**01
    *AIBEP*ZZ*0095AMRDASHP*1
    01
    1
    27*1
    71
    9*U*00400*000003438*0*P*>
    GS*NL*1
    234567890 *999999999 *201
    201
    26*1
    21
    1
    *1
    *T*00401
    0
    ST*31
    5*0001
    B4*1
    5*24*2*201
    201
    27*1
    505*Statu*Equi*EquipmentX*D*EQUI*Location Identifier*A*3
    N9*01
    *Reference Identification*Free-form Description*201
    201
    27*1
    5051
    50*01
    *01
    Reference Identification1
    Reference Identification1
    Reference Identification
    Q2*VESSEL C*COU*201
    201
    27*201
    201
    27*201
    201
    27*1
    663*28881
    3984*A*Flight/Voy*01
    *Reference Identification*B*Vessel Name*1
    71
    7*B*E
    SG*2*001
    *DI*201
    201
    27*1
    5051
    5*01
    R4*1
    *A*Location Identifier*Port Name*COU*Terminal Name*Pier*ST
    DTM*001
    *201
    201
    27*1
    5051
    6*01
    *CC*Date Time Period
    DTM*001
    *201
    201
    27*1
    505*01
    *CC*Date Time Period
    DTM*001
    *201
    201
    27*1
    505*01
    *CC*Date Time Period
    DTM*001
    *201
    201
    27*1
    505*01
    *CC*Date Time Period
    DTM*001
    *201
    201
    27*1
    505*01
    *CC*Date Time Period
    DTM*001
    *201
    201
    27*1
    505*01
    *CC*Date Time Period
    DTM*001
    *201
    201
    27*1
    5051
    60*01
    *CC*Date Time Period
    DTM*001
    *201
    201
    27*1
    505*01
    *CC*Date Time Period
    DTM*001
    *201
    201
    27*1
    505*01
    *CC*Date Time Period
    DTM*001
    *201
    201
    27*1
    5051
    6*01
    *CC*Date Time Period
    V9*AAD*Event*201
    201
    27*1
    5051
    60*City Name*ST*COU*001
    *STANDARDX*6342981
    7*Tr*Free-Form Message*01
    *572*STANDARDX*82*1
    5*2*1
    650831
    559*6928
    SE*1
    8*0001
    GE*1
    *1
    IEA*1
    *00000001
    4

    However, my original EDI document is,

    ISA*01*0000000000*01*0000000000*01*AIBEP*ZZ*0095AMRDASHP*101127*1719*U*00400*000003438*0*P*>
    GS*NL*1234567890 *999999999 *20120126*1211*1*T*004010
    ST*315*0001
    B4*15*24*2*20120127*1505*Statu*Equi*EquipmentX*D*EQUI*Location Identifier*A*3
    N9*01*Reference Identification*Free-form Description*20120127*1505150*01*01Reference Identification1Reference Identification1Reference Identification
    Q2*VESSEL C*COU*20120127*20120127*20120127*1663*288813984*A*Flight/Voy*01*Reference Identification*B*Vessel Name*1717*B*E
    SG*2*001*DI*20120127*150515*01
    R4*1*A*Location Identifier*Port Name*COU*Terminal Name*Pier*ST
    DTM*001*20120127*150516*01*CC*Date Time Period
    DTM*001*20120127*1505*01*CC*Date Time Period
    DTM*001*20120127*1505*01*CC*Date Time Period
    DTM*001*20120127*1505*01*CC*Date Time Period
    DTM*001*20120127*1505*01*CC*Date Time Period
    DTM*001*20120127*1505*01*CC*Date Time Period
    DTM*001*20120127*1505160*01*CC*Date Time Period
    DTM*001*20120127*1505*01*CC*Date Time Period
    DTM*001*20120127*1505*01*CC*Date Time Period
    DTM*001*20120127*150516*01*CC*Date Time Period
    V9*AAD*Event*20120127*1505160*City Name*ST*COU*001*STANDARDX*63429817*Tr*Free-Form Message*01*572*STANDARDX*82*15*2*1650831559*6928
    SE*18*0001
    GE*1*1
    IEA*1*000000014

    #edi
    #webMethods
    #Integration-Server-and-ESB


  • 2.  RE: Trading Networks using Wrong Delimiter for Processing

    Posted Sun December 24, 2017 11:37 PM

    If I define an EDITPA and define the partner profiles with the correct ID types, it just takes some random delimiters and tries to process the data. I am not sure why.

    Any help will be appreciated.


    #Integration-Server-and-ESB
    #edi
    #webMethods