none
Integration - Decode EDIFACT - Transaction Set or Group Control Number Mismatch RRS feed

  • Question

  • Note, doing this in an Azure Logic App, but hoping to maybe get faster feedback here.

    Trying to decode an EDIFACT IFTSTA D96b file from a partner, receiving the error below. Have tried altering the UNT value without success.

    "Error encountered during parsing. The Edifact transaction set with id '409400001' contained in functional group with id '4094', in interchange with id '4095', with sender id '{SENDER}', receiver id '{RECEIVER}' is being suspended with following errors:
    Error: 1 (Miscellaneous error)
    70: Error: 2 (Miscellaneous error)
    71: Transaction Set or Group Control Number Mismatch
    Error: 3 (Miscellaneous error)
    29: Invalid count specified at interchange, group, or message levels"

    Flatfile:
    UNA:+.? 'UNB+UNOA:1+{removed}:ZZZ+{removed}:ZZZ+171003:0138+4095'UNG+IFTSTA+{removed}+{removed}+171003:0138+4094+UN+D:96B'UNH+409400001+IFTSTA:D:96B:UN'BGM+44'DTM+184:20171003013824-05:303'TSR+++3+11'RFF+ACL:0013000059'RFF+AGR:085'RFF+AAZ:DNZA'RFF+AF:CX'RFF+AWB:2TO8132'RFF+AHC:NA'LOC+5+SJU:::SAN JUAN, PR+Z4'LOC+8+ICN:::INCHEON, KOREA+Z4'FTX+AAB++INCO-TERM+CPT:INCHEON AIRPORT'FTX+PMD+++A'CNI+1'CNT+9:1'STS+1+21:::DPTD+62:::AIRC+62:::NOAP+62:::NOAP+62:::NOAP'RFF+IL:0013000059_2017SEP28_SAPQ96US'DTM+171:201710021255-04:303'NAD+IM+{removed}+++NONE+SEOCHO-GU,SEOUL+00++KR'NAD+FW+23637+{removed}+++{removed}+PA'EQD+ULD'MEA+WT+AAB+LBS:68.5'MEA+WT+G+KGS:31.1'MEA+VOL+AAW+I:000000015625'UNT+26+409400001'UNE+1+4094'UNZ+1+4095'


    Microsoft Community Contributor Docker Accredited Consultant MCSD: Web Apps MCPD: Windows Azure Developer


    • Edited by Andy Badera Friday, October 13, 2017 7:48 PM
    Friday, October 13, 2017 7:31 PM

Answers

  • Schema settings in the EDIFACT agreement needed some additional info. In our case, it now looks like this, and everything decodes fine:

    IFTSTA
    D
    96B
    UNG2.1
    ZZZ
    EFACT_D96B_IFTSTA



    And validations:

    Default
    true
    false
    false
    false
    NotAllowed
    IFTSTA
    false
    false
    false
    false
    Optional

    Microsoft Community Contributor Docker Accredited Consultant MCSD: Web Apps MCPD: Windows Azure Developer



    • Marked as answer by Andy Badera Tuesday, October 17, 2017 12:49 PM
    • Edited by Andy Badera Tuesday, October 17, 2017 12:52 PM
    Tuesday, October 17, 2017 12:48 PM

All replies

  • Basically, the counts in any of the Trailer values (UNT1, UNE1 or UNZ1) are incorrect in the sample.

    Refer:

    https://social.msdn.microsoft.com/Forums/en-US/60a1ceeb-3237-426a-a759-fe30b0181488/error-receiving-edifact-file?forum=biztalkediandas2


    Thanks Arindam


    Monday, October 16, 2017 1:52 AM
    Moderator
  • Hi Andy,

    I also get the error.

    Took multiple live production messages, which can be received and validated on BizTalk 2013 R3 and BizTalk 2016, uploaded the EDIFACT schema to a Logic app, and they all fail with the error

    "exception": "Error encountered during parsing. The Edifact transaction set with id '1' contained in interchange (without group) with id '0540263064', with sender id '9999999999999', receiver id '9999999999998' is being suspended with following errors:\r\nError: 1 (Miscellaneous error)\r\n\t70: \r\n\r\nError: 2 (Miscellaneous error)\r\n\t71: Transaction Set or Group Control Number Mismatch\r\n\r\nError: 3 (Miscellaneous error)\r\n\t29: Invalid count specified at interchange, group, or message levels\r\n\r\n",

    Have also tried to disable all EDI validation on the Integration account agreement, but it makes no difference.

    Best regards

    Rasmus Jaeger

    Monday, October 16, 2017 1:15 PM
  • Nope on UNT/UNE/UNZ.

    Microsoft Community Contributor Docker Accredited Consultant MCSD: Web Apps MCPD: Windows Azure Developer


    • Edited by Andy Badera Tuesday, October 17, 2017 12:53 PM
    Tuesday, October 17, 2017 12:47 PM
  • Schema settings in the EDIFACT agreement needed some additional info. In our case, it now looks like this, and everything decodes fine:

    IFTSTA
    D
    96B
    UNG2.1
    ZZZ
    EFACT_D96B_IFTSTA



    And validations:

    Default
    true
    false
    false
    false
    NotAllowed
    IFTSTA
    false
    false
    false
    false
    Optional

    Microsoft Community Contributor Docker Accredited Consultant MCSD: Web Apps MCPD: Windows Azure Developer



    • Marked as answer by Andy Badera Tuesday, October 17, 2017 12:49 PM
    • Edited by Andy Badera Tuesday, October 17, 2017 12:52 PM
    Tuesday, October 17, 2017 12:48 PM