Chinese Characters in ABAP Mapping

Hi All,
I have one problem with chinese characters in ABAP Mapping. Actually there is an ABAP Mapping written in XI which converts IDoc to Idoc Flat file which is provided by SAP and is in the below link.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Chinese characters are properly coming to XI but after this ABAP mapping those characters are being replaced with #. Any idea on this pelase?
Regards,
Dinakar

Hi !
Check this thread:
Unable to get Chinese Characters as output.
Regards,
Matias
ps:please award points if helpful.

Similar Messages

Cyrillic characters issue in ABAP mapping

Hello Experts,
I am using ABAP mapping program to convert IDOC XML to flat file. Further i am using FIle adapter to write this file on FTP server.
My problem is:
When Idoc contains CYRILLIC characters in payload, then these characters appear as "#" after the mapping has executed.
If I check in SXMB_MONI in XI, the inbound payload displays data correctly. In "Request Message mapping" node, if I check the output of ABAP mapping program, then cyrillic characters are replaced with "#". The same "#" is then written to File.
Do you have any idea, how do i deal with this problem.
NOTE: I tried passing encoding type = UTF-8 to the function - SCMS_STRING_TO_XSTRING which is used the mapping program to set the encoding type, but it did not work.

@PI Expert: I tried to debug the ABAP mapping using SXI_MAPPING_TEST transaction, however when I paste my payload in the editor, the cyrillic characters appear as junk characters. Due to this, in the output, these junk characters are appear as "#"
@Sarvesh: I too initially thought that this could be problem with AL11, that it is not displaying the data correctly. However when I checked the "Request Message Mapping" node in SXMB_MONI, it showed "#" characters. Also the .csv file generated contains "#" only.
Thanks for your time and response.

How to set Encoding in ABAP Mapping

Hi All,
I have implemented ABAP Mapping in XI for converting Idoc into Idoc Flatfile which is provided by SAP and is in the below link.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
However after this mapping is taking place all chinese characters are being replaced by #.
So i want to explicitly set encoding in this ABAP Mapping. Can anybody please tell me where to set Encoding and how in this ABAP Code?
Regards,
Dinakar

Any help please. Urgent.
Regards,
Dinakar

Issue Regarding Chinese characters In Smart Form Print preview..

Hi All,
I am working on a smart form development for chinese users. The requirement is the user will login using English & when the delivery will be issued for output, a check will be done on the country of user. If that comes as china then the international version (C) maintained for that customer will come as output.
Now the problem is even if I login using EN or ZH the below issue I am facing always.
In the database I can view the details in chinese properly by logging in as ZH. During debugging also i checked the data from table ADRC & MAKT is coming in chinese properly. But when i gave the values to be output in SmartForm, it is showing the characters like how it will look if I login using EN & view the table contents.
When i view the data by changing character set as Simplified Chinese then in table i can see chinese texts properly. But when the same data goes to print preview it shows the chinese characters like as it would appear when character set is Unicode or West European..
Please help..
Thanks in advance.
Edited by: malayanayak123 on Jun 1, 2011 5:48 AM

Dear,
print preview and physical printout are two different things.
PrintPreview:
The data stream will be sent to the frontend and rendered with windows-fonts etc (for backend prints a simulation).
Printout:
Frontend: You need a printer, that maps the character, you have to use SAPWIN or SAPWINCF when using cascading fonts. The rendering will be done in the windows spooler.
Backend: Your printer needs also a mapping (look like something with UTF8). Also the printer needs the fonts installed because the rendering will be done in the printer!
If you use the pdf-printer in SAP, you need to upload all necessary fonts (TTF) for the pdf-composer. Also you need a unicode pdf printer for that.
Regards,
Christian

Problem with chinese characters while sending mail with .CSV attachment

Hi,
i am sendin .CSV file as an attachment with mail using "SO_DOCUMENT_SEND_API1" FM,
whle opening the mail attachment the chinese characters are not displaying properly.
currently i am using ECC 5.0
can any body help in this regard.
Thanks,
Rahim

