Sending special characters to non-unicode non-sap system: user exit

Hello All,
We are sending data from a SAP unicode system to a non-sap non-unicode system via IDOC. The idoc is standard idoc GLMAST which contains gl account information.
Some text fields contained in this idoc can contain special Polish characters. If they are sent unchanged to the non-unicode system, they give problems in the destination system.
What we would like to do is to build a user exit to convert these special characters, for example : 'é' becomes 'e', ....
We used enhancement object ALE00001, function EXIT_SAPLBD11_001 and implemented it, but it seems this exit is not called. Can this user exit be used for this functionality?
We also tried to change in SM59 the type of system of the destination to non-unicode, so that SAP replaces those special characters by #. But, than the error 02. Codepage not found is given in the idoc. Note: the link to the external system is not set up yet, so no actual connection is possible. Is this why we receive this error, and will this functionality work in the end with a non-sap system?
Thanks for helping.
Kind Regards,
Bart Pelsmaekers

I faced this problem in many project i implement below logic.
DATA: c_splchar(2) VALUE '90',
        c_defaultchar(1) type c VALUE '#'.
You have to move one by one character to this function module
          CALL FUNCTION 'URL_ASCII_CODE_GET'
               EXPORTING
                    trans_char = spl_char
               IMPORTING
                    char_code = spl_code.
All non unicode(Better you check) are always greater than 90.
         if spl_code is gt c_splchar.
            move c_defaultchar to c_splchar.
         endif.
"Reward points if usefull"
Thanks,
Narayan

Similar Messages

Unicode Errors - Interface with non-Unicode 3rd party system

Does anyone have an experience working with an interface between a Unicode SAP system and a non-Unicode 3rd party system? Would appreciate your input on existing data declaration and logic (prior to SAP Unicode conversion), if changes need to be made to the character types and upload/download functions.
We are doing our testing in a newly converted Unicode system which has interface sending files through SAP Business Connector, and uses TDAccess/COMM-PRESS to encrypt the payment file.
We are getting an COMM-PRESS error that it's not able to get the private key
ERR=>RC=107#Error building signature segment (S1A/S2A) ERR=>#Error getting private key: #PUBLIC KEY FINGERPRINT = , rc = 524
The issue seems to be that the passphrase is not received correctly in COMM-PRESS (codepage 1100) from Unicode SAP (codepage 4102). The passphrase is uploaded from a text file (codepage 1100?) to T_PPLOC and then to W_PPLOC.
TYPES: BEGIN OF T_PPLOC,
         FLINE(64) TYPE C,
       END OF T_PPLOC.
DATA: W_PPLOC(64) TYPE C
CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        FILENAME                = W_FILENAME
        FILETYPE                = 'BIN'
      TABLES
        DATA_TAB                = T_PPLOC
    LOOP AT T_PPLOC.
      IF W_PPLOC IS INITIAL.
        MOVE T_PPLOC-FLINE TO W_PPLOC.
      ELSE.
        CONCATENATE W_PPLOC T_PPLOC-FLINE INTO W_PPLOC.
      ENDIF.
    ENDLOOP.
Comparing the results between a Unicode and non-Unicode system, the uploaded passphrase is different because of the codepage. But even if I convert the passphrase first from 1100 to 4102 codepage, it still fails.

Hi,
Try this by sending value to the CODEPAGE parameter of the function module GUI_UPLOAD.
aRs

Special characters as keys - Unicode BW system

Hello together,
we want to change our SAP BW System 3.5 to Unicode and afterwards we plan the upgrade to BI 7.0.
We found the OSS note which tells that characteristic keys (e.g. material number, customer number, brand key, country key) must be designed as 7-bit-US-ASCII characters (common characters), but we did not found any note about what happens if we dont convert these characters into 7-bit-US-ASCII and weve got some Infoobjects with special characters.
Do we really have to convert theses characters? What happens if we dont change these?
We used as well the customizing option ALL_CAPITAL. What does ALL_Capital mean at the Unicode-compliant BW system. Does it have the same function as before?
Thanks and regards,
Julia
Message was edited by:
Julia

