Unicode character conversion

Hello,
From external system we receive XML messages in UTF-8. The data are transfered from XI to SAP WAS by RFC adapter. The communication language is set to 'CS' (Czech). The data are saved into database with no conversion to set code page (1401). The receiving system is not Unicode compatible.
Into database are writen unicode chars (e.g. ř) instead of single chars in Czech alphabet.
Is here any way how to force a XI to make a character conversion ?
Thanks for any feedback.
Marian Morzol

Pl identify your database characterset
SQL> select * from NLS_DATABASE_PARAMETERS;If the NLS_CHARACTERSET is WE8ISO8859P1, it is not capable of storing the Euro symbol (pl do a google search to find various references).
To store the Euro symbol, you will most likely need to change the database characterset to UTF8 - pl see the MOS Docs mentioned in this thread for details - Adding Greek & German language to R12
HTH
Srini

Similar Messages

Character conversion problems when calling FM via RFC from Unicode ECC 6.0?

Hi all,
I faced a Cyrillic character convertion problem while calling an RFC function from R/3 ECC 6.0 (initialized as Unicode system - c.p. 4103). My target system is R/3 4.6C with default c.p. 1500.
The parameter I used in my FM interface in target system is of type CHAR10 (single-byte, obviously).
I have defined rfc-connection (SM59) as an ABAP connection and further client/logon language/user/password are supplied.
The problem I faced is, that Cyrillic symbols are transferred as '#' in the target system ('#' is set as default symbol in RFC-destination definition in case character convertion error is met).
Checking convertions between c.p. 4103 and target c.p. 1500 in my source system using tools of transaction i18n shows no errors - means conversion passed O.K. It seems default character conversion executed by source system whithin the scope of RFC-destination definition is doing something wrong.
Further, I played with MDMP & Unicode settings whithin the RFC-destination definition with no successful result - perhaps due to lack of documentation for how to set and manage these parameters.
The question is: have someone any experience with any conversion between Unicode and non-Unicide systems via RFC-call (non-English target obligatory !!!), or can anyone share valuable information regarding this issue - what should be managed in the RFC-destination in order to get character conversion working? Is it acceptable to use any character parameter in the target function module interface at all?
Many thanks in advance.
Regards,
Ivaylo Mutafchiev
Senior SAP ABAP Consultant

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

Character conversion from Unicode to WE8ISO8859P1

Hi,
I am having a text field in which i need to enter Unicode characters also. When entering the Unicode character '€' in the text field and when clicked on the "Save" button it is throwing the error "java.sql.SQLException: Cannot map Unicode to Oracle character". The oracle database characterset is of type "WE8ISO8859P1". Do i need to do the conversion of Unicode character to WE8ISO8859P1 in the Controller explicitly?If so, Please mention the method through which i can achieve the same.Or is there any profile options or setup changes through which i can avoid this error?Can anyone please suggest how to proceed with this?
Thanks,
Sreeja

Pl identify your database characterset
SQL> select * from NLS_DATABASE_PARAMETERS;If the NLS_CHARACTERSET is WE8ISO8859P1, it is not capable of storing the Euro symbol (pl do a google search to find various references).
To store the Euro symbol, you will most likely need to change the database characterset to UTF8 - pl see the MOS Docs mentioned in this thread for details - Adding Greek & German language to R12
HTH
Srini

Printing ZPL (Zebra) data to printer spooler without character conversion

Hi all,
We are printing shipping labels from UPS, with a process where we recive the ZPL label code directly from UPS, and we just need to pass the data to the printer to get the labels. We have already implemented this with Fedex and some custom labels, and it works perfectly. The problem with the UPS label data is that it contains non-printable characters (in the MaxiCode data field). When passed to the SAP printer spooler (see code example below), the data gets corrupted because SAP interprets these non-printable characters as printer control codes.
I have verified this by saving the ZPL data to a local file, before printing it through the SAP spooler. I then print this raw data and compare the output with the labels printed from the spooler. The MaxiCode (the big 2D barcode) is different in these labels. UPS has also tested the labels, and rejected them because of incorrect data in the barcode.
For printing, we are using printers defined as type "PLAIN", but I also tried using the "LZEB2" device type with the same result. The error we see in the spooler entry is this:
Print ctrl S_0D_ is not defined for this printer. Page 1, line 2, col. 2201
Print output may not be as intended
The printer ctrl code differs, depending om the label. I have examined the spooler data in "raw" mode, and there is always an ASCII character 28 (hex 1C) in front of the characters that SAP think are control codes, and this is why I think these non-printable characters are the reason for the problems.
This is the function module I use to print the ZPL data (and as stated above, this works fine for Fedex and custom labels). The ZPL data is converted to binary format before passed to the function module, but I also tried to send the data in text format with another FM, but the result is the same. I have experimented with the "codepage" parameter, and this one gives the least amount of errors, and some labels actually get through without errors. But still at least 50% of the labels gets corrupted, with log entries like above.
CALL FUNCTION 'RSPO_SR_WRITE_BINARY'
      EXPORTING
        handle           = lv_spool_handle
        data             = lv_label_line_bin
        length           = lv_len
        codepage         = '2010'
      EXCEPTIONS
        handle_not_valid = 1
        operation_failed = 2
        OTHERS           = 3.