Hi Kang Ring,
please convert the content of the attachement into the binary format and then add it as a mail attachment.
LOOP AT i_data ASSIGNING <wa_data>.
if s_output is INITIAL.
CONCATENATE <wa_data> cl_abap_char_utilities=>cr_lf into s_output.
else.
CONCATENATE s_output <wa_data> INTO s_output SEPARATED BY cl_abap_char_utilities=>cr_lf.
endif.
ENDLOOP.
CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
EXPORTING
text = s_output
IMPORTING
buffer = x_output.
CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
EXPORTING
buffer = x_output
TABLES
binary_tab = imail_att.
     OR
please use ABAP-Object classes like CL_BCS , CL_document_BCS.....
please findthe below sample code.
cl_bcs_convert=>string_to_solix(
          EXPORTING
            iv_string   = s_output
            iv_codepage = '4103'          "suitable for MS Excel, leave empty
            iv_add_bom = 'X'               "for other doc types
          IMPORTING
            et_solix = s_output_binary "(of type solix_tab)
            ev_size   = size ).
attachment->add_attachment(                       "attachment of type ref to cl_document_bcs
          i_attachment_type    = 'xls'
          i_attachment_subject = l_subject
          i_attachment_size    = size
          i_att_content_hex    = s_output_binary ).
you need to write the code for adding the receipents, subject and adding this "attachment " as an attachment to the mail.
Hope this will helps to you....,
thanks,
Rahim.

Processing xml in abap mapping

Hi all,
I use abap mapping to create XML from Idoc, I use if_ixml interface to do it.
In my code I use method get_elements_by_tag_name (on object if_ixml_document)
to find all elements with the same name:
I checked my mapping in SXI_MAPPING_TEST and it is working when I put formatted idoc
(with many lines, one tag in one line).
But when I put one long line with all tags in one line (XI receives idoc in such format from ECC)
method get_elements_by_tag_name does not return any result.
I checked also others searching methods but without results.
It looks like only first 255 characters are processed. When element, which I am looking for,
is in further position, it is not finding.
Does anyone know what is a root cause of such situation and how can I resolve my problem?
Best Regards,
Przemek

Hi,
get_elements_by_tag_name work fine for all my abap mappings so you must be doing wrong something else
the code from this page works for IDOCs also:
http://help.sap.com/saphelp_nw04/helpdata/en/ba/e18b1a0fc14f1faf884ae50cece51b/content.htm
with small changes to the nodes so maybe compare it with yours
Regards,
Michal Krawczyk

Unicode in ABAP-Mapping (u00E9 becomes u00C3u00A9)

Hello all,
I implemented this guide to create a flatfile from an IDoc. It works fine, but some characters are not mapped correctly: an "é" for example becomes "Ã©" and an "ú" becomes "Ãº". Is this a Unicode problem or something? If yes, how can I use Unicode in ABAP mapping?
As the XML-IDoc is transfered correctly to XI the problem is not in communication channels... it's in the ABAP mapping.
Best regards,
David

Hi David,
As michal said the problem needs to be isolated whether it is at the mapping level or at the file adapter level.
In case it the file adapter then you can mention the encoding standard and if its at the abap mapping the your objects should be unicode enabled.
Regards
joel

Preview and Printing of Chinese Characters in Smartform

Hi everyone!
I have a development that needs to output in Smartform a combination of Chinese and English characters, on an English Logon,
When I debug the form, the Chinese characters are shown in the debug screen, but when it is previewed or printed, it shows garbage. Can anyone help me with this?
Thanks a lot! Points for any helpful answer!

Hi
check this OSS Note
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000    0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X
Regards
Anji

Problems with Chinese characters

