UTF-8 to non-unicode RFC - encoding

Hi,
I get data via SOAP UTF-8 and send them with some simple mappings to a RFC receiver non-unicode. How can I post special characters?
In sender payload i see and i expected to get A & B in SAP but i get A & B in SAP. In the RFC receiver adapter i don't see any setting for codepage.
Anyone an idea?
Regards
Jörg

Hi,
The first thing is that XI is unicode so if you are sending special char which are UTF-8 encoded then you should be seeing them in XI in the payload monitor. Can you check that first?
Now if the target is Not Unicode then what is the encoding on the target side? You can encode these special chars in XI and then pass it on in the encoding format the target system expects. One more thing in the SM59 transaction in XI for the Receiving R/3 system you can specify the Char Set encoding. Make sure you check and based on that your encoding should work. try this out.
thanks
Ashish

Similar Messages

Truncated record in OPEN DATASET ENCODING NON-UNICODE

Hi,
I have to read a Unicode created file into a non-unicode SAP System, version 4.7.
When I make the OPEN DATASET using ENCODING UTF-8 y get a CONVT_CODEPAGE dump. That´s odd cause my system is non-unicode. I don´t wanna use IGNORING CONVERSION ERRORS attribute, the output will be corrupt.
But when I use ENCODING NON-UNICODE or ENCODING DEFAULT the READ DATASET mysteriously truncate the record which try to read from real 401 characters to 361 characters. Variable is string.
I can see full records through AL11.
Any ideas?
Thanks,
Pablo.

Hi,
Try using:
open dataset filename in text mode encoding default for input
ignoring conversion errors.
As said in AL11 its coming so the above code is used for that.
Hope this will surely help you !!!
Regards,
Punit

Difference between IN LEGACY TEXT MODE & TEXT MODE ENCODING NON-UNICODE

Hi,
We're upgrading to ECC5 and the 'open dataset' command needs amending if the program is flagged for Unicode (which usually occurrs in user/fm exits). Therefore is ECC5 this command is no longer valid:
"open dataset DSN in text mode"
We currently interface with systems that may not have unicode enabled. Yet we have not enabled unicode in our own system just yet.
So we think these two commands are the most approriate for replacing the 'old' open dataset command:
"open dataset DSN for input in TEXT MODE encoding NON-UNICODE"
"open dataset DSN in LEGACY TEXT MODE for input"
However we're not really sure what the difference between these two commands is?
Has anyone worked with these commands?
Could you offer some help as to their differences and when each should be used?
Many thanks!

Hi Robert,
   Here is an excerpt from sap documentation.
