none
Invalid character found RRS feed

  • Question

  • I have a edifact content.  ORDERS D97A

    I can confirm the error is 7".

    How can I fix it?

    thanks


    appear erros follow:

    Error: 1 (Field level error)
     SegmentID: LIN
     Position in TS: 9
     Data Element ID: C21201
     Position in Segment: 4
     Position in Field: 1
     Data Value: BZX84C5V6 T/R 7"
     21: Invalid character found

    K.D. Chen
    Monday, August 10, 2009 2:32 AM

Answers

  • Hi,
        Here UNB1.1 is UNOA that is your encoding type. And UNOA encoding allows :
    • A to Z
    • 0 to 9
    • . , – ( ) / = (space)
    It does not allow " . So pipeline is throwing error "Invalid character found.

    Following is the list of encoding and their descriptions:

    UNOA allows:

    • A to Z
    • 0 to 9
    • . , – ( ) / = (space)

    UNOB allows:

    • All of UNOA
    • a to z
    • ‘ + : ? ! ” % & * ; < >

    UNOC allows:

    • ISO 8859 character set

    UNOD-UNOK allows:

    • All of UNOA-UNOC
    • All of UTF8 characters

    UNOX allows:

    • ISO 50220 character set
      • This code page allows the escape techniques in accordance with ISO 2375. The text starts in ASCII and switches to Japanese characters through an escape sequence. The bytes following the escape sequence are encoded in two bytes each

     KECA allows:

    • A to Z
    • 0 to 9
    • . , – ( ) / = ! ” % & * ; < >
    • Windows 949 code page
      • Korean Syllables (2350 characters)
      • Korean Hanja (4888 characters)
      • Korean Alphabets
      • Characters and numbers enclosed in a circle
      • The length of the strings are counted by byte instead of characters. So if you have a data element of length 3, you can have 3 latin characters, 1 Korean character or 1 Korean and 1 Latin character!


    For this document I think you should use UNOB encoding as UNB1.1


    Thanks
    Gyan


    If this answers your question, please mark it as "Answered".
    • Proposed as answer by KD Chen Tuesday, August 11, 2009 6:33 AM
    • Marked as answer by Andrew_ZhuModerator Monday, August 17, 2009 7:24 AM
    Monday, August 10, 2009 9:50 AM

All replies

  • Hi,
       Which encoding are you using. And validate that according to that encoding is this data element is right?

    Please provide the file here or at least UNB segment.


    Thanks
    Gyan
    If this answers your question, please mark it as "Answered".
    Monday, August 10, 2009 8:47 AM
  • Dear Gyan:

    Can you tell me where is the encoding configration ?

    My content is follow:

    UNA:+.? '
    UNB+UNOA:1+SENDER:ZZZ+RECEIVER:ZZZ+081106:2124+6++ORDERS++++1'
    UNH+1+ORDERS:D:97A:UN:EDPO04'

    Thanks,
    K.D. Chen
    K.D. Chen
    Monday, August 10, 2009 9:38 AM
  • Hi,
        Here UNB1.1 is UNOA that is your encoding type. And UNOA encoding allows :
    • A to Z
    • 0 to 9
    • . , – ( ) / = (space)
    It does not allow " . So pipeline is throwing error "Invalid character found.

    Following is the list of encoding and their descriptions:

    UNOA allows:

    • A to Z
    • 0 to 9
    • . , – ( ) / = (space)

    UNOB allows:

    • All of UNOA
    • a to z
    • ‘ + : ? ! ” % & * ; < >

    UNOC allows:

    • ISO 8859 character set

    UNOD-UNOK allows:

    • All of UNOA-UNOC
    • All of UTF8 characters

    UNOX allows:

    • ISO 50220 character set
      • This code page allows the escape techniques in accordance with ISO 2375. The text starts in ASCII and switches to Japanese characters through an escape sequence. The bytes following the escape sequence are encoded in two bytes each

     KECA allows:

    • A to Z
    • 0 to 9
    • . , – ( ) / = ! ” % & * ; < >
    • Windows 949 code page
      • Korean Syllables (2350 characters)
      • Korean Hanja (4888 characters)
      • Korean Alphabets
      • Characters and numbers enclosed in a circle
      • The length of the strings are counted by byte instead of characters. So if you have a data element of length 3, you can have 3 latin characters, 1 Korean character or 1 Korean and 1 Latin character!


    For this document I think you should use UNOB encoding as UNB1.1


    Thanks
    Gyan


    If this answers your question, please mark it as "Answered".
    • Proposed as answer by KD Chen Tuesday, August 11, 2009 6:33 AM
    • Marked as answer by Andrew_ZhuModerator Monday, August 17, 2009 7:24 AM
    Monday, August 10, 2009 9:50 AM
  • Hi Gyan:

    After your reminders, I think of it.

    Thanks your reply.

    K.D. Chen
    Tuesday, August 11, 2009 6:39 AM