none
820 005010x306 RRS feed

  • Question

  • Hi,

    I have deployed new 820 (005010X306)version schema and when i try to process it edi receive pipeline giving this error 

    A message received by adapter "FILE" on receive location "Receive Location" with URI " " is suspended. 
     Error details: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error: 
         Functional Group Error Information

    Sequence No: 1
    Functional Id: RA
    Control Number: 1



    Transaction Set Errors

    Sequence No: 1
    TS Id code: 820
    Control Number: 1001

    Error: 1 (Segment level error)
    SegmentID: ST
    Position in TS: 1
    8: Segment Has Data Element Errors

    Error: 2 (Field level error)
    SegmentID: ST
    Position in TS: 1
    Data Element ID: ST03_ImplementationConventionReference
    Position in Segment: 3
    Data Value: 005010X306
    7: Invalid code value

    Error: 3 (Segment level error)
    SegmentID: BPR
    Position in TS: 2
    8: Segment Has Data Element Errors

    Error: 4 (Field level error)
    SegmentID: BPR
    Position in TS: 2
    Data Element ID: BPR10_PayerIdentifier
    Position in Segment: 10
    Data Value: 
    1: Mandatory data element missing

    Error: 5 (Segment level error)
    SegmentID: N1
    Position in TS: 5
    3: Mandatory Segment Missing

    Error: 6 (Segment level error)
    SegmentID: N1
    Position in TS: 5
    2: Unexpected segment

    Error: 7 (Field level error)
    SegmentID: N1
    Position in TS: 5
    Data Element ID: N101_EntityIdentifierCode
    Position in Segment: 1
    Data Value: RM
    7: Invalid code value

    Error: 8 (Field level error)
    SegmentID: N1
    Position in TS: 5
    Data Element ID: N103_IdentificationCodeQualifier
    Position in Segment: 3
    Data Value: 58
    7: Invalid code value

    Error: 9 (Segment level error)
    SegmentID: ENT
    Position in TS: 7
    8: Segment Has Data Element Errors

    Error: 10 (Field level error)
    SegmentID: ENT
    Position in TS: 7
    Data Element ID: ENT02_EntityIdentifierCode
    Position in Segment: 2
    Data Value: 
    1: Mandatory data element missing

    Error: 11 (Segment level error)
    SegmentID: NM1
    Position in TS: 8
    8: Segment Has Data Element Errors

    Error: 12 (Field level error)
    SegmentID: NM1
    Position in TS: 8
    Data Element ID: NM108_IdentificationCodeQualifier
    Position in Segment: 8
    Data Value: C1
    7: Invalid code value

    Error: 13 (Segment level error)
    SegmentID: REF
    Position in TS: 10
    8: Segment Has Data Element Errors

    Error: 14 (Field level error)
    SegmentID: REF
    Position in TS: 10
    Data Element ID: REF01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: POL
    7: Invalid code value

    Error: 15 (Segment level error)
    SegmentID: RMR
    Position in TS: 11
    8: Segment Has Data Element Errors

    Error: 16 (Field level error)
    SegmentID: RMR
    Position in TS: 11
    Data Element ID: RMR01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: ZZ
    7: Invalid code value

    Error: 17 (Segment level error)
    SegmentID: REF
    Position in TS: 12
    8: Segment Has Data Element Errors

    Error: 18 (Field level error)
    SegmentID: REF
    Position in TS: 12
    Data Element ID: REF01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: 0N
    7: Invalid code value

    Error: 19 (Segment level error)
    SegmentID: DTM
    Position in TS: 13
    8: Segment Has Data Element Errors

    Error: 20 (Field level error)
    SegmentID: DTM
    Position in TS: 13
    Data Element ID: DTM01_DateTimeQualifier
    Position in Segment: 1
    Data Value: 582
    7: Invalid code value

    Error: 21 (Field level error)
    SegmentID: DTM
    Position in TS: 13
    Data Element ID: DTM02_PayerProcessDate
    Position in Segment: 2
    Data Value: 
    1: Mandatory data element missing

    Error: 22 (Segment level error)
    SegmentID: RMR
    Position in TS: 14
    8: Segment Has Data Element Errors

    Error: 23 (Field level error)
    SegmentID: RMR
    Position in TS: 14
    Data Element ID: RMR01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: ZZ
    7: Invalid code value

    Error: 24 (Segment level error)
    SegmentID: REF
    Position in TS: 15
    8: Segment Has Data Element Errors

    Error: 25 (Field level error)
    SegmentID: REF
    Position in TS: 15
    Data Element ID: REF01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: 0N
    7: Invalid code value

    Error: 26 (Segment level error)
    SegmentID: DTM
    Position in TS: 16
    8: Segment Has Data Element Errors

    Error: 27 (Field level error)
    SegmentID: DTM
    Position in TS: 16
    Data Element ID: DTM01_DateTimeQualifier
    Position in Segment: 1
    Data Value: 582
    7: Invalid code value

    Error: 28 (Field level error)
    SegmentID: DTM
    Position in TS: 16
    Data Element ID: DTM02_PayerProcessDate
    Position in Segment: 2
    Data Value: 
    1: Mandatory data element missing

    Error: 29 (Segment level error)
    SegmentID: ENT
    Position in TS: 17
    8: Segment Has Data Element Errors

    Error: 30 (Field level error)
    SegmentID: ENT
    Position in TS: 17
    Data Element ID: ENT02_EntityIdentifierCode
    Position in Segment: 2
    Data Value: 
    1: Mandatory data element missing

    Error: 31 (Segment level error)
    SegmentID: NM1
    Position in TS: 18
    8: Segment Has Data Element Errors

    Error: 32 (Field level error)
    SegmentID: NM1
    Position in TS: 18
    Data Element ID: NM108_IdentificationCodeQualifier
    Position in Segment: 8
    Data Value: C1
    7: Invalid code value

    Error: 33 (Segment level error)
    SegmentID: REF
    Position in TS: 20
    8: Segment Has Data Element Errors

    Error: 34 (Field level error)
    SegmentID: REF
    Position in TS: 20
    Data Element ID: REF01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: POL
    7: Invalid code value

    Error: 35 (Segment level error)
    SegmentID: RMR
    Position in TS: 21
    8: Segment Has Data Element Errors

    Error: 36 (Field level error)
    SegmentID: RMR
    Position in TS: 21
    Data Element ID: RMR01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: ZZ
    7: Invalid code value

    Error: 37 (Segment level error)
    SegmentID: REF
    Position in TS: 22
    8: Segment Has Data Element Errors

    Error: 38 (Field level error)
    SegmentID: REF
    Position in TS: 22
    Data Element ID: REF01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: 0N
    7: Invalid code value

    Error: 39 (Segment level error)
    SegmentID: DTM
    Position in TS: 23
    8: Segment Has Data Element Errors

    Error: 40 (Field level error)
    SegmentID: DTM
    Position in TS: 23
    Data Element ID: DTM01_DateTimeQualifier
    Position in Segment: 1
    Data Value: 582
    7: Invalid code value

    Error: 41 (Field level error)
    SegmentID: DTM
    Position in TS: 23
    Data Element ID: DTM02_PayerProcessDate
    Position in Segment: 2
    Data Value: 
    1: Mandatory data element missing

    Error: 42 (Segment level error)
    SegmentID: RMR
    Position in TS: 24
    8: Segment Has Data Element Errors

    Error: 43 (Field level error)
    SegmentID: RMR
    Position in TS: 24
    Data Element ID: RMR01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: ZZ
    7: Invalid code value

    Error: 44 (Segment level error)
    SegmentID: REF
    Position in TS: 25
    8: Segment Has Data Element Errors

    Error: 45 (Field level error)
    SegmentID: REF
    Position in TS: 25
    Data Element ID: REF01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: 0N
    7: Invalid code value

    Error: 46 (Segment level error)
    SegmentID: DTM
    Position in TS: 26
    8: Segment Has Data Element Errors

    Error: 47 (Field level error)
    SegmentID: DTM
    Position in TS: 26
    Data Element ID: DTM01_DateTimeQualifier
    Position in Segment: 1
    Data Value: 582
    7: Invalid code value

    Error: 48 (Field level error)
    SegmentID: DTM
    Position in TS: 26
    Data Element ID: DTM02_PayerProcessDate
    Position in Segment: 2
    Data Value: 
    1: Mandatory data element missing

    Error: 49 (Segment level error)
    SegmentID: RMR
    Position in TS: 27
    8: Segment Has Data Element Errors

    Error: 50 (Field level error)
    SegmentID: RMR
    Position in TS: 27
    Data Element ID: RMR01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: ZZ
    7: Invalid code value

    Error: 51 (Segment level error)
    SegmentID: REF
    Position in TS: 28
    8: Segment Has Data Element Errors

    Error: 52 (Field level error)
    SegmentID: REF
    Position in TS: 28
    Data Element ID: REF01_ReferenceIdentificationQualifier
    Position in Segment: 1
    Data Value: 0N
    7: Invalid code value

    Error: 53 (Segment level error)
    SegmentID: DTM
    Position in TS: 29
    8: Segment Has Data Element Errors

    Error: 54 (Field level error)
    SegmentID: DTM
    Position in TS: 29
    Data Element ID: DTM01_DateTimeQualifier
    Position in Segment: 1
    Data Value: 582
    7: Invalid code value

    Error: 55 (Field level error)
    SegmentID: DTM
    Position in TS: 29
    Data Element ID: DTM02_PayerProcessDate
    Position in Segment: 2
    Data Value: 
    1: Mandatory data element missing.
     The sequence number of the suspended message is 1.  
     MessageId:  {2B543A52-9334-4AB4-902D-9D77E8AEA38C}
     InstanceID: {AC521AA2-553D-4987-ACC5-09B0ABBE9F50}

    Thanks 

    Tuesday, January 28, 2014 4:16 PM