... TEXT MODE ENCODING {DEFAULT|UTF-8|NON-UNICODE}
Effect:
The addition IN TEXT MODE opens the file as a text file. The addition ENCODING defines how the characters are represented in the text file. When writing in a text file, the content of a data object is converted to the representation entered after ENCODING, and transferred to the file. If the data type is character-type and flat, trailing blanks are cut off. In the data type string, trailing blanks are not cut off. The end-of-line marking of the relevant platform is applied to the transferred data by default. When reading from a text file, the content of the file is read until the next end-of-line marking, converted from the format specified after ENCODING into the current character format, and transferred to a data object.
The end-of-line marking depends on the operating system of the application server. In the MS Windows operating systems, the markings "CRLF" and " LF" are possible, while under Unix, only "LF" is used. If, when using Windows, an existing file is opened without the TYPE addition (see os_addition), the first end-of-line marking is found and used for the whole file. If a new file is created without the TYPE addition, the content of the profile parameter abap/NTfmode is used. If the profile parameter is not set, "CRLF" is used. If a file with the TYPE addition is opened and a valid value is contained in attr, this value is used.
In Unicode programs, only the content of character-type data objects can be transferred to text files and read from text files. The addition ENCODING must be specified in Unicode programs, and can only be omitted in non-Unicode programs.
The additions after ENCODING determine in which character representation the content of the file is handled.
DEFAULT
In a Unicode system, the designation DEFAULT corresponds to the designation UTF-8, and the designation NON-UNICODE in a non-Unicode system.
UTF-8
The characters in the file are handled according to the Unicode character representation UTF-8.
NON-UNICODE
In a non-Unicode system, the data is read or written without being converted. In a Unicode system,the characters in the file are handled according to the non-Unicode-codepage that would be assigned to the current text environment according to the database table TCP0C, at the time of reading or writing in a non-Unicode system.
If the addition ENCODING is not specified in non-Unicode programs, the addition NON-UNICODE is used implicitly.
... LEGACY TEXT MODE [{BIG|LITTLE} ENDIAN] [CODE PAGE cp]
Effect:
Opening a Legacyfile. The addition IN LEGACY TEXT MODE opens the file as a legacy text file. As with legacy binary files, the byte order and the codepage with which the content of the file should be handled can also be specified. The syntax and meaning of {BIG|LITTLE} ENDIAN and CODE PAGE cp are the same as for legacy binary files.
In contrast to legacy binary files, the trailing blanks in a legacy file are cut off when writing character-type flat data objects in a legacy text file. As for a text file, an end-of-line marking is also applied to the transferred data. In contrast to text files opened with the addition INTEXT MODE, Unicode programs do not check whether the data objects used for reading or writing are character-type. Furthermore, the LENGTH additions of the statements READ DATASET and TRANSFER are used for counting in bytes in legacy text files and in the units of a character represented in the memory for text files.
Note:
As with legacy binary files, text files that have been written in a non-Unicode system can be accessed in Unicode systems as legacy text files, and the content is converted accordingly.
Example
A file test.dat is created as a text file, filled with data, changed, and exported. As every TRANSFER statement applies end-of-line marking to written content, after the change, the content of the file has two lines. The first line contains "12ABCD". The second line contains "890". The character "7" has been overwritten by the end-of-line marking of the first line.
DATA: file   TYPE string VALUE `test.dat`,
      result TYPE string.
OPEN DATASET file FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
TRANSFER `1234567890` TO file.
CLOSE DATASET file.
OPEN DATASET file FOR UPDATE IN TEXT MODE ENCODING DEFAULT
                             AT POSITION 2.
TRANSFER `ABCD` TO file.
CLOSE DATASET file.
OPEN DATASET file FOR INPUT IN TEXT MODE ENCODING DEFAULT.
WHILE sy-subrc = 0.
READ DATASET file INTO result.
WRITE / result.
ENDWHILE.
CLOSE DATASET file.
Regards,
Ravi

File Transfer non-unicode - unicode via client

Hello.
I downloaded a binary file from a SAP 4.0 system to my client (win2k) with OPEN DATASET (to read the file on the app server) and WS_DOWNLOAD (to save it to the client).
Now i want to upload this file from my client to a 6.40 unicode system. Therefore i do the following:
- GUI_UPLOAD to get the file from the client into an internal table
- OPEN DATASET dsn FOR OUTPUT IN BINARY MODE to save the contents of the internal table to the file system of the app server.
This works pretty well on non-unicode systems but does not work properly for unicode systems.
Which options do i have to use? Anything with code pages?!
THX
--MIKE

check out the OPEN DATASET - Mode - {TEXT MODE ENCODING {DEFAULT|UTF-8|NON-UNICODE}} option .
The additions after ENCODING determine in which character representation the content of the file is handled.
DEFAULT
In a Unicode system, the designation DEFAULT corresponds to the designation UTF-8, and the designation NON-UNICODE in a non-Unicode system.
UTF-8
The characters in the file are handled according to the Unicode character representation UTF-8.
NON-UNICODE
In a non-Unicode system, the data is read or written without being converted. In a Unicode system,the characters in the file are handled according to the non-Unicode-codepage that would be assigned to the current text environment according to the database table TCP0C, at the time of reading or writing in a non-Unicode system.
Check out the ABAP Key Word Documentation .
Regards
Raja