Does anyone know if there is a way to send data to the spooler without character conversion or interpretation of printer control codes? Or is there any other smart way to get around this problem?
/Leif

I do a more direct output to the spooler, to avoid any issues with the WRITE statement and SAP's report output processing. At the same time, I insert line breaks so that the output is easy to debug in the spooler if needed. Also included is the code to to detect the escape code (ASCII #28) and to insert a control code ZZUPS in its place (you can skip this for Fedex). Here's a simplified example, but please note this is for a Unicode system, some minor changes is required in a non-Unicode system.
CONSTANTS: lc_spcode TYPE c LENGTH 5 VALUE 'ZZUPS',
           lc_xlen TYPE i VALUE 5.
   DATA: lv_print_params TYPE pri_params,
         lv_spool_handle TYPE sy-tabix,
         lv_name TYPE tsp01-rq0name,
         lv_spool_id TYPE rspoid,
         lv_crlf(2) TYPE c,
         lv_lf TYPE c,
         lstr_label_data TYPE zship_label_data_s,
         lv_label_line TYPE char512,
         lv_label_line_bin TYPE x LENGTH 1024,
         lv_len TYPE i,
         ltab_label_data_255 TYPE TABLE OF char512,
         ltab_label_data TYPE TABLE OF x,
         lv_c1 TYPE i,
         lv_c2 TYPE i,
         lv_cnt1 TYPE i,
         lv_cnt2 TYPE i,
         lv_x(2) TYPE x.
   FIELD-SYMBOLS: <n> TYPE x.
   lv_crlf = cl_abap_char_utilities=>cr_lf.
   lv_lf = lv_crlf+1(1).
   lv_name = 'ZPLLBL'.
CALL FUNCTION 'RSPO_SR_OPEN'
     EXPORTING
       dest                   = i_dest
       name                   = lv_name
       prio                   = '5'
       immediate_print        = 'X'
       titleline              = i_title
       receiver               = sy-uname
*      lifetime               = '0'
       doctype                = ''
     IMPORTING
       handle                 = lv_spool_handle
       spoolid                = lv_spool_id
     EXCEPTIONS
       device_missing         = 1
       name_twice             = 2
       no_such_device         = 3
       operation_failed       = 4
       OTHERS                 = 5.
   IF sy-subrc <> 0.
     RAISE spool_open_failed.
   ENDIF.
LOOP AT i_label_data INTO lstr_label_data.
     CLEAR ltab_label_data_255.
     SPLIT lstr_label_data-label_data AT lv_lf INTO TABLE ltab_label_data_255.
     LOOP AT ltab_label_data_255 INTO lv_label_line.
       IF lv_label_line NE ''.
         lv_len = STRLEN( lv_label_line ).
*       Convert character to hex type
         lv_c1 = 0.
         lv_c2 = 0.
         DO lv_len TIMES.
           ASSIGN lv_label_line+lv_c1(1) TO <n> CASTING.
           MOVE <n> TO lv_x.
           IF lv_x = 28.
             lv_cnt1 = 0.
             lv_label_line_bin+lv_c2(1) = lv_x.
             lv_c2 = lv_c2 + 1.
             DO lc_xlen TIMES.
               ASSIGN lc_spcode+lv_cnt1(1) TO <n> CASTING.
               MOVE <n> TO lv_x.
               lv_cnt2 = lv_c2 + lv_cnt1.
               lv_label_line_bin+lv_c2(2) = lv_x.
               lv_c2 = lv_c2 + 2.
               lv_cnt1 = lv_cnt1 + 1.
               lv_len = lv_len + 1.
             ENDDO.
           ELSE.
             lv_label_line_bin+lv_c2(2) = lv_x.
             lv_c2 = lv_c2 + 2.
           ENDIF.
           lv_c1 = lv_c1 + 1.
         ENDDO.
