none
BizTalk 2009 997 Issue - AK401 seems to be malformed using the component seperator RRS feed

  • Question

  • Below is the EDI sample, look at the rejected transaction set.  Notice the AK401 has two ^^ which is the component seperator.  Any thoughts on why this is occuring?

    ISA*00*          *00*          *ZZ*FOO            *ZZ*BAR            *171109*1025*U*00501*000001253*1*T*^~
    GS*FA*FOO*BAR*20171109*1025*1253*X*005010~
    ST*997*2453*005010X230~
    AK1*RA*16034*005010~
    AK2*820*000574918~
    AK3*NTE*3**8~
    AK4*2^^1**1~
    AK3*NTE*3**6~
    AK5*R*4*5~
    AK2*820*000574919~
    AK5*A~
    AK9*E*2*2*1*4~
    SE*11*2453~
    GE*1*1253~
    IEA*1*000001253~


    • Edited by taboryee Thursday, November 9, 2017 4:31 PM
    Thursday, November 9, 2017 4:30 PM

All replies

  • The first think I would do is look at the Xml of the 997.
    Thursday, November 9, 2017 5:38 PM
  • Here it is.  The partner says their BizTalk system deems the 997 invalid, but our BizTalk system can consume it just fine and parse it correctly and build it correctly.

    <AK4>

    <AK41>

    <AK41.1>2</AK41.1>

    <AK41.3>1</AK41.3>

    </AK41>

    <AK42 />

    <AK43>1</AK43>

    </AK4>

    Thursday, November 9, 2017 5:53 PM
  • Well, based on that, the EDI seems correct.

    Are you sure you and the partner have matching expectations on the use of the Repetition Separator?

    Seems they are not setup correctly to handle it.  Either because their ISA11 usage is set wrong or they are not properly resolving the Agreement.

    Thursday, November 9, 2017 5:59 PM
  • Here is the settings I have defined, I'm not using the repetition separator, but it looks like it is using it for the 997.  I have checked in the logs and when the 997 gets created it is using this defined party.


    Thursday, November 9, 2017 6:15 PM