none
Invalid character found RRS feed

  • Question

  • I have a edifact content.  DELFOR D97A

    I can confirm the error is 21.

    I think it is letter Sensitive issues, but I don't how to handle it?

    How can I fix it?

    thanks

    appear erros follow:

    Error: 1 (Field level error)
    SegmentID: NAD
    Position in TS: 5
    Data Element ID: C05803
    Position in Segment: 4
    Position in Field: 3
    Data Value: Fiscally Represented by
    21: Invalid character found


    Thursday, January 30, 2014 2:56 AM

Answers

  • I have a edifact content.  DELFOR D97A

    I can confirm the error is 21.

    I think it is letter Sensitive issues, but I don't how to handle it?

    How can I fix it?

    thanks

    appear erros follow:

    Error: 1 (Field level error)
    SegmentID: NAD
    Position in TS: 5
    Data Element ID: C05803
    Position in Segment: 4
    Position in Field: 3
    Data Value: Fiscally Represented by
    21: Invalid character found


    Check which element in data is causing trouble? Then check you schema, and collection for that element if it allows such elements or only specific values/format etc.

    For fixing, try run the file by removing invalid character to see if it goes through. Ask the sender of file if they can replace it with something and send a correct value/format

    • Marked as answer by Pengzhen Song Friday, February 7, 2014 8:00 AM
    Thursday, January 30, 2014 9:31 AM

All replies

  • I have a edifact content.  DELFOR D97A

    I can confirm the error is 21.

    I think it is letter Sensitive issues, but I don't how to handle it?

    How can I fix it?

    thanks

    appear erros follow:

    Error: 1 (Field level error)
    SegmentID: NAD
    Position in TS: 5
    Data Element ID: C05803
    Position in Segment: 4
    Position in Field: 3
    Data Value: Fiscally Represented by
    21: Invalid character found


    Check which element in data is causing trouble? Then check you schema, and collection for that element if it allows such elements or only specific values/format etc.

    For fixing, try run the file by removing invalid character to see if it goes through. Ask the sender of file if they can replace it with something and send a correct value/format

    • Marked as answer by Pengzhen Song Friday, February 7, 2014 8:00 AM
    Thursday, January 30, 2014 9:31 AM
  • You will have to open the original EDI and go the that NAD segment and look at the data.

    You should use a good text editor like Notepad++ or even the Visual Studio binary viewer in case it's a non-printable character.

    The characters sets for EDI are pretty limited so if the Trading Partner is sending a truly invalid character, technically, you should be reject the interchange.

    However, you could adjust the EDI validation level in the agreement.  It depends on what the character is also.

    Thursday, January 30, 2014 1:13 PM
  • Check the EDIFACT encoding (found in the UNB segment).

    It seems to me that if "Fiscally Represented by" is invalid, then UNOA is used (where only capitalized letters A-Z are allowed). 

    I would suggest changing the encoding to UNOC (if you are sending you can change this in the Agreements), and if you are receiving you would need the sender to change UNOA to UNOC.

    Morten la Cour

    Thursday, January 30, 2014 1:31 PM