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

Similar Messages

Open dataset filename for output in text mode encoding default

Hi,
When I excute this command I get a sy-subrc = 0, but no file is created. This happens in an ECC 6.0 system. In 4.6C works ok.
filename has the following structure '
server\directory\filename'
What am I doing wrong??
Thank you very much for your your help.
Regards.

Hi,
Can u tell what syntax u have written for open statement.
In programs with active Unicode check, you must specify the access type (such as ... FOR INPUT, ... FOR OUTPUT, and so on) and the mode (such as ... IN TEXT MODE, ... IN BINARY MODE, and so on). If the file is opened using ... IN TEXT MODE, you must still use the addition ... ENCODING. If the Unicode check is enabled, it is possible to use file names containing blanks.
Regards,
Sruthi

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

Problem writing file ANSI to UTF-8. OPEN DATASET FOR OUTPUT IN TEXT MODE

Hello everybody,
My report needs to create a file in ANSI so I am using this sentence: * "OPEN DATASET p_dir_a FOR OUTPUT IN TEXT MODE ENCODING DEFAULT."* almost all charters in the file are well generating excepting for this two: ( Á ) & ( Í ) because SAP assigns the same code to both characters ( Ã? ) = 'xC3' which is not correct, the right code should be ( Á ) = 'xC1' ( Í ) = 'xCD' respectively
from this string = ( ÁÉÍÓÚáéíóúàèìòùÀÈÌÒÙ ) only those two characters are wrong converted.
Also I tray to catch a conversion error with this sentence:
          TRY.
            TRANSFER <field> TO p_dir_a NO END OF LINE.
          CATCH cx_sy_conversion_codepage.
            MESSAGE 'error' type 'I'.
        ENDTRY.
but never enters in it.
Does anyone know where I can configure SAP to SET this value correctly?
Thanks for your help.

was a server problem, not SAP

OPEN DATASET FILENAME FOR OUTPUT.

HI,
While doing unicode enable inECC6.0 FOLLOWING ERROR IS COMING.hOW IT WILL BE RESOLVED.
oPEN DATASET physname FOR OUTPUT.

Hello,
For opendataset u need to add the below coding.
open dataset 'filename' for output in text mode encoding default. ( Based on ur filetype)
binary mode encoding default
if it not a unicode system then non unicoding must be added.
N.B
In the Transfer stmt the data types apart from CNDT will result dump.
So please ensure that all are of CNDT types.
With Regards,
Sumodh.P

OPEN DATASET FOR INPUT IN TEXT MODE - linesize issue

Hi,
I faced a problem when opened ANSI file with CYRILLIC in ECC 6.0 Unicode system - the system cuts the line to 250 characters. Below is snip of code:
REPORT Z_TEST_01 LINE-SIZE 1023.
DATA:
file TYPE char40 VALUE 'ansi_file.txt',
line TYPE char1024, len TYPE i.
OPEN DATASET file FOR INPUT IN TEXT MODE ENCODING DEFAULT.
WHILE sy-subrc = 0.
      READ DATASET file INTO line ACTUAL LENGTH len.
        WRITE: / len, line.
ENDWHILE.
CLOSE DATASET file.
In this case, variable LEN always get value 250. File-content is correctly converted from ANSI and all CYRILLIC is displayed to the screen. I changed type for LINE - initialy the type was STRING, actially.
Further, tried to open it in BINARY - like this:
DATA:
file TYPE char40 VALUE 'ansi_file.txt',
line TYPE char1024, len TYPE i.
FIELD-SYMBOLS <hex_container> TYPE x.
OPEN DATASET file FOR INPUT IN BINARY MODE.
ASSIGN line TO <hex_container> CASTING.
DO.
READ DATASET file INTO <hex_container>.
IF sy-subrc = 0.
    WRITE: / line.
ELSE.
    EXIT.
ENDIF.
ENDDO.
CLOSE DATASET file.
WRITE: / line.
In this case I got bigger linesize (obviously 1024), but faced conversion issues - the file contains some CYRILLIC and it is messed. Played for few hours with conversions - using additions: IN LEGACY BINARY MODE... BIG/LITTLE ENDIAN, CODE PAGE... without success. So decided to ask...
Well, I searched SDN for a similar issue, but didn't found, except this one:
Re: OPEN DATASET STRING Problem
Could someone points me what am I doing wrong? How can I read my ANSI file with line-size more than 250 chars? Actually, in my case line size may vary up to 1800 chars. Further, afrer conversion and some validation, I should save it back to the AS.
Many thans in advance.
Regards,
Ivaylo Mutafchiev

Sorry for the noise - it is not an issue anymore.

Data transfer error open dataset files