Answers

  • In that case:

    1. Make sure the new schema is Deployed

    2. Restart the Host Instances

    3. If the Agreement has change, make sure the Local Host Settings match the new schema.  Because of Error 2, it seems like the Disassembler is resolving to an older version.

    4. If you're not using them, disable the Fallback Settings.

    • Marked as answer by Sam_biz Tuesday, January 28, 2014 10:17 PM
    Tuesday, January 28, 2014 9:47 PM

All replies

  • Hi,

    Message you received is failed to parse. If you used any custom schema make sure its deployed and set schema in party settings.

    Tuesday, January 28, 2014 8:41 PM
  • You should resolve these issues in Visual Studio before deploying.  The schema errors are often more helpful than the EDI versions.
    Tuesday, January 28, 2014 9:15 PM
  • Hi,

    In Visual studio it validated correctly.

    Its a new schema which is exported with CU2 updates for 2013.

    Thanks

    Tuesday, January 28, 2014 9:39 PM
  • In that case:

    1. Make sure the new schema is Deployed

    2. Restart the Host Instances

    3. If the Agreement has change, make sure the Local Host Settings match the new schema.  Because of Error 2, it seems like the Disassembler is resolving to an older version.

    4. If you're not using them, disable the Fallback Settings.

    • Marked as answer by Sam_biz Tuesday, January 28, 2014 10:17 PM
    Tuesday, January 28, 2014 9:47 PM