IS-FS-EDT:German special Characters umlaut not uploaded in the database

Hi,
I have problems with special German characters (umlaut) like ü, ö, ä. I am uploading BPs using External Data Transfer using flat file. Flat file contains multiple strings.
The problem is that when I'm using a string containing one of those in the flat file text for example u201Cu201D, EDT uploaded the string without umlaut i.e. umlaut replaced with #.
Is there any way to upload umlaut using EDT as it is in the database?
Thanks in advance.

Similar Messages

German special Characters ( umlaut) not displaying in WebI

Hi There,
i'm working with on BO XI R2 SP3 installed on Solaris.
I have problems with special german characters(umlaut) like ü, ö, ä. They are not being displayed correctly in Webi; actually they are displayed following this logic ü = u, ö = o, ä = a.
The problem is that when i'm using a string containing one of those in the filter conditions, the query so generated returns empty results because is not matching the data in the database.
Is there any way to display umlaut in the report result and in the LOV, as they are in the database?
Please any suggestion is more than welcomed.
Pierluca

Hi,
Could you please follow the below steps:
1>     Check if you have international language support pack installed on Bo server. Check if you have Arialuni.ttf under fonts file under Windows directory on BO Server.
2>     Specify Arialuni.ttf file name in fontaliases.xml under <bo installation>\fonts\
3>     Connectivity modification
Oracle 9
a> Modify oracle.sbo file under
Windows
u201C\BOInstalledfolder\dataAccess\RDBMS\connectionServer\oracleu201D
Under the corresponding target database engine, add the Unicode parameter with the UTF8 value as specified below;
        <DataBase Active="Yes" Name="Oracle 9">
          <Parameter Name="Library">dbd_oci9</Parameter>
          <Parameter Name="Unicode">UTF8</Parameter>
        </DataBase>
You can do the modification under the DEFAULT section. This applies for all target databases.
b>     Windows: Modify NLS_LANG setting in Registry
Under Oracle/HOME0 folder, you can find NLS_LANG definition
Default setting is(example in UK English):
     ENGLISH_UNITED KINGDOM.WE9ISO8859P 15
Changed to:
     ENGLISH_UNITED KINGDOM.UTF8
MS SQL Server 2000
a>     Modify odbc.sbo file under
u201C\BOInstalledfolder\dataAccess\RDBMS\connectionServer\odbcu201D
Under the corresponding target database engine,
u2022     add the Unicode parameter with the UCS2 value as specified below;
u2022     Check the Library parameter to set with the correct Unicode library name (See Connection Server release note for more information).
    <DataBase Active="Yes" Name="MS SQL Server 2000">
          <Parameter Name="Family">Microsoft</Parameter>
          <Parameter Name="Version">rdbms_mssqlserverodbc.txt</Parameter>
          <Parameter Name="SQL External File">sqlsrv</Parameter>
          <Parameter Name="SQL Parameter File">sqlsrv</Parameter>
          <Parameter Name="Array Bind Available">True</Parameter>
          <Parameter Name="Library">dbd_wmssql</Parameter>
          <Parameter Name="Unicode">UCS2</Parameter>
          <Parameter Name="Driver Level">31</Parameter>
            </DataBase>
You can do the modification under the DEFAULT section. This applies for all target databases.
DB2 UDB
a>     Modify db2.sbo file under
u201C\BOInstalledfolder\dataAccess\RDBMS\connectionServer\db2u201D
Under the corresponding target database engine, add the Unicode parameter with the UTF8 value as specified below;
        <DataBase Active="Yes" Name="DB2 UDB v8">
          <Parameter Name="Binary Slice Size">30000</Parameter>
          <Parameter Name="Max Rows Available">True</Parameter>
          <Parameter Name="Unicode">UTF8</Parameter>
           </DataBase>