hi,
When i try to create a excel or text in my application server using open dataset.
i.e
l_filename type rlgrap-filename value '/tmp/down.txt'.
I got a short dump during the run time
i got the output and put into an internal table.
the following code has been used.
form user_command using r_ucomm like sy-ucomm
rs_selfield type slis_selfield.
if r_ucomm = 'confirm' .
OPEN DATASET l_fname FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
LOOP AT it_out INTO wa_out.
IF sy-subrc = 0.
TRANSFER wa_out TO l_filename.
ENDIF.
ENDLOOP.
endform.
during the execution i hv a button alv grid outpu. when i click the button the file should be transferred.
but NO authorization to open the file "/tmp/down.txt".
and the error is pointed in the opendataset line.
Please tell me where i am wrong . and help me in resoving this.

Try this..instead of moving field by field into the file 1st convert all he fields to a character stream..and then move that steam to file. Ex:
loop at internal table into l_h_tbl_file.
concatenate l_h_tbl_file-f1 l_h_tbl_file-f2 l_h_tbl_file-f3
l_h_tbl_file-f4 l_h_tbl_file-f5 into g_string.
TRANSFER g_string TO fu_wk_get_file.
endloop.

Open Dataset : File creation in server

Hi Guys,
I am trying to use
Open dataset dsn for output in text mode encoding default.   " dsn = '
pt-net\taskout\outfile.txt'.
loop at itab.
transfer itab to dsn.
endloop.
to write a file at a destination on a windows NT server For eg :
pt-net\taskout\outfile.txt
I see sy-subrc = 0 at both open dataset and transfer commands in the debugger. But the file is not written.
I can manually create files when I access this path in my explorer. So it is not an access issue.
Also, my SAP application server is a Unix server. But the file I am trying to write is in NT server. THis is for a 3rd party application. Where am I possibly going wrong ? I am able to write this file to the Unix application server path using the above command. But I need to write this in the Windows server.
Do I need first write to Unix path and then FTP it to Windows server ? I can manually do this. But since this program is going to run as a job, I want to automate this..
THanks in advance!!

Hi,
This is my advice:
First write the file in the file system of your application server.
After that find out, what to do for transport on operation system level.
Since SAP allows system calls, you can do it in the same way by program.
I give you some code. Unfortunately it is from Windows to Windows. Nevertheless I hope you can profit by it.
*&      Form file_to_l66
FORM file_to_l66 USING src_fpath
                        dest_fname.
- src_fpath full path of source file
- dest_fname intended file name for destination
DATA:
    parcom(250),
    BEGIN OF tabl OCCURS 0,
      line(200),
    END OF tabl,
    str(250).
drive y free
parcom = 'y:'.
CALL 'SYSTEM' ID 'COMMAND' FIELD parcom
              ID 'TAB'     FIELD tabl-sys.
IF sy-subrc IS INITIAL.
    RAISE file_to_l66_err_drive_y.
ENDIF.
mapping y
128.1.123.1 ServerL66
parcom =
    'net use y:
128.1.123.1\SAPDATA passwd /user:usr01'.
CALL 'SYSTEM' ID 'COMMAND' FIELD parcom
              ID 'TAB'     FIELD tabl-sys.
IF NOT sy-subrc IS INITIAL.
    RAISE file_to_l66_err_mapping_y.
ENDIF.
copying
CONCATENATE 'copy' src_fpath 'y:\' INTO str SEPARATED BY space.
CONCATENATE str dest_fname INTO parcom.
example:
src_fpath = 'e:\trans\l66.xml'
dest_fname = 'l66_20080531235959.xml'
-> parcom = 'copy e:\trans\l66.xml y:\l66_20080531235959.xml'.
CALL 'SYSTEM' ID 'COMMAND' FIELD parcom
              ID 'TAB'     FIELD tabl-sys.
IF NOT sy-subrc IS INITIAL.
    RAISE file_to_l66_err_copying.
ENDIF.
release y
parcom =
    'net use y: /delete'.
CALL 'SYSTEM' ID 'COMMAND' FIELD parcom
                ID 'TAB'     FIELD tabl-sys.
IF NOT sy-subrc IS INITIAL.
    RAISE file_to_l66_err_unmapping_y.
ENDIF.
ENDFORM.                    " file_to_l66
Edited by: Walter Habich on May 22, 2008 4:24 PM

Open Dataset : File Not Created In The Directory

Hi Guru's,
I have a small question, I try trough my code to create a file but when I use the "open dataset" nothing produces. I have no errors and in the debug mode the sy-subrc is always to "0".
w_locdrive    = 'C:\RECON_SUP\'.
w_rec         = '5499728464709 '.     "AO
w_mess        = 'RECON_SUP'.
SELECT /bic/ricr1_003 /bic/ricr1_061
       /bic/ricr1_010 /bic/ricr1_091 /bic/rikr2_001
      INTO CORRESPONDING FIELDS OF TABLE i_2006 FROM /bic/aro_r200600.