I have a client experiencing 3 distinct problems with their Chinese-localized Fm files:
The SimSun TTF font used in the source Fm files is "uninstalling" itself. This requires reinstallation of the font on a regular basis (every few days).
The colons used in index markers in the Fm source files are not being parsed as Level1IX, Level2IX, etc. in the RoboHelp project. Instead, they are recognized as colons. In other words, the first level marker in Rh is XXXXXXXX:XXXXXXX:XXXXXXX. The same is true for the semicolons.
The conversion settings for the Chinese project do not allow for mapping to individual CSS elements and classes. This means that all of the formatting is controlled via the supplemental CSS generated from the FrameMaker formatting. IOW, the formatting all uses the class="FM_ definitions.
Has anyone had success working with Chinese characters in a FrameMaker to RoboHelp workflow (either linking or importing)?
Anyone else seen any of these issues in Chinese or any other fonts?
I'm thinking the first two issues are likely due to the TrueType font used, but can't find an Adobe OTF SimSans font to use as a replacement.
However, the lack of mapping capability in the conversion process is a stumper...perhaps due to the double-byte font itself.
Any thoughts or solutions are greatly appreciated by my client (whose deadline passed yesterday!)
-Matt

I dont think you can print chinese chars at the console on window
to print the character codes to the console use someting like that
char [] chars = request.getParameter("whatever").toCharArray()
for(each chars){
System.out.println((int)chars);
then check if you got the corresponding chinese char

Non-unicode FTP transfer of chinese characters

Hi,
We're trying to transfer data in SAP stored under .txt format using an abap program to FTP across to another external system. Our current SAP system is 4.6C is does not have unicode capability and uses code page to translate non-English texts. We have data that contains chinese characters and we would need to automatically transfer these data across to the external system via FTP.
The problem we face is that it appears that the text in the receiving end was unable to interpret the chinese characters and funny characters are appearing. How do we solve this problem ?

hi
as far as i know when working with korean characters
we came to know that OS level should support the language characters
usally if the text file is having ascii characters that is enough(no need of any kind of specifi language characters, korean or chinese or what ever it may be)
if u open this text file with proper OS installed in your system then it will appear correctly for you
otherwise it will show junk characters
so concentrate on the ascii values for the chinese characters in your system
if the target system supports chinese characters then this ascii characters should appear as chinese characters to them also

Printing chinese characters in a zebra printer using SAP Interactive Forms

Hello,
We have created an Adobe Interactive Forms in SAP with transaction SFP. In this form we have used some words in English and another ones using Simplified Chinese characters . We have defined a Zebra printer in SPAD transaction using Device Type AZPL203.
We have defined an ABAP program to printout this form. When we print it in the zebra printer some of the chinese characters are printed and some of them no.
Has anyone faced the same problem?
Please if this is not the right forum, please could you adress me to the right one?
Thanks a lot
Miquel A. Vergara

Hello,
Please check if the notes below are useful.
83502 - Printing Support for Native Languages
1612051 - Foreign text printed with garbage characters
Thanks,
Ravi

Printing Chinese Characters in Smart Forms

Hi,
Iu2019m trying to print Chinese characters via smart forms. However during print preview or print, all Chinese characters are showing as # symbols.
I have researched and implemented for some possible solutions posted in the forum like:
a.) Setting the regional language control panel.
b.) Activating the multi-byte function in I18N.
c.) Checked the output device is SWINCF.
d.) Control parameter language is ZH (Chinese).
Unfortunately it still doesnu2019t solve the problem. Any input is highly appreciated.
With regards,
Marc

Remark following basics:
Forms:
Language of the form must be: "ZH".
Due to a SAPNOTE only font family CN* (CNSONG etc.) is mapped.
For frontend print, you must install chinese true type on you local PC and print via "CNSAPWIN" .
For backend print, you must install neccesaary fonts in your printer to the resident fonts. You must use a printer like "CNHPL4" or so.
For PDF archiving, you must upload truetype fonts to application server -> basis guys.
Cascading Fonts:
If you mix different subfonts to unicode areas, you must use CNSAPWINCF.
Until now, only frontend printing is available.
Note:
Spool created for back end print with print preview is only a simulation of getting a picture of the output created with front end technology. So it can differ, when the printer does not have the resident fonts.
Regards,
Christian

