File Transfer non-unicode - unicode via client

Question

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

Answer 1

check out the <b>OPEN DATASET - Mode - {TEXT MODE ENCODING {DEFAULT|UTF-8|NON-UNICODE}} </b> 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