Unicode Open Dataset Question

[Former Member]

We are beginning to prepare for the Unicode enabling of our custom ABAP programs and I have a question about the new OPEN DATASET statement. We have programs that write sequential files for use by the following:

1) ABAP programs that execute on our own SAP system

2) Non-SAP programs that execute in our data center

3) Programs (which may or may not be SAP) that execute in the data centers of other completely independent companies.

Conversely, we have programs that read files supplied by those systems.

After reading through a lot of information, I am reaching the conclusion that for our files that contain only character data, it would be safe for us to modify our OPEN DATASET statements simply to use u201COPEN DATASET IN TEXT MODE ENCODING DEFAULT IGNORING CONVERSION ERRORSu201D without attempting to be more explicit with some of the other options that are available.

Can any of you confirm that this is (or is not) a valid assumption?

[Former Member]

yes you can go ahead with that..for the text files and chardata files

OPEN DATASET IN TEXT MODE ENCODING DEFAULT IGNORING CONVERSION ERRORSu201D

[Former Member]

If the SAP system is upgraded to unicode compliant, then the default codepage would be Unicode compliant, so the OPEN DATASET should work

[Former Member]

Hi ,

OPEN DATASET IN TEXT MODE can be just replaced with

OPEN DATASET IN TEXT MODE ENCODING DEFAULT.

DESCRIBE LENGTH should be followed by the addition

IN CHARACTER MODE/BYTE MODE.

[Former Member]

This is just a quick note to let anyone who may be reading this thread know that I have confirmed that my assumption is invalid. The OPEN DATASET statement must be coded differently depending on whether the source of/destination for the file is Unicode (or not).