CONCATENATE w_mess '.' w_send '.' w_rec '.' sy-datum sy-uzeit '.txt' INTO w_name.
CONCATENATE w_locdrive w_name INTO w_path.
IF i_2006[] IS NOT INITIAL.
SORT i_2006 BY /bic/ricr1_003.
*Open my file.
OPEN DATASET w_path FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
* Put all records in the file output.
LOOP AT i_2006 INTO wa_2006.
    w_rikr2_001 = wa_2006-/bic/rikr2_001. " Convert the Volume in char Field.
    CONCATENATE wa_2006-/bic/ricr1_003 ';' wa_2006-/bic/ricr1_061 ';' wa_2006-/bic/ricr1_010 ';'
                wa_2006-/bic/ricr1_091 ';' w_rikr2_001
                INTO w_string.
    IF sy-subrc = 0.
      TRANSFER w_string TO w_path.
      CLEAR w_string.
    ENDIF.
ENDLOOP.
Thank you in advance for your help,
Mohamed.

Can you try like this
OPEN DATASET w_path FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
    IF sy-subrc = 0."<---Add here
* Put all records in the file output.
LOOP AT i_2006 INTO wa_2006.
    w_rikr2_001 = wa_2006-/bic/rikr2_001. " Convert the Volume in char Field.
    CONCATENATE wa_2006-/bic/ricr1_003 ';' wa_2006-/bic/ricr1_061 ';' wa_2006-/bic/ricr1_010 ';'
                wa_2006-/bic/ricr1_091 ';' w_rikr2_001
                INTO w_string.
    IF sy-subrc = 0. "<---Remove here
      TRANSFER w_string TO w_path.
      CLEAR w_string.
    ENDIF."<---Remove here
ENDLOOP.
endif."<---Add here

Open dataset file length

Hi Friends,
I am uploading a file into SAP server and I would like to upload with 300 length char. ( I mean The file should contian 300 coloms)
where we can declare the length of the file?
Thanks,
Sridhar

Hi Sridhar,
Define variable of type string or type CHAR(XXX), XXX should be equal or more than expected length of record.
Open dataset in text mode or binary mode.(prefer binary mode - if user will go to OS and see the file by double click prefer text mode so that it will get downloaded in readable format).
if dataset is opened successfully -
Loop at your internal table into string or defined variable .
Use transfer command to transfer each line.
Close the dataset.
Here goes some code:
DATA: lv_file1 TYPE string.
FIELD-SYMBOLS: <f_t_table> TYPE ANY.
lv_file1 = lfile_path.
IF im_binary_mode IS NOT INITIAL.
    OPEN DATASET lv_file1 FOR OUTPUT IN BINARY MODE.
ELSE.
    OPEN DATASET lv_file1 FOR OUTPUT IN TEXT MODE ENCODING DEFAULT .
ENDIF.
IF sy-subrc EQ 0.
    LOOP AT t_table ASSIGNING <f_t_table> .
      TRANSFER <f_t_table> TO lv_file1.
    ENDLOOP.
    CLOSE DATASET lv_file1.
   MESSAGE s027(zdev) RAISING download_success.
ELSE.
    MESSAGE e028(zdev) RAISING download_error.
ENDIF.
Now important thing:
Record with length more than 255 gets downloaded successfuly intext mode but when you try to read it via AL11, CG3Y, or with OPEN dataset- READ- write ..CLOSE dataset you can see only 255 character.
Dont worry about this.
AL11 and CG3Y is unable to display more than 255 char in text mode. if you are writing content of the file on list screen, use OFFSET, like WRITE: /01(500) lv_string.
write statement in AL11/cg3y doesnt have this offset in write so more than 255 length cant be seen.
I hope u get the answer and able to understand this solution.
Bless u.

Opening a file for write access [trailing spaces required]

Hi,
i am opening a file for write access using:
OPEN DATASET W_FILENAME FOR OUTPUT IN TEXT MODE.
However, when i perform transfer W_LINE to W_FILENAME, trailing spaces in W_LINE are trimmed off automatically. I have tried various methods without success.
Appreciate if help can be offered. Thank You~

haiiiiiii,
OPEN DATASET OUTFILE FOR OUTPUT IN TEXT MODE encoding default.
TRANSFER OUTREC TO OUTFILE.
CLOSE DATASET OUTFILE.
here out rec we are moving to the out put file.
for ur requrement concatinate all the fioelds to outrec and then move it to file.
then u wont get any problems with spaces

Bad data added in Open Dataset for output in Binary mode