You can do the modification under the DEFAULT section. This applies for all target databases.
b> Define the Environment Variable DB2CODEPAGE with the value 1208.
Teradata V2R5
a> Modify teradata.sbo file under
u201C\BOInstalledfolder\dataAccess\RDBMS\connectionServer\teradatau201D
Under the corresponding target database engine, add the Unicode parameter with the UTF8 value as specified below;
        <DataBase Active="Yes" Name="Teradata V2 R5">
          <Parameter Name="Unicode">UTF8</Parameter>
        </DataBase>
You can do the modification under the DEFAULT section. This applies for all target databases.
4> Universe - parameters - UNICODE_STRINGS - Yes
Please let me know if this works for you.
Thanks,
Madhu.

German special characters are not returned from catalog

When the german special characters are part of the descrition of the article from the the catalog (external). ( reaching catalog from PM order components screen)
It returns '#' in place german special characters ö ('Umlet') . This is because of the initial charset from the HTML page. How do we get the correct charset of the loaded HTML page.
But when we execute the same through WTS the german characters are correctly returned but charset is incorrect. Can someone help me to resolve this?

Hi ,
Can you pls check the customization OCI interface Convert of HTML fields to SAP Fields where in you maintained the text, which is inturn mapped to conversion module in the customization for example IOCI_DESCRIPTION_W.
Regards
Satish

German special characters (Umlaute)

Hello,
I just wanted to switch over from Eudora 6.2 to Mail 2.0.7.
After importing the mails completely and starting with Mail I realized that all mails contaning characters such as "äöü?" been converted to strange characters.
I couldn't find anything in Mail's settings and so I have switched back to Eudora (as long as this problem is not being solved;-().
Does anybody have a hint what I have to change or fix?
Thanks a lot and greetings from Leipzig
Ralf
PS.: I'd love to use the special features of Mail but at the moment "No Way:-("

how did you import the Eudora Mailboxes? Did you use the free application Eudora Mailbox Cleaner for this?
If not then you definitely might want to give a try. For me and regarding to the comments in VersionTracker it did a perfect job, in converting several thousands of old messages including attachements. In addition it is super fast.
Best regards
Rolf

German Special Characters not displayed correctly in RTF using code

Hi ,
In my code we are using webdynpro method
WDResourceFactory.createResource(
byte[] data, String resourceName,WDWebResourceType
Type)
Here in our code we are implementing this as
ITemplateElement templateEl = wdContext.currentTemplateElement();
WDResourceFactory.createResource(
templateEl.getReportData(),
reportName.substring(0, reportName.lastIndexOf('.')),
WDWebResourceType.RTF); reportName.lastIndexOf('.')),
Here templateEl.getReportData() returns a set of bytes which has some
german special characters.
We are generating the Bytes using String.getByes(),Just before
String text = new String(in);
collector.putBusinessObject(boName, bo);
reportDocTemplateParser(collector, text);
collector.removeBusinessObject(boName);
String generatedText = collector.generateRTF();
out = (null != generatedText) ? generatedText.getBytes() : null;
The out put is the if i am giving a word with german special characters for eg:
Betriebsübersichten it first gets converted to bytes and then passes through method WDResouseFactory.createResourse(.....) which creates an RTF file and finally in the RTF file it appears as Betriebsbbersichten the special character is not displayed correctly.
i came to knw that while converting into bytes we have to make it RTF supported encoding.ie for eg generatedText.getBytes('cp1252').i even tried with other charactersets like ISO-8859,cp1253 and so on but none of them worked.
It would be really great if you could suggest the needful.
Thanks and Regards
Neeta

I soved this by using get_data function of response object. Then converting this into ISO-8859-1 charset.
See code below.
DATA : lv_encoding   TYPE abap_encoding,
          lv_conv       TYPE REF TO cl_abap_conv_in_ce,
          lv_x_string   type xstring.