RFC destination definition with non-unicode external program

Hello All,
we have one issue with our RFID system connecting to WM system (SWD).
For most functions, external RFID server/middleware makes RFC call to SAP system. Means, from outside system to inside SAP. This seems to be working fine.
But in one case, SAP needs to print label to RFID printer. In this case, SAP is calling external RFID server/middleware using RFC destination. Means, from inside SAP to outside system. This is failing.
We think this has something to do with ECC60 being unicode system, and the RFC destination setup. We define rfc destination "ZRFID_SSI" in SM59. We define it same way as in as-is SSI 4.6B production system. But in SWD ECC60 system, SM59 has more options. We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server. RFC destination is actually working ok.
To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI. Listener on RFID server/middleware will respond to function call. This also seems to be working. But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0". (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
Compared with production environment, everything is the same, except that SAP is unicode system. So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data. I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange. Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
Anyone know how to help ?

Hi Jeongbae,
as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
In earlier releases, this is not possible.
In general, SAP systems use the logon language (SY-LANGU) to determine the code page, if this is available.
Please check SAP note 788239.
Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
In addition I would recommend to have a look at SAP note 1021459.
However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
Best regards,
Nils Buerckel
SAP AG

Report Script output in UTF-8 code with Non-Unicode Application

Essbase Nation,
Report Script output (.txt) file is being coded as UTF-8 when the application is set to Non-unicode. This coding creates a signature character in the first line of the text file, which in turn shows up when we import the file into Microsoft Access. Does anyone know how to change the coding of the output file or know who to remove the UTF-8 signature character.
Any adive is greatly appreciated.
Thank you.
Concerned Admin

You may be able to find a text editor that can do the conversion. Alternatively, I have converted from one encoding to the another programmatically using Java as well.
Tim Tow
Applied OLAP, Inc

OPEN DATASET file FOR OUTPUT IN TEXT MODE ENCODING NON-UNICODE

Hi There,
I also have the similar issue. I am able to write the data into appliaction server in Chinese Characters using :OPEN DATASET datei FOR OUTPUT IN TEXT MODE ENCODING DEFAULT or OPEN DATASET datei FOR OUTPUT IN TEXT MODE ENCODING UTF-8. But when i save that file into my presentation server manually, all the chinese characters are showing as Junk.
When i use OPEN DATASET datei FOR OUTPUT IN TEXT MODE ENCODING NON-UNICODE, giving runtime error and when i use OPEN DATASET datei FOR OUTPUT IN TEXT MODE ENCODING NON-UNICODE IGNORING CONVERSION ERRORS, No error but application server output itself showing as Junk characters.
Could you please suggest me what you have done?
Regards,
Chaitanya A

Hi,
Use this
OPEN DATASET File_path FOR OUTPUT IN TEXT MODE ENCODING NON-UNICODE
WITH SMART LINEFEED
it will definitely work.
Regards,
Manesh. R

Gettin data from SAP R/3 4.7 unicode sys to SAP ERP non-unicode sys via RFC

We are trying to get data from SAP R/3 4.7 unicode sys to SAP ERP non-unicode sys via RFC. We are reading field from the database via FM and this field got converted by SAP standard Method (CL_ABAP_CONTAINER_UTILITIES=>fill_CONTAINER_C) from structure. When reading this field from ERP sys and converted back to structure using SAP standard Method the value is un-accurate, and different(blank) giving values.
How, if the data originally was a char or numeric it works fine, but not for decimal.
best regards,
Abu-Qaht

I have a range fields with different type of ranges, am saving these to the database by converting them to a string via the same method. I got the same problem so I tried to convert the string to xstring using function SCMS_STRING_TO_XSTRING, before send it to the other system, but the function raised an exception: CX_SY_CONVERSION_CODEPAGE

RFC Destination - Unicode / non - Unicode behavior