*       Print binary data to spool
         lv_len = lv_len * 2. "Unicode is 2 bytes per character
         CALL FUNCTION 'RSPO_SR_WRITE_BINARY'
           EXPORTING
             handle                 = lv_spool_handle
             data                   = lv_label_line_bin
             LENGTH                 = lv_len
           EXCEPTIONS
             handle_not_valid       = 1
             operation_failed       = 2
             OTHERS                 = 3.
         IF sy-subrc <> 0.
           RAISE spool_write_failed.
         ENDIF.
       ENDIF.
     ENDLOOP.
   ENDLOOP.
   CALL FUNCTION 'RSPO_SR_CLOSE'
     EXPORTING
       handle = lv_spool_handle.
   IF sy-subrc <> 0.
     RAISE spool_close_failed.
   ENDIF.

"character conversion error" while parsing xml files

Hello,
I'm trying to parse MusicXML (Recordare) files, but I'm getting an exception.
I'm using the SAX parser (javax.xml.parsers.SAXParser).
Here is the code I use to instantiate it:
final javax.xml.parsers.SAXParserFactory saxParserFactory = javax.xml.parsers.SAXParserFactory.newInstance();
final javax.xml.parsers.SAXParser saxParser = saxParserFactory.newSAXParser();
final org.xml.sax.XMLReader parser = saxParser.getXMLReader();
I'm using my own handler, but I get the same exception even if I use org.xml.sax.helpers.DefaultHandler.
The error I get is:
Character conversion error: "Illegal ASCII character, 0xc2" (line number may be too low).
The first few lines of my xml files look like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE score-partwise
PUBLIC "-//Recordare//DTD MusicXML 0.6 Partwise//EN"
"http://www.musicxml.org/dtds/partwise.dtd">
<score-partwise>
[...etc...]
If I delete the <!DOCTYPE ...> line, then I don't get the exception anymore. But the MusicXML files I get (from some other program) always contain this line, and it would be quite some work to delete them from every file manually.
So does anyone know if there is a way to avoid deleting that line in every file, while still being able to parse the xml files without exceptions?
Or maybe does anyone know what the exact cause of the exception is? (because I don't know what exactly causes it)
Thank you in advance.
Greetz,
Jipo

So does anyone know if there is a way to avoid
deleting that line in every file, while still being
able to parse the xml files without exceptions?ok this is side-stepping the real problem but I've used this code to filterout DTD references for other reasons   public static InputStream filterOutDTDRef(InputStream in) throws IOException {
      BufferedReader iniReader = new BufferedReader(new InputStreamReader(in));
      StringBuffer newXML = new StringBuffer();
      for(String line = iniReader.readLine(); line!=null; line = iniReader.readLine())
         newXML.append(line+"\n");
      in.close();
      int s = newXML.indexOf("<!DOCTYPE ");
      if(s!=-1)
         newXML.replace(s,newXML.indexOf(">",s)+1,"");
      return new ByteArrayInputStream(newXML.toString().getBytes());
   }and it actually speeds up the parsing phase too (since the DTD ref.s were on the web and the XML standard mandates that there is a fetch for each xml file parsed..)
you can feed the above into the InputSource constructor that takes an InputStream argument.
Now for the real problem... 0xc2 is "LATIN CAPITAL LETTER A WITH CIRCUMFLEX" according to a unicode chart - which is not an ASCII character (as the error message correctly reports). I'm not sure why the file is being parsed as ASCII though? You could try parsing in a FileReader to the inputsource and hope it picks up the default character encoding of your system, and that that character encoding matches the file. Or you could try passing in a FileReader constructed with a explicit character encoding (eg "UTF8") and see if that does the trick?
asjf

Need suggestion on Multi currency and Unicode character set use in ABAP

Hi All,
Need suggestion. In one of the requirement I saw 'multi-currency and Unicode character set experience in FICO'.
Can you please elaborate me how ABAPers are invlolved in multi currency as I think this is FICO fuctional area.
And also what is Unicode character set exp.? Please give me some document of you have any.
Thanks
Sreedevi
Moderator message - This isn't the place to prepare for interviews - thread locked
Edited by: Rob Burbank on Sep 17, 2009 4:45 PM