Mobile network symbol displays Chinese characters whilst in China instead of English

The network carrier symbol in the status area displays in Chinese characters instead of English whilst travelling in China so that I have to go to the settings to see which carrier is selected. The phone is set to English in the region format and I have never had this on my previous Blackberry. Is it a setting or a firmware issue?

Yup, only if your iOS device is set to English. Then yes, good Pinyin (and even some English!) shows up. I guess my only complaint now (in English) is that you really have to zoom in to see the smaller streets compared to how Google Maps showed them.
The Hanzi is still an issue, though, in at least some other languages. I prefer English but some others in my household prefer Spanish, and when the language is set to Spanish, Hanzi shows up everywhere.

The pdf chinese characters not display (11G WLS_PERORTS)

My Database:TRADITIONAL CHINESE_TAIWAN.AL32UTF8
Environment:xp
According to:http://docs.oracle.com/cd/E24269_01/doc.11120/e24479/pbr_pdf002.htm#BABCCEAB
C:\Oracle\Middleware\asinst_1\config\FRComponent\frcommon\tools\COMMON\uifont.ali
add a row
[ PDF ]
.....AL32UTF8 = "MSungStd-Light-Acro"
But the pdf chinese characters not display,Why??
http://ppt.cc/h-Tx

kindly, make sure that you add the font path into your FORMS_PATH in regestery (if you are using windows) also put your font mapping ubder [ PDF:Subset ]
for example:
[ PDF:Subset ]
times = "Barcd39.ttf"
Arial..italic.Bold.. = "arialbi.ttf"
Arial..italic... = "ariali.ttf"
Arial...Bold.. = "arialbd.ttf"
Arial = "arial.ttf"
"Andale Duospace WT J" = "Aduoj.ttf"
"Albany WT J"="AlbanWTJ.ttf"
"Arabic Transparent"="artro.ttf"

How to generate reports 10g in chinese characters pdf/html (10g)

Hi,
we have installed Oracle AS 10g (9.0.4.1) on an windows 2000 server.
The nls_lang=American_america.UTF8
the database server 10g with characterset utf8
The chinese font used is the simsun (simsun.ttf) semplified chinese.
We have no problem with the forms and the database (we have prompt in chinese and we store data in chinese and we view the forms with the jnitiator.
Our problem are the reports: we can't view chinese characters in pdf reports or html
We have readen a lot of topics (very confused..) and we have tryed a lot of solutions but without success.
In particolar, the last:
in the uifont.ali under the pdf subset section we have mapped the simsun font with the file arialuni.ttf
simsun="arialuni.ttf"
We have installed the arial unicode ms (arialuni.ttf) on the server and also on the client.
we have put the file arialuni.ttf also in a directory of the report path.
But it doesn't work.
What can we do ?
Regards

I agree with Phillip. Looks li ke you've got everything else setup properly, but you should use a Unicode font in your report instead of simsun. If you really want to use Simsun, then change your report server NLS parameter to use something like NLS_LANG=SIMPLIFIED CHINESE_CHINA.ZHS16GBK or even NLS_LANG=AMERICAN_AMERICA.ZHS16GBK, and remove the reference to arialuni.ttf. By making your report server use UTF8, it requires that you use a Unicode font. If you change your NLS to a Chinese character set, sqlnet will do the conversion for you automatically and transparently, and you can use simsun
The subset feature is what allows you to see the PDF properly on machines that don't already have the font installed. If your target users are internal and you can control them, or external and all likely to have the font already, you don't need the subsetting at all.

Chinese Characters in ABAP Mapping

Similar Messages

Maybe you are looking for