Hi All,
In our current production system the RFC destination from R3 to Xi is non-unicode.We have currently 300 Interfaces running using this RFC destination in production.
In few upcoming requirements for some 15 Interfaces some special characters will come from R3 to Xi system.In this case we need a unicode RFC Destination.
I have a query here , can i go ahead and change the existing RFC destination to Unicode or is it suggestible to create a new RFC destination only for these 15 Interfaces?
Need expert advice on this?
<<Text removed>>
Regards,
RK
Edited by: Matt on Oct 5, 2011 9:38 AM

Hello,
The Non-Unicode Single code page systems are supported by SAP for older applications for historical reasons - unicode was not available when they were released. These systems are restricted to only processing characters from their specific code page. This means their can be restrictions if they need to support language combinations that span multiple code pages - basically it is not possible. In addition some languages are not fully available at all for single code page systems like Thai. In addition the Euro symbol is not available.
Unicode is the future for all applications - SAP or otherwise. The significance at the moment is where customers who needs to convert to unicode to support additional business requirements like additional languages. Converting a system, although a simple process is not a trivial process in terms of time and resources.
So u can go ahead and change the existing RFC destination to Unicode .it will not create any prob. for other interfaces which are using non unicode setting.
Regards
Monica

Passing chinese character from RFC call between unicode & non unicode syst.

Hi Experts,
I am making a RFC call from an ABAP in non unicode system to a Function module in Unicode system and filling the itab fields in ABAP by using move statement and using offset in order to populate amount fields correctly from flat structure tables returned by function module. But i am facing problem in getting chinese characters correctly in return from the Remote Function Module.
        CALL FUNCTION 'ZFXX_GET_CLR_OI'
          STARTING NEW TASK W_TASKNAME
          DESTINATION S_RFCDES-LOW
          PERFORMING F3100_GET_RFC_DATA ON END OF TASK
          EXPORTING
            P_WAERS               = P_WAERS             "Screen Curr
            P_AUGDT               = P_AUGDT             "Clearing date
            P_BUKRS               = P_BUKRS             "Comp Code
          TABLES
            T_SEL_TABLE           = T_SEL_TABLE
            T_OUTPUT              = T_MCDATA
            T_ERRORS              = T_EMCDATA
          EXCEPTIONS
            COMMUNICATION_FAILURE = 1
            SYSTEM_FAILURE        = 2
            OTHERS                = 3.
       MOVE : t_mcdata1-line+0(32)   TO t_succs-awsys,
               t_mcdata1-line+32(4)   TO t_succs-bukrs,
               t_mcdata1-line+36(10) TO t_succs-belnr,
               t_mcdata1-line+46(4)   TO t_succs-gjahr,
               t_mcdata1-line+50(1)   TO t_succs-shkzg,
               t_mcdata1-line+51(2)   TO t_succs-bschl,
               t_mcdata1-line+53(4)   TO t_succs-gsber,
               t_mcdata1-line+57(16) TO t_succs-dmbtr,
               t_mcdata1-line+73(16) TO t_succs-wrbtr,
               t_mcdata1-line+89(5)   TO t_succs-pswsl,
               t_mcdata1-line+94(6)   TO t_succs-vbund,
               t_mcdata1-line+100(10) TO t_succs-hkont,
               t_mcdata1-line+110(10) TO t_succs-prctr,
               t_mcdata1-line+120(16) TO t_succs-dmbe2,
               t_mcdata1-line+136(20) TO t_succs-txt20.
        APPEND t_succs.
Can anybody suggest or advice me on it ? Any help or suggestion would be appreciated.
Thanks in advance,
Akash

.

UTF-8 stored in VARCHAR2 on a non-Unicode DB