Use the default parser.
By default, WebLogic Server is configured to use the default parser and transformer to parse and transform XML documents. The default parser and transformer are those included in the JDK 5.0.
The built-in WebLogic Server DOM factory implementation class is com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl.
The DocumentBuilderFactory.newInstance method returns the built-in parser.
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();

Unicode Character sets (e.g UTF-8)

Hi,
We are using some third party software which will connect to the oracle database.
One of the requiremebnts it states is that both the databse client and server must use the Unicode character set e.g UTF-8.
How do we ensure this when installing the oracle client software.
Also, why when install orcale client software and select language as English does it put NLS_LANG as American by default.
Is there an English U.K language option - couldn't see it.
Many Thanks

user5716448 wrote:
Hi,
We are using some third party software which will connect to the oracle database.
One of the requiremebnts it states is that both the databse client and server must use the Unicode character set e.g UTF-8.
Pl post details of OS and database and client versions being installed
How do we ensure this when installing the oracle client software.
For the client, set NLS_LANG appropriately when using the client software - there is no setup required during the install - http://www.oracle.com/technetwork/database/globalization/nls-lang-099431.html
Also, why when install orcale client software and select language as English does it put NLS_LANG as American by default.
Is there an English U.K language option - couldn't see it.Try "ENGLISH"
http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch3globenv.htm
>
Many ThanksHTH
Srini

Error occurred during character conversion in SXMB_MONI

Hello Experts,
Good Day!
I would like to seek your help here. When i used tcode SXMB_MONI to search for messages i get this error : Error occurred during character conversion.
So far no problem with the program. Its work for all other dates. Just for one particular day and specific time period, im geting this error.
Does anyone know what is this error means? Please reply..
Thanks for your help.
Looking forward for ur replies..

Hi Presheela,
Basically this problem occurs when ur payload contains any special characters like '&' ,'>'...etc .So you have to take care of how to deal with these characters in XI.
Refer the following documentation:
How to Work with Character Encodings in Process Integration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
Regards,
Vinod.

Character conversion error

Hi all,
We are getting the following error when trying to parse an xml string resource - Character conversion error: "Illegal ASCII character, 0xc2" (line number may
be too low)-. We have not been able to get around this. We have tried creating the InputSource two different ways:
reader = new StringReader(stringSource);
src = new InputSource( reader );
and
src = new InputSource(new InputStreamReader(new ByteArrayInputStream(stringSource.getBytes())));
The problem does appear to go away if we treat the DTD we are validating against as a file. If we set it has a uri, we get the above problem.
Is anyone else experiencing this problem?
Any help would be greatly appreciated.
Thanks in advance,
Greg

Hi,
2 possible solutions:
1) try using the xerces parser instead of sun's parser
2) look at the posting at the following url and see wether the posted solution solves your problem: http://forums.java.sun.com/thread.jsp?forum=34&thread=67558
Hope this helps,
Kurt.

Problem in the character conversion

Hi Guys,
I am facing problem in the character conversion
I am posting data from SAP to third party system using XI , by converting whole input message to a String .I am using SOAP adapter to communicate XI to third party system.
Thirdparty system needs String to be wrapped in CDATA so that it will not choke by looking at the special characters. I did Wrap the output string in CDATA, using ABAP mapping but when I do that XI is converitng arrow brackets < and >. into &lt and u2018&gtu2019 my assumption is it is double encoding.
example -
before map - <AppSystemInfo>
after mapping it is converted as - <![CDATA[ &ltAppSystemInfo&gt]]>
Edited by: Vamsi on Jun 17, 2010 10:00 PM
Edited by: Vamsi on Jun 17, 2010 10:01 PM

Did you try to see the output?
bcz if you are trying this in mapping testing it will show you like this as this conversion if for xml, so xml will not do anything wrong with the special characters, so for that special characters will be converted like that.
Once try to run end to end interface and try to see at receiver side that how data looks like.
Thanks,
Hetal

Unicode character not displaying when PDF is created using PDFMaker

