MessageError: [A59]: incoming file has not allowed characters at/after file-position

[Rajeev R]

The parser failed when there is a special charcter in the EDI file.

MessageError: [A59]: incoming file has not allowed characters at/after file-position 82: "1118~2344~¨~00501~000063425~0~P~>|GS~MZ~UPSN~A".

So I have replaced the  ¨ with ^ symbol and parsed successfully.

I got the same issue for the : colon character too.

Is this the correct way to avoid the error due to "not allowed characters"?
Is there any way to predefine those characters and parse the document?
Is this characters are allowed in x12 files?

Please help.

[henk-jan ebbers]

normally this has to do with non-ascii characters.
(x12 usually is ascii only.)

the ':' is unlikly to be the cause.
use a decent editor, try to find out what is in the file.
error says it is at position 82; this is fairly accurate.

kind regards,
henk-jan

On 11/21/2014 10:32 AM, Rajeev R wrote:
> The parser failed when there is a special charcter in the EDI file.
>

> MessageError: [A59]: incoming file has not allowed characters at/after file-position 82: "1118~2344~*¨*~00501~000063425~0~P~>|GS~MZ~UPSN~A".
>
>
> So I have replaced the *¨*with ^ symbol and parsed successfully.

>
> I got the same issue for the : colon character too.
>
> Is this the correct way to avoid the error due to "not allowed characters"?
> Is there any way to predefine those characters and parse the document?
> Is this characters are allowed in x12 files?
>
> Please help.

> --
> You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to botsmail+u...@googlegroups.com <mailto:botsmail+u...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

[Rajeev R]

¨ this is the character. I have opned the edi file in vi editor and found this character at 83 rd position. So what should I do now to get it working on bots without replacing the character?

[henk-jan ebbers]

what charset is it? often used are eg ISO-8859-1; utf-8
(ascii is ONLY the first 128 characters.)
as they use this in ISA header it is probably somthing like ISO-8859-1

for me, I would always contact the edi-partner, and ask if this is really what they want, etc. It is not very common.

in file bots/usersys/grammars/x12/x12.py
there is a syntax section.
indicate here the syntax set used.

kind regards,
henk-jan

> > To unsubscribe from this group and stop receiving emails from it, send an email to botsmail+u...@googlegroups.com <javascript:> <mailto:botsmail+u...@googlegroups.com <javascript:>>.
> > For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.

[Rajeev R]

ANSI 210/4030


syntax = {
        'version'    :  '00403',
        }
~         

[henk-jan ebbers]

that is not the character st.
see eg http://en.wikipedia.org/wiki/Charset

kind regards,
henk-jan

> > > For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout> <https://groups.google.com/d/optout <https://groups.google.com/d/optout>>.

[Rajeev R]

text/plain; charset=iso-8859-1

[Rajeev R]

I have one more file which is giving error

character set details - application/octet-stream; charset=binary

110/4060 transaction set.

Error is

Message nr 2, type 110004060, [F17] line 1 pos 91551: Record "ST-LX-N1-N2" expect field but " BARBARA REESE" is a subfield.

in Edi,

N2*ATTN: BARBARA REESE

When I replace the : colon character,  error goes.

[henk-jan ebbers]

this sounds like errors in the incoming x12 files.
check this with you edi-partner.
(in ISA-header, indicate ':' to be the sub-field delimiter.
but than they use this in the data...

kind regards,
henk-jan

On 11/21/2014 02:34 PM, Rajeev R wrote:
>
> I have one more file which is giving error
>
> character set details - application/octet-stream; charset=binary
>
> 110/4060 transaction set.
>
> Error is
>
> Message nr 2, type 110004060, [F17] line 1 pos 91551: Record "ST-LX-N1-N2" expect field but " BARBARA REESE" is a subfield.
>
>
> in Edi,
>
> N2*ATTN: BARBARA REESE
>
>
> When I replace the : colon character, error goes.
>
>
> On Friday, 21 November 2014 18:42:59 UTC+5:30, Rajeev R wrote:
>
> text/plain; charset=iso-8859-1
>
>
> On Friday, 21 November 2014 17:50:56 UTC+5:30, eppye wrote:
>
> that is not the character st.

> see eg http://en.wikipedia.org/wiki/Charset <http://en.wikipedia.org/wiki/Charset>

> > > For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout> <https://groups.google.com/d/optout <https://groups.google.com/d/optout>>.

[Rajeev R]

So that means, the colon : character is only allowed in ISA header not in other segments. To parse them we must contact the edi partner to provide colon removed edi. Bots can not handle it. ok

The earlier file (charset=iso-8859-1) has a character ¨  in the ISA header. which also should get removed. Bots can not handle that too. ok.

[henk-jan ebbers]

On 11/21/2014 02:50 PM, Rajeev R wrote:
> So that means, the colon : character is only allowed in ISA header not in other segments. To parse them we must contact the edi partner to provide colon removed edi. Bots can not handle it. ok

no.
problem is: Bots handles this OK. Your edi-partner does not, and send incorrect X12 files.

>
> The earlier file (charset=iso-8859-1) has a character ¨ in the ISA header. which also should get removed. Bots can not handle that too. ok.

bots handles that. Do NOT remove that character.
Normal charset for X12 is us-ascii.
Probably you need to use iso-8859-1 (as explained in previous emails).

(unless I am mistaken, you have never used x12 before. so this all might be confusing. check first if these are indeed the x12 files from your partner. NOT copy-parse from documentation. etc etc)


kind regards,
henk-jan

>
>
>
> On Friday, 21 November 2014 19:11:07 UTC+5:30, eppye wrote:
>
> this sounds like errors in the incoming x12 files.
> check this with you edi-partner.
> (in ISA-header, indicate ':' to be the sub-field delimiter.
> but than they use this in the data...
>
> kind regards,
> henk-jan
>
> On 11/21/2014 02:34 PM, Rajeev R wrote:
> >
> > I have one more file which is giving error
> >
> > character set details - application/octet-stream; charset=binary
> >
> > 110/4060 transaction set.
> >
> > Error is
> >
> > Message nr 2, type 110004060, [F17] line 1 pos 91551: Record "ST-LX-N1-N2" expect field but " BARBARA REESE" is a subfield.
> >
> >
> > in Edi,
> >
> > N2*ATTN: BARBARA REESE
> >
> >
> > When I replace the : colon character, error goes.
> >
> >
> > On Friday, 21 November 2014 18:42:59 UTC+5:30, Rajeev R wrote:
> >
> > text/plain; charset=iso-8859-1
> >
> >
> > On Friday, 21 November 2014 17:50:56 UTC+5:30, eppye wrote:
> >
> > that is not the character st.

> > see eg http://en.wikipedia.org/wiki/Charset <http://en.wikipedia.org/wiki/Charset> <http://en.wikipedia.org/wiki/Charset <http://en.wikipedia.org/wiki/Charset>>

> > > For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout> <https://groups.google.com/d/optout <https://groups.google.com/d/optout>>.

> >
> > --
> > You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to botsmail+u...@googlegroups.com <javascript:> <mailto:botsmail+u...@googlegroups.com <javascript:>>.