Hi there,
we have a company that implements storing Unicode data in Oracle in the following way:
A plain VARCHAR2 on a non-Unicode DB (charset is actually WE8MSWIN1252) receives UTF-8 coded data.
As client and server have the same setting for NLS_LANG, no conversion takes place, and the app will run fine.
(in my eyes, a clean way to set this up would be utilizing NVARCHAR fields for this, but this is no option)
But: how can I do query based on these columns without getting garbage for each non-ASCII character?
I imagine setting up views for that purpose, but I need the syntax on how to re-interpret the UTF-8 data coming from a VARCHAR2 field.
I tried the following:
SELECT CONVERT(column, 'WE8MSWIN1252', 'AL32UTF8') FROM table where ...
This will give me the right data on a client with cp 1252 set up, with the restriction to 8 bit output.
Now I would like to have a Unicode-capable application like SQL*Developer to be fully capable of dealing with the Unicode data, but I guess, for that to work, I would need the DB to deliver a NVCHAR2 output from the above query?
Any help and comments appreciated.
Tom
Message was edited by: snmdla

we have a company that implements storing Unicode data in Oracle in the following way:
No - they don't. They are NOT storing unicode data - they are storing individual one-byte characters and using that VARCHAR2 column as a BLOB. Ask them how, of if, they query the data.
A plain VARCHAR2 on a non-Unicode DB (charset is actually WE8MSWIN1252) receives UTF-8 coded data.
No - it doesn't. It receives a string of one byte characters in the WE8MSWIN1252 character set. It does not know, or care, what those one-byte characters represent. All you are doing is storing BINARY data in that VARCHAR2 column one byte at a time. When you query it you will get one or several bytes back - but since Oracle thinks it is really character data, when it is actually binary, you can only match it by matching those one-byte characters.
I imagine setting up views for that purpose, but I need the syntax on how to re-interpret the UTF-8 data coming from a VARCHAR2 field.
You don't have UTF-8 data - you have a BLOB that you need to convert to UTF-8 data. You can use the DBMS_LOB.CONVERTTOCLOB procedure to do the conversion and specify the character set to use. See the DBMD_LOB API
http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_lob.htm#i1020356
CONVERTTOCLOB Procedure
This procedure takes a source BLOB instance, converts the binary data in the source instance to character data using the character set you specify, writes the character data to a destination CLOB or NCLOB instance, and returns the new offsets.
See this AskTom article for further review
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:3575852900346063772

Unicode Or Non-Unicode for RFC Destination.

Hi,
while creating a RFC Destination, what role does a Unicode Setting play.
Should this by default always set to Unicode. or does it vary from system to system. Is XI Uniode compatible or not.
Regards,
Sita Rama Raju

Hi Raju,
As far as i know, by default, this setting is non-unicode, and that whenever you change the setting to unicode, you need to run a unicode test or something.
cheers,
Prashanth

RFC FM call problem uni-code to non-unicode?

Hi SDN,
I am calling RFC fun. module from non-unicode system to a uni-code system.
i am calling this FM from various systems is there any way in target system to know whether the call is from uni-code system or non-unicode system.
Regards,
Rahul.

Hi,
I think it is not possible for the reason that an RFC function module can be called from not only an SAP system but also from any non-SAP system like a J2EE Application in which case it does not make sense to know if the calling system in unicode or not.
But still check with the SYST structure in SE11 if there is any system field.
Regards,
Sesh

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
/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
Regards,
Sridhar Reddy

Encoding Problem: non-Unicode Data to Unicode format of XI

Hi SDN,
I have a JDBC sender to SAP BW scenario. The database is MS SQL server.
The code page of db CP1CIAS
Description:SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data
Some fields with values like ZAKADY TWORZYW SZTUCZNYCH are failing in XI Mapping with error
Fatal Error: com.sap.engine.lib.xml.parser.Parser~
XMLParser : #0 not allowed in Character data sections
in the trace.
Please help how should i get over this code page errors. By installing this code page on XI server help?

There is no such global setting, this is b/c your source has Unicode I trust, and the only one other thing to try would be this:
Arthur My Blog

UTF-8 to non-unicode RFC - encoding

Similar Messages

Maybe you are looking for