lv_x_string = pv_http_client->response->get_data( ).
    lv_encoding = '1100'.
    lv_conv = cl_abap_conv_in_ce=>create(
                          encoding = lv_encoding
                             input = lv_x_string ).
    lv_conv->read( IMPORTING data = pv_result ).

German special characters..

I just got my first iPod this afternoon and am now in the process of uploading all my CDs into iTunes. However, some of my files require typing German special characters (umlauted vowels). I'm using a PC and the special character codes for PCs are not working in iTunes. I'm stumped!
Anyone know how to access special characters? They seem to exist, since certain albums I've uploaded which have German titles are picking up umlauts.
TIA....
Bob

Trevor,
If the client application attempts to store a character such as the euro that is not defined in the database character set a replacement is selected and the clients representation will be lost. If the client uses a different code page to the databases character set the symbol can still be stored as long as both code pages have a code. The client must also have the character set component of NLS_LANG set to the client's character set.
The solution is in finding a correct combination of the MS Windows code page that match the chosen Oracle client character set encoding for that character. The problems are with the client PC settings, and the resolution could be time consuming when looking for the available OS code pages and font information. You could find some information on code pages at the following Microsoft site:
http://www.microsoft.com/typography/unicode/cscp.htm

Special characters are not shown in compare document report in Acrobat X

Hi All,
I have a pdf document which is having some special characters like üὄ. Now I have updated the document with few corrections and while compare document in Acrobat X special characters are not shown in the report.
Can any one please look into this and give suggestion.

Hi Steve,
Thanks for your reply.
Platform - PC
Application - 3B2 and Acrobat 9
So far we have seen this kind of issue in only one document. In the below screenshot you can see 2 pdf files, the right side one is my MS pdf and the left side one is the exported pdf from 3B2 application both the files having the special characters such as . I just did the text comparison however both and is missing in the exported pdf but the reports shown the changes for characters only wherever the charactes is missing the report not shown the changes properly(See highlighted in yellow).
Please let me know if you need more deatails.

German special characters not displaying on page instead of that Question marks displayed

when i submit form,i need to send a mail with filled data.Here Suppose user entered german special characters.I am getting Question marks instead of ä,Ä,ö,Ö,ü,Ü,ß. I have used meta tag like
<meta http-equiv="content-type" content="text/html;charset=utf-8" />.But i am getting fine characters with IE and Chrome.I am using FireFox 3.6.16 english.

Hello core team,
Thanks a lot!!!!
i m not only the person to use html form.So many non technical persons using the same. how can i tell to all persons regarding changing character encoding. i need some permenant solution,

Smart Web Printing does not show/print german special characters (äöü)

I have installes Smart Web Printing on my computer with WIndows 7. I do use a german localization. Selected text is shown and printed correct, except german special characters ä ö ü. They are even not shown correctly in the menues of the application.

