none
Invalid character in data element-Biztalk 2013 RRS feed

  • Question

  • I am using Biztalk 2013, i want to process a file received from partner EDI To XML(843). I received following file as below:-

    REF~QU~N //I received QU value in received file for REF01 and this value is mentioned in collection for REF01, still biztalk is generating following error

    Note:-I even change the Base data type to xs:string from X12_AN

    Error: 1 (Field level error)
        SegmentID: REF
        Position in TS: 5
        Data Element ID: REF01
        Position in Segment: 1
        Data Value:
        6: Invalid character in data element

    Secondly almost same error is is N1 loop

    N1~S8~PUBLIC SERV N C~29~42222//i received this value in N102

    Note:-I even change the Base data type to xs:string

    Error: 3 (Field level error)
        SegmentID: N1
        Position in TS: 22
        Data Element ID: N102
        Position in Segment: 2
        Data Value:
        6:Invalid character in data element

    Help me to solve this issue.it's urgent

    Thanks in advance

    Thursday, January 23, 2014 5:58 AM

Answers

  • This specific error is most often caused by not having the ISA11 usage setting correct in the Agreement.

    If the Trading Partner is sending 'U' in ISA11, the setting must be Standard Identifier.

    If it is set to Repetition Separator, the EDI Disassembler will interpret the 'U' as the Repetition Separator and will consider it an invalid character in no-repeating sub-elements.

    • Marked as answer by Gagz Thursday, October 30, 2014 8:20 AM
    Tuesday, September 9, 2014 11:18 AM

All replies

  • Hi Gag,

    1.Create a new custom receive pipeline
    2.Add the XmlDisassembler to the pipeline and configure it to your need.
    3.Add the FixEncodingComponent to the pipeline in the Decode stage, so that it is run before the XmlDisassembler.
    4.Set the Encoding parameter of the component in the Property Explorer to the encoding you want to use. To make this easier, the component implements a custom
     UITypeEditor that pops up a list of all the encodings supported by the .NET framework:

    For encoding Component you can visit

    http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample

    Thanks

    Abhishek


    Thursday, January 23, 2014 2:37 PM
  • Try adding the value 'QU' in the Enumeration Collection of your validation schema.

    Make sure that you make tihs change in correct REF segment as there are multiple REF's in EDI 834 (which you mentioned as EDI To XML(843) by  mistake.

    Friday, January 24, 2014 4:29 AM
  • Hi Prabhdeep,


    The Schema i am dealing with ie 843 is already having 'QU' in collection still it is giving error as mentioned above.

    Thanks

    Friday, January 24, 2014 5:18 AM
  • I hope you don't mind my jumping on this thread - I'm experiencing a similar issue.  We receive EDI data from many partners, some of which is sent from them with invalid data.  Our organization does not force strict compliance to the X12 standard, so we accept the data and process it.  We are converting to BizTalk 2013, and I'm now getting suspended messages due to validation errors.  Is it possible to turn off this validation?  I've checked the X12ConditionDesignator_Check in the schema to be sure it's 'No' and have the Validate EDI in my pipeline set to false, but BizTalk insists on validating, which results in suspended messages.

    Any thoughts?

    Wednesday, April 9, 2014 3:42 PM
  • Hi Gagz,

    In my case it was an issue in a separate segment not being populated (CTT02) correctly.  Check the other segments validation properties above and below the segment in question.

    Tuesday, September 9, 2014 4:55 AM
  • This specific error is most often caused by not having the ISA11 usage setting correct in the Agreement.

    If the Trading Partner is sending 'U' in ISA11, the setting must be Standard Identifier.

    If it is set to Repetition Separator, the EDI Disassembler will interpret the 'U' as the Repetition Separator and will consider it an invalid character in no-repeating sub-elements.

    • Marked as answer by Gagz Thursday, October 30, 2014 8:20 AM
    Tuesday, September 9, 2014 11:18 AM