on 04-11-2007 6:32 AM
Hi,
I have configured File(FTP) - > File(FTP) Scenario.
I am expecting a Chinese File from Source system which is AS400. I am using the file encoding format UTF-8 while the chinese characters are in GB2312 format. My sender file adapter picks up the file correctly, but SXMB_MONI gives Mapping related Parser error. Kindly Suggest.
Do i need to change some character set or code page? if yes, where should it be done?
Thanks Charu.
Thanks Stefan,
The file was corrupt.
It worked fine.
Kind Regards,
Charu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good to hear.
I learned a lot with this question
I put my learnings in this how-to guide:
I hope, this is helpful.
Regards
Stefan
Hi,
In the sender file adapter change the file encoding Scheme.
Make the file type as text and then make the encoding as ,
US-ASCII or ISO-8859-1.
Let us know if this does the trick.
Also check the other encodingh schemes in thsi link,
http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
Regards
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i guess maybe even providing the encoding as GB2312 should work !!! Just give it a try and let us know.
The files that you provided are not chinese, the might be japanese (JIS).
I am not sure what codepage is behind, but it is definitively not GB2312.
To verify, that you have a japanese text, open the file with Word. Word will ask for the correct codepage. When you walk through all codepages, you will see that JIS is the only one, that provides a correct text.
Make sure, what language you really have and what codepage it should be and apply this codepage in the file adapter.
Regards
Stefan
Hi Stefan,
You are right, I noticed it, but the problem is that when these files are opened on AS400(FTP) server, they show Chinese characters with codepage GB2312.
But when I download the file from FTP server to my local machine, I am not able to see the Chinese character. Also in SXMB_MONI, the inbound xml shows Chinese characters, but i continue to get the parser error from Mapping.
Regards,
Charu
Yeah, the files shows casually some chinese characters. But it is definitively not GB2312.
When you opne the file with a hex editor, you see the foreign characters like this:
0E 24 36 5D 5B B1 DC AF 30 5B B9 A8 3B 5D D4 A8 43 A9 3F 0F
0E and 0F are ASCII signs for shift-in and shift-out. These signs cause the trouble in mapping.
Then you have a sequence that looks like:
$6][卤脺炉0[鹿篓;]脭篓C漏? (GB2312)
This is to random to be real chinese. Could you check, if the file is corrupted by the FTP? Compare the files with a hex editor.
Regards
Stefan
Actually in AS400 they are having CCSID which is 935. This CCSID is compatible with GB2312.
Customer has given this file to me. He has downloaded that file in outbound library of FTP Server. Through my scenario I am accessing this file.
I dont have any idea about this file.As per customer it is correct file.
I think AS400 is able to generate the chinese file but FTP server is having some problem while accessing the file. Do we need to specify any attribute in configuration of FTP server?
Warm Regards,
Charu
I don't think that the FTP server causes the trouble. The CCSID 935 is a double codepage. The 0E and 0F switch the codepage.
http://www-03.ibm.com/servers/eserver/iseries/software/globalization/ccsid/00935.htm
When it is say, that the codepage is compatible to GB2312, that only means, that the signs are the same, but not that the hex code of the signs is the same.
I think you have to apply the conversion routines from CCSID 935 to UTF-8.
Maybe you could ask, if you could receive the file in GB2312 or in UTF-8.
I cannot help you here further, because I have not worked with AS400 so far and I do not know how to install the conversion routines on the XI server.
Regards
Stefan
Hi,
Under File Encoding, specify a code page.
The default setting is to use the system code page that is specific to the configuration of the installed operating system. The file content is converted to the UTF-8 code page before it is sent.
Permitted values for the code page are the existing charsets of the Java runtime. According to the SUN specification for the Java runtime, at least the following standard character sets must be supported:
US-ASCII
Seven-bit ASCII, also known as ISO646-US, or Basic Latin block of the Unicode character set
ISO-8859-1
ISO character set for Western European languages (Latin Alphabet No. 1), also known as ISO-LATIN-1
UTF-8
8-Bit Unicode Character Format
UTF-16BE
16-bit Unicode character format, big-endian byte order
UTF-16LE
16-bit Unicode character format, little-endian byte order
UTF-16
16-bit Unicode character format, byte order
Check which other character sets are supported in the documentation for your Java runtime implementation.
XML text documents generally contain their own code page description and should be treated as binary data type.
If it is not there the you need write the Adapter module for sender side .
Or you can use the XSLT mapping using CDATA.
see the below link
http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
Regards
Chilla
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.