Response to cor-el suggestions:
I tried what you suggested as far as checking the theme (it's "Default 8.0") and deleting the sessionstore files (there was one .js file, one -1.js file and one .bak file). I still have the same slow response problems (especially typing, it has gone dead on me for a short time twice while typing this replay so far, now a third time) and lost of headers and trailers and some data.
I did the suggested actions three times just to make sure that I was doing them correctly. On the first try, the sessionstore.js and sessionstore-1.js was more than twice the size of sessionstore.bak. Since doing what was suggested, the sessionstore.js and sessionstore.bak are, I believe, the same size. I did not write down their size is why I am not certain.
The printing problem appears to only be with one website which is an investment website which I would prefer not to document here. I print from this website each weekday and I have confirmed that the printing problem started when the upgrade to version 8.0 occurred.
I need a solution to this or I am going to either go back to IE (Ugh!) or find another browser. The typing delays are an extreme annoyance since I do lots on the Internet including a lot of emailing. The delays also involve the buttons to select functions within a website.
Is there a way to get back to the version previous to version 8.0?

Unity Connection 8.6 LDAP or CUCM Import with german special characters called "Umlaut": ä, ö, ü

Hi,
for jabber 9.1 integration i sync'ed all users at Callmanager, Presence and Unity to our LDAP (MS AD). with CUCM and Presence (both 8.6.x), it works fine, just Unity Connection sync the Users from AD, but i cannot import Users with german special characters ä, ö, ü (i.E. German Name in LDAP-su: Müller).
Jabber 9.1 need for Voicemail Integration the AD Authentication. Know somebody, if there is an Workaraound or Fix ?
This is a general issue, with or without Jabber, with sync directly from AD, or indirectly through CUCM (sync'ed with AD)
thx and regards
Jacky

I located an identical defect (CSCts28455) that was closed as unreproducible. The defect references CSCtj73444 "Add support for UTF-8 password to LDAP and RADIUS/MSCHAP" which is added to 8.4.2 with the recommendation of RADIUS/MSCHAP or LDAP only for international character support. It would make sense to go to the latest in your current train (ie: 8.4.4.1.ED) and see if the issue remains. What you want to do appears to be supported.
Matthew

Problem with german special characters in APEX

Hi,
we have a problem with all the special characters in german language in our Application.
APEX version 3.1.0.00.32 is installed on a oracle database 9.2.0.6.0
The nls_characterset of the database is: American_America.WE8ISO8859P1
We have modified the wdbsvr.app file on our HTTP-Server like it's shown in the installationguide for APEX and have set the nls_lang parameter to American_America.AL32UTF8.
If I look at the source code of the html-pages of our application, there are already the following settings in the header of every page:
meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"
With this settings all the german special characters like ä ö ü are not shown correctly in the browser.
What can I do that the pages are shown correctly?
Thanks for help!

Hi Petra,
ok, so my guess was correct. So the solution is to set the charset attribute in the HTML header to "charset=UTF-8". This is actually the way it should be. But I'm wondering why it is not in your case? Are you using a custom template for the page(s) in question where the charset attribute is set to a custom value? The meta tags in the HTML header are usually set by/through the #HEAD# substitution string in the header definition section of the page template, cp. one of the page templates in Shared Components --> Templates. And as far as I know you are not able to change this substitution string, you can only switch the inclusion on/off with the option "Include Standard CSS and JavaScript" in each page definition. (I might be mistaken, though, I'm quite new to APEX...)
Regards
Frank

Problem with special characters (umlaut)

Hi,
I have a text box in my form.
when I am entering the normal characters it working fine and the values are
persisting quiet well in the database but when I am entering special characters (umlaut characters),
it is not storing them properly in the database.
I have checked in the logs at the application server side and the problem is while getting the values from
the request. The JSP which is submitting the request I have explictly put the following line:
request.setCharacterEncoding("iso-8859-1");
But this also not seems to be working.
Could you please let me know the resolution of this problem.
Thanks in advance
Amit

Hi,
Thanks for the reply.
I have checked the database and there is no problem there.
To check if I am getting the correct values from the JSP I have put the following code in my action class:
                              if(columnName.equalsIgnoreCase("REMARKS"))
                                   log.debug("Character Encoding value of � is "+Character.getNumericValue('�'));
                                   log.debug("Character Encoding value of � is "+Character.getNumericValue('�'));
                                   log.debug("Character Encoding value of � is "+Character.getNumericValue('�'));
                                   log.debug("Character Encoding value of � is "+Character.getNumericValue('�'));
                                   log.debug("Character Encoding value of � is "+Character.getNumericValue('�'));
                                   log.debug("Character Encoding value of � is "+Character.getNumericValue('�'));
                                   String str = value.toString();
                                   char[] remarkArray = new char[str.length()];
                                   str.getChars(0, (str.length()-1), remarkArray, 0);
                                   for (int i = 0; i < remarkArray.length; i++)
                                        log.debug("Encoding value of "+remarkArray[i]+" is "+Character.getNumericValue(remarkArray));
In the remarhs I am setting the value in the form as "��"
and I am getting the following in the logs:
Character Encoding value of ─ is -1
Character Encoding value of � is -1
Character Encoding value of ▄ is -1
Character Encoding value of � is -1
Character Encoding value of � is -1
Character Encoding value of � is -1
Encoding value of ├ is -1
Encoding value of ┐ is -1
Encoding value of ├ is -1
Encoding value of ┐ is -1
Encoding value of ├ is -1
Encoding value of ┐ is -1
Encoding value of ├ is -1
Encoding value of ┐ is -1
Encoding value of ├ is -1
Encoding value of � is -1
Encoding value of ├ is -1
Encoding value of is -1
Kindly suggest what may be the issue??
Amit

TCS 3.0: Anchored Frames contain callouts with german special characters Conversion to RH nok

Hi all,
I have Frame documents, which contain anchored frames with callouts. The callouts are created with Frame and contain german special characters like ä,ö,ü. These characters are not converted correctly.
Thanks for help.
Regards,
Rainer

German Special Characters in XSTRING to STRING conversion

Hi Experts,
I have a CSV file (created from a Windows Excel file) with German Special Characters (e.g. 'ä', 'Ä') and I am trying to read this into ABAP internal tables. By using the THTMLB tag 'thtmlb:fileUpload' I get an XSTRING and I am trying to convert this into STRING. However, wheny trying to do this I get an exception 'CX_SY_CONVERSION_CODEPAGE'.
This is my coding:
data: conv type ref to cl_abap_conv_in_ce.
conv = cl_abap_conv_in_ce=>create( input = lr_upload->file_content ).
conv->read( importing data = lv_content ).
Note: lr_upload is my XSTRING object from the file upload, lv_content is a STRING.
In the CSV file the German special characters look fine and the SAP system is a Unicode system, but it seems like there are some problems with the conversions somehow. Any ideas from the experts?
Thanks a lot and Regards,
Jens

As you mention a csv file I'm wondering if your encoding is wrong: I.e. when you create your instance of cl_abap_conv_in_ce you don't specify the encoding of your source hex string, so that means the default encoding is used, which should be UTF-8 in your case. So if your csv file is not encoded in UTF-8, specify the correct encoding in the create method and see if that helps.
Depending on how you get the file contents you might actually be able to combine the file retrieval with the conversion in one step. E.g. if the file is read from the application server you could specify the used code page via [open dataset ... in legacy text mode ... code page|http://help.sap.com/abapdocu_70/en/ABAPOPEN_DATASET_MODE.htm#&ABAP_ALTERNATIVE_4@4@]. Similarly method gui_upload of class cl_gui_frontend_services also allows you to specify a code page.
If all of this doesn't help, post some further details on your file (e.g. sample content & encoding) and possibly add some further details from the exception you're getting. As you mention a Unicode system it basically means that we should be able to convert all characters without any problem as long as we specify the correct source code page.
Cheers, harald

Problems with german special characters on DOC export.

Hello,
I have a problem when I export a pdf to doc via the adobe cloud feature. Everything works fine except for the special german characters. And since I want to use this tool to convert my latex pdf to word to use the spellchecker for me the entire system is broken. Do I need to change to a special encoding of my textfiles for this to work? Can you fix this somehow?
Cheers
nenTi

I use Arial as font generated by MiKTex. So I doubt it's a font problem. Also it detects all other characters without a problem, only the german special chars äöüÄÖÜß are a problem for the system.
Try it yourself:
"Hier ist mein scheiß überfordertes konvertierungs script und rödel vor sich hin ohne ännähernd befriedigendes Ergebniß."
You won't have the special chars editable in the doc. It is visible but you can't edit it because it is converted to something strange.

IS-FS-EDT:German special Characters umlaut not uploaded in the database

Similar Messages

Maybe you are looking for