It's a difficult matter that's made extremely easy with Unicode. But you're not there yet so you are stuck with code pages and these can get very messy.
I dealt with this with Asian languages but it was a long time ago. I do remember there was a white paper from SAP that explained all the possible scenarios and possible solutions. For downloads to Excel etc. you will have to convert to a windows code page or Unicode in your program.
[This SAP Help page|http://help.sap.com/saphelp_nw04/helpdata/en/9c/70023cfa699508e10000000a11402f/frameset.htm] might contain the mentioned document, I was unable to open it...
Good luck,
Gert.

Write Special Characters in PDF file from SAP Script

Hi there,
Need a quick help...
We are converting SAP Script to PDF using the function module CONVERT_OTF
and saving the file on presentation server using GUI_DOWNLOAD...
But in certain cases where the item text is maintained with some special
characters like @#$% u03B1 u03B2 u03B3 u03B4 ®... then, some of these characters are seen
as junk/garbage characters...
how do we handle this??
P.S. Our Forms are already using Korean Font...
Any help is highly appreciated
Kind Regards,
Tanuja

Hi,
Use the FM CONVERT_OTF to get the Binary data and down load it as PDF .
sample
*/ Convert the OTF data into PDF.
    call function 'CONVERT_OTF'
     exporting
       format                      = 'PDF'
     importing
       bin_filesize                = lv_bin_filesize
        bin_file                   = lv_xstring
      tables
        otf                        = lt_otf_data-otfdata[]
        lines                      = lt_pdf_data
     exceptions
       err_max_linewidth           = 1
       err_format                  = 2
       err_conv_not_possible       = 3
       err_bad_otf                 = 4
       others                      = 5 .
*/ Convert the Xstring data into PDF
    call method cl_document_bcs=>xstring_to_solix
      exporting
        ip_xstring = lv_xstring
      receiving
        rt_solix   = lt_mess_att .
Then down load the table lt_mess_att with extension PDF.
Edited by: UmaMaheswaraRao Surapaneni on Apr 1, 2009 5:44 PM

SAP ISU - User exits at the end of move-in process

Hi,
We have a requirement to send some outbound messages on completion of Move-in process in SAP ISU system. And send some outbound message on completion of Reverse Move-in process.
I tried to find the customer/user exit in transaction EC50E and EC53E, all i could find is user exits during the process. I need something at the end of process.
At the moment all I can do is use the events raised when these process are completed (Ex: MOVEINDOC.Created) and start a workflow to send outbound messages. But i would want to know if there are any exits available at the end of the processess as I dont want to create a workflow just for one activity.
Any inputs will be appreciated.
Many Thanks,
Anand

very old item - closed

Changing SAP System User password

Due to recent security concerns we want to change <ora>sid & <sid>adm passwords. SAP is running with AIX OS.
Is there any SAP tool/script to change it or we can simply change it at OS level and be done with it?

Hi Amit,
OS level goto Computer Management -> Local Users and groups -> check for the user <sid>adm,and also for the group ora_<sid> the same way u can do with AIX OS
regards,
S.Rajeshkumar

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

How to check for Unicode/Non-Unicode SAP?

Hi All,
Please let me know how can I check whether an SAP system is a Unicode/Non-Unicode from SAP GUI?
Thanks in advance,
Adarsh

Hi,
You can check under menu :
System -> Status -> SAP System Data -> Unicode System -> Yes/ No

Sending Order acknowledgment to Non SAP system

Hello All,
Need expert advice in one of the scenario i am facing.
The scenario is
Vendor sends the scheduling agreement order confirmation to SAP system through inbound IDOC with message type ORDRSP......IDOC is posted in SAP.Now there is another third party system which plans the material planning... now this order confirmation needs to be send to that non SAP third party system which has JDBC
client needs the order confirmation data (SA no.,,co code...Item number....committed qty...delivery date...material no... plant) in flat file format only
please suggest the possible ways to overcome.

Hi NR,
What I understand from above is -
1. Inbound IDoc getting posted in SAP
2. Confirmation needs to be send to Non-SAP system which uses JDBC/Database
3. They want only Flat Files.
To answer above questions/scenarios - you have 2 choices
1. Proxy to JDBC Approach Directly post confirmation data to third party database.
How to do this -
a. Open ports with third party. - Check Connectivity stuff.
b. get databases details and configure receiver JDBC Adapter in your side
2. Proxy to SecureFTP - By this approach you will place a CSV file to securedFTP decided by you and your third party from where third party job will pick that file and post it to their database.
Regards
Aashish Sinha

Problem publishing database contents from non-unicode to unicode system

Hello everyone!
We just set up a new SAP WAS based on Netweaver 2004 as a unicode system. Out problem now is that we have a content management system on our non-unicode system and that we are publishing the contents via rfc to the WAS unicode system to display the contents online. the contents are stored in our own database tables.
The problem thereby is that many texts pasted from microsoft word contain special characters like bullets, long minus or low-9 quotation marks which are not correctly displayed in the unicode system / on the website. we already found out that it has something to do with the codepage. the sap notes say we should use 1160 instead of 1100 and that the transaction SPUMG would be helpful. but we are not able to select any tables there.
so now we do not know what to do exactly. do we have to change something in our non-unicode system or do we have to conversion in our unicode system. and what happends if content containing special microsoft word characters is published after the spumg conversion? do we have to to this frequently?
We would be glad if anyone could help.
Thanks a lot!

Hi Martin,
thanks for your quick answer.
You got me right. We have a local non-Unicode SAP HCM Netweaver 2004 system running a self-developed web based content management system / wiki. The texts entered in the bsp application are stored in a string field in our database table. Actually we publish the contents to a WAS 6.20 non-Unicode system with the same database tables to provide the content via BSP for the public. Everything is working fine including the special characters.
Now we want to replace the WAS 6.20 non-Unicode system by a new WAS 7.0/2004 Unicode system. But when publishing the contents via the same RFC function module to the new system the special characters seem to be damaged. We are not able to replace them with abap commands and when they are displayed on the website we only see "boxes".
If I get you right we have to run SPUMG on our nw 2004 non-unicode productive hcm system, right? but isn't there a danger to damage existing contents?
Best regards,
Stefan

Unicode and non-unicode string data types Issue with 2008 SSIS Package

Hi All,
I am converting a 2005 SSIS Package to 2008. I have a task which has SQL Server as the source and Oracle as the destination. I copy the data from a SQL server view with a field nvarchar(10) to a field of a oracle table varchar(10). The package executes fine
on my local when i use the data transformation task to convert to DT_STR. But when I deploy the dtsx file on the server and try to run from an SQL Job Agent it gives me the unicode and non-unicode string data types error for the field. I have checked the registry
settings and its the same in my local and the server. Tried both the data conversion task and Derived Column task but with no luck. Pls suggest me what changes are required in my package to run it from the SQL Agent Job.
Thanks.

What is Unicode and non Unicode data formats
Unicode :
A Unicode character takes more bytes to store the data in the database. As we all know, many global industries wants to increase their business worldwide and grow at the same time, they would want to widen their business by providing
services to the customers worldwide by supporting different languages like Chinese, Japanese, Korean and Arabic. Many websites these days are supporting international languages to do their business and to attract more and more customers and that makes life
easier for both the parties.
To store the customer data into the database the database must support a mechanism to store the international characters, storing these characters is not easy, and many database vendors have to revised their strategies and come
up with new mechanisms to support or to store these international characters in the database. Some of the big vendors like Oracle, Microsoft, IBM and other database vendors started providing the international character support so that the data can be stored
and retrieved accordingly to avoid any hiccups while doing business with the international customers.
The difference in storing character data between Unicode and non-Unicode depends on whether non-Unicode data is stored by using double-byte character sets. All non-East Asian languages and the Thai language store non-Unicode characters
in single bytes. Therefore, storing these languages as Unicode uses two times the space that is used specifying a non-Unicode code page. On the other hand, the non-Unicode code pages of many other Asian languages specify character storage in double-byte character
sets (DBCS). Therefore, for these languages, there is almost no difference in storage between non-Unicode and Unicode.
Encoding Formats:
Some of the common encoding formats for Unicode are UCS-2, UTF-8, UTF-16, UTF-32 have been made available by database vendors to their customers. For SQL Server 7.0 and higher versions Microsoft uses the encoding format UCS-2 to store the UTF-8 data. Under
this mechanism, all Unicode characters are stored by using 2 bytes.
Unicode data can be encoded in many different ways. UCS-2 and UTF-8 are two common ways to store bit patterns that represent Unicode characters. Microsoft Windows NT, SQL Server, Java, COM, and the SQL Server ODBC driver and OLEDB
provider all internally represent Unicode data as UCS-2.
The options for using SQL Server 7.0 or SQL Server 2000 as a backend server for an application that sends and receives Unicode data that is encoded as UTF-8 include:
For example, if your business is using a website supporting ASP pages, then this is what happens:
If your application uses Active Server Pages (ASP) and you are using Internet Information Server (IIS) 5.0 and Microsoft Windows 2000, you can add "<% Session.Codepage=65001 %>" to your server-side ASP script.
This instructs IIS to convert all dynamically generated strings (example: Response.Write) from UCS-2 to UTF-8 automatically before sending them to the client.
If you do not want to enable sessions, you can alternatively use the server-side directive "<%@ CodePage=65001 %>".
Any UTF-8 data sent from the client to the server via GET or POST is also converted to UCS-2 automatically. The Session.Codepage property is the recommended method to handle UTF-8 data within a web application. This Codepage
setting is not available on IIS 4.0 and Windows NT 4.0.
Sorting and other operations :
The effect of Unicode data on performance is complicated by a variety of factors that include the following:
1. The difference between Unicode sorting rules and non-Unicode sorting rules
2. The difference between sorting double-byte and single-byte characters
3. Code page conversion between client and server
Performing operations like >, <, ORDER BY are resource intensive and will be difficult to get correct results if the codepage conversion between client and server is not available.
Sorting lots of Unicode data can be slower than non-Unicode data, because the data is stored in double bytes. On the other hand, sorting Asian characters in Unicode is faster than sorting Asian DBCS data in a specific code page,
because DBCS data is actually a mixture of single-byte and double-byte widths, while Unicode characters are fixed-width.
Non-Unicode :
Non Unicode is exactly opposite to Unicode. Using non Unicode it is easy to store languages like ‘English’ but not other Asian languages that need more bits to store correctly otherwise truncation will occur.
Now, let’s see some of the advantages of not storing the data in Unicode format:
1. It takes less space to store the data in the database hence we will save lot of hard disk space.
2. Moving of database files from one server to other takes less time.
3. Backup and restore of the database makes huge impact and it is good for DBA’s that it takes less time
Non-Unicode vs. Unicode Data Types: Comparison Chart
The primary difference between unicode and non-Unicode data types is the ability of Unicode to easily handle the storage of foreign language characters which also requires more storage space.
Non-Unicode
Unicode
(char, varchar, text)
(nchar, nvarchar, ntext)
Stores data in fixed or variable length
Same as non-Unicode
char: data is padded with blanks to fill the field size. For example, if a char(10) field contains 5 characters the system will pad it with 5 blanks
nchar: same as char
varchar: stores actual value and does not pad with blanks
nvarchar: same as varchar
requires 1 byte of storage
requires 2 bytes of storage
char and varchar: can store up to 8000 characters
nchar and nvarchar: can store up to 4000 characters
Best suited for US English: "One problem with data types that use 1 byte to encode each character is that the data type can only represent 256 different characters. This forces multiple
encoding specifications (or code pages) for different alphabets such as European alphabets, which are relatively small. It is also impossible to handle systems such as the Japanese Kanji or Korean Hangul alphabets that have thousands of characters."<sup>1</sup>
Best suited for systems that need to support at least one foreign language: "The Unicode specification defines a single encoding scheme for most characters widely used in businesses around the world.
All computers consistently translate the bit patterns in Unicode data into characters using the single Unicode specification. This ensures that the same bit pattern is always converted to the same character on all computers. Data can be freely transferred
from one database or computer to another without concern that the receiving system will translate the bit patterns into characters incorrectly.
https://irfansworld.wordpress.com/2011/01/25/what-is-unicode-and-non-unicode-data-formats/
Thanks Shiven:) If Answer is Helpful, Please Vote