Using Adobe Acrobat Pro 9
Our company letterhead contains a special character (Unicode 25AA "Black Small Square"). When a PDF is created of a Microsoft Word document (2003 or 2007) using the PDFMaker, that character is not displayed in Acrobat (shows as whitespace). Strangely enough, if I search for the character in that PDF file using the Acrobat search function (query "u/25AA"), the search finds the character, but again, it is displayed as whitespace.
However, if I create a PDF from that same Word document by printing to Adobe PDF, the character displays correctly in Acrobat. Additionally, if I do a SaveAs to PDF (Using the Microsoft plugin), the character displays correctly in Acrobat. This leads me to believe that muy issue is related to the PDFMaker (as opposed to the PDF printing function) and how the character is embedded into the PDF file. I have tried opening the PDF in other versions of Acrobat, but I get the same result.
Any suggestions? We would like to utilize the convenience of the PDFMaker for our letters and reports, and not have to use the print function. I can email a sample of all the PDF's I spoke of upon request, but the issue should be reproducable using the following steps:
1. Open MS Word and type (or copy from the Character Map) unicode character 25AA in Arial font.
2. Save Word file.
3. Use PDFMaker to create PDF file.
4. Open PDF file and view results.
Any guidance or help is appreciated.
Phil Hinton

First, check the fonts in the PDF to be sure that they are not embedded (you are likely correct that there is a problem). What job settings are you using. Try the press or print. Also check the job settings to be sure that ALL fonts are to be embedded.
Also, check the log file of Distiller (set it to not be deleted in the settings). If there is an issue with the license of the font then the font will not be embedded. In that case you need to find a licensed version of the font or change to a different font.

Connecting to EMS fails with No mapping for the Unicode character exists in the target multi-byte code page

I am getting the following error when trying to connect to both my exchange servers.
New-PSSession : [ex2013-002.nafa.ca] Connecting to remote server ex2013-002.nafa.ca failed with the following error
message : No mapping for the Unicode character exists in the target multi-byte code page. For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:12
+ $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ht ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : 1113,PSSessionOpenFailed
EMS used to connect ok. I am not sure if there is any connection but Outlook was installed recently on the exchange server to enable mailbox level backups.
Any help would be appreciated.
Steve Hurst

Hello Steve,
Firstly, you cannot install Outlook with Exchange because they share certain dll files.
About the EMS question, I suggest we try rebuilding the powershell virtual directory. If it still does not work, check the application log for more referernce.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Unicode character not displaying correctly

when i am stroring Unicode Character in Oracle 8 DB .The Stored Character are not displayed correctly . Through sql client seen as '�' .Altough through JSp it displays correct value 集 (in japanese)
My client wants to see through sql also same value . Pls help wat is wrong. More info :
Oracle is set up in UTF-8 Format.
Using code as below before inserting in DB
String temp =product.getDescription();
String newResult = new String(temp.getBytes("UTF-8"), "UTF-8");

TryString newResult = new String(temp.getBytes(default),>
"UTF-8");// "default" is a String of the name of
default encoding on the part of client
Sorry there was a slip. Try the following.
String newResult = new String(temp.getBytes(default));

How to input unicode character set from oralce form 9i

Hi,
Can anyone show me how to input unicode character set from form 9i. I have designed a form and run it but when I input unicode charater in TEXT ITEM on form (FONT_NAME of this TEXT ITEM is New Roman, AriaTime l ...), but it display incorrectly nor stored it in Database.
Thank you !

Thank Duncan R Mills !
My setting NLS_CHARACTER in Database as follow :
SQL> SELECT * FROM NLS_DATABASE_PARAMETERS;
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET UTF8
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
PARAMETER VALUE
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZH:TZM
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZH:TZM
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_NCHAR_CHARACTERSET UTF8
NLS_RDBMS_VERSION 8.1.7.0.0
18 rows selected.
Even if I can'nt input unicode character on Oracle Forms, It display incorrectly though I set exactly font_name.

Unicode Literal to Unicode Character

I have a list of all the unicode characters (00C1, 00E1, 0103, etc.).
I am displaying their data as \u00C1 (in a java string: System.out.println("\\u00C1");)
How would I go about converting that literal string to the actual unicode character?
I want \\u00C1 to become the actual \u00C1 character.
All I'm really doing right now is letting the user enter in that data and then parsing their string for all unicode specifications and then turning them into the actual unicode characters.

char c = (char)Integer.valueOf("00C1", 16).intValue();

Unicode character conversion

Similar Messages

Maybe you are looking for