Hello,
I am getting random bad data being added to the end of the file that is created on the file server when I run the Open Dataset for output in Binary mode. This data sometimes looks like information about the Unix file server. If I do the Open Dataset in Text mode, it does not add the extra bad data.
** transfer file to Unix File server
       DATA: LIN TYPE P.
                                                                                OPEN DATASET P_APPFIL FOR OUTPUT IN BINARY MODE.
                                                                                DESCRIBE TABLE XML_TAB LINES LIN.
                                                                                IF LIN EQ 0.
         EXIT.
       ELSE.
         LOOP AT XML_TAB.
           TRANSFER XML_TAB TO P_APPFIL.
         ENDLOOP.
       ENDIF.
                                                                                CLOSE DATASET P_APPFIL.
Running the program 2 times with the same variant will give different results.
For example, the data in file should end with </cPedigreeXML> but it added data as shown below:
</cPedigreeXML>8                I   X-UNKNOWN                                                 9                    I   X-UNKNOWN                                                10
            C   X-UNKNOWN
Then, when the program was run again with the same selections, it did not add the erroneous data at the end.
This is a real problem because the bad data that gets added causes the file to error in the application. Any help would be greatly appreciated.
Thanks,
Bob

Hi Bob,
      Use CLEAR statement after TRANSFER statement and check once.
     IF LIN EQ 0.
         EXIT.
       ELSE.
         LOOP AT XML_TAB.
           TRANSFER XML_TAB TO P_APPFIL.
           <b>CLEAR XML_TAB.</b>
         ENDLOOP.
       ENDIF.
Thanks,
Vinay

FileNotFoundException thrown when opening a file for writing from EJB

Hi,
I know it is against EJB rules that access file IO from EJB. However we have a legacy system to working with and we need to generate a text file on file system.
Weblogic (we are using 10.3) allows open a file for read from EJB. When we tried to open a writer like below:
BufferedWriter writer = new BufferedWriter( new FileWriter(fileName, false));
FileNotFoundException was thrown from the native method of open. The fileName is an absolute path and permission is properly set. The same piece of code can execute correctly in a test application with same filename.
Does anyone know how to achieve this or whether Weblogic just forbids this kind of output access?

Sorry guys. Just double-checked the source code and found out a bug produced wrong filename, the filename was surrounded by "", so FileNotFoundException is a correct result.
Weblogic does allow read/write external file.

I need to make a pdf document, made in photoshop, 'page turn' and then add it to my website. I know I can do this in indesign but indesign will not open pdf files for some inexplicable reason. Any ideas how I can do it without completely starting again?

I need to make a pdf document, already made in photoshop, 'page turn' and then add it to my website as an e-brochure. I know I can do this in indesign but indesign will not open pdf files for some inexplicable reason. Any ideas how I can do it without completely starting again?

Hello waitingone,
please try this (all terms are translated from my German programs to my best knowledge):
1. Did the creator of the pdf file enable the import options?
2. See import options: choose an other visibility option for your layer.
3. Let you show the import options and click into one with a black background and try these out (often a gray is selected).
4. See trimming: try the different modes there. Often works: "Media".
5. Is the pdf file (eg from Word) correctly created?
6. Is the PDF file protected? >>> no import possible.
7. If that does not help, store the pdf file in Acrobat, repair possible errors, run the PDF Optimizer before placing in InDesign.
Good luck!
Hans-Günter

Could not open Transport File for creation

I Changed the path and copied the repository from old path to new path. While executing se38 à RSCMST TCode, we get the errors in RED(HTTP interface using fuction group).
1.The error log check_subrc: subrc     1 instead          0
check_subrc: Component : data error text : No such file or directory
docGet: DOC_0                                    error
docGet: DOC_S
check_subrc: subrc     1 instead          0
check_subrc: Component : sdata1.txt error text : No such file or directory
docGet: DOC_S                                    error
docGet: DOC_M
check_subrc: subrc     1 instead          0
check_subrc: Component : mabc error text : No such file or directory
docGet: DOC_M                                    error
docGet: DOC_L
check_subrc: subrc     1 instead          0
check_subrc: Component : ldata error text : No such file or directory
docGet: DOC_L                                    error
docGet: DOC_N
check_subrc: subrc     1 instead          0
check_subrc: Component : Data6 error text : No such file or directory
docGet: DOC_N                                    error
HTTP error: 404 (Not Found) "G:CS_REPZHR_MASTEK046cDF6258C5DF68EAF183C4001F295A507C directory not found"
info: mCreate DOC_0                              error
2.Message 704: (SAPKPROTP Error: Could not open Transport File for creation.
Thanks & Regards
Jituda

Hi,
Could you plz let me know how did you fix this issue?
BR,
Shyam

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

Similar Messages

Maybe you are looking for