Transport from Non-Unicode to Unicode system

I'd like to transfer program from SAP 4.6c to SAP ECC 6.0.
But source system is Non-Unicode, and target system is Unicode.
I exported transport request from SAP 4.6c into files:
K920948.D51
R920948.D51
then importing into SAP ECC 6.0 by STMS and getting error:
"Program ZRM06EF00: Syntax error in line 000000
The program 'ZRM06EF00' is not Unicode-compatible,according to its program attributes."
What should i do?

Hi:
It is required to make the change accordingly of UCCHECK.
So upload in the higher version, and check its syntax error first and then activate.
Regards
Shashi

ABAP development in a non-unicode system

Does anyone have a "list of abap development considerations" when developing ABAP in a 4.6C system to also be sensitive to an upcoming UNICODE conversion project, that is, What do I need to be sensitive to concerning unicode when developing in a non-unicode 4.6C system to make the upgrade to unicode of these programs easier .

You can check the documents available at market place.
service.sap.com/unicode under section
Sap netweaver-> Sap Netweaver in Detail -> Application Platform -> Unicode -> ABAP and Unicode Library.
There is one document which is specifically related to 4.6c (Vorbereitung von ABAP Programmen für Unicode in 4.6C/D) but its in German.
You can go through the other documents and see whichever is applicable for 4.6c
Regards,
Abhishek

Creating RFC Destination For UNICODE system From NON-UNICODE system

hi
how can i create RFC Destination For UNICODE system( XI ) From NON-UNICODE (R/3) system.
thanks and regards
Mithlesh Kumar Jha

Hi,
Check these blogs , Hope u would be getting some idea
<b>/people/thomas.jung3/blog/2004/06/24/bsp-150-a-developer146s-journal-part-v-xml-for-rfcs
/people/thomas.jung3/blog/2004/11/15/bsp-150-a-developer146s-journal-part-xiii-developing-abap-webservices
/people/sap.user72/blog/2004/06/19/how-i-started-with-sap-web-development</b>
Regards,
Sridhar Reddy

How to create a non-unicode transport on a unicode system?

Folks,
Occassionally, I have to create transports for some of the functions from our unicode-based SAP system. The created transports by default are unicode and thus cannot be installed on a non-unicode SAP client. Is there a way to create non-unicode transport from a unicode SAP system?
Note that the transport contains only the code (function modules). There is no data.
Thank you in advance for your help.
Regards,
Peter

Hi Peter,
Note 638357 - Transport between Unicode systems and non-Unicode systems
Regards
Ashok Dalai

Sending special characters to non-unicode non-sap system: user exit

Similar Messages

Maybe you are looking for