Skip to Content
author's profile photo
Ole Müßigbrodt

Uni-Code with OPEN DATASET 4.6C ->4.70

Oct 07, 2005 at 08:59 AM | 29 Views

Hello,

we have a 4.6C development system and several reports which use OPEN DATASET IN TEXT MODE to read files from server.

These reports are transported to a 4.70 Rel. and there we have a uni-code problem. The transaction "UCCHECK" marks this reports with an error-flag and the message: "In TEXT MODE" the "ENCODING" addition must be specified".

Problem: In 4.6C the addition "ENCODING" doesn't exist!!!

How can I solve the problem? How can I use the OPEN DATASET in 4.6C so that it is uni-code compatible?

Regards,

Ole.

ABAP Development
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    author's profile photo
    Former Member
    Oct 07, 2005 at 11:43 AM

    If you have different version 46C -> 470 in the same landscape , the only option you have is to ignore those UCCHECK errors till your dev system is upgraded .

    This way you can keep the programs in sync and executable on both systems with no syntax errors in SE38. Programs without "encoding" will run fine on 46C as well as 470 systems . When you move a transport from 46C to 470 , the program attributes ( Unicode Checks Active ) is not activated by the transport . It is only activated when you create a new program on 470 system directly .

    Cheers.

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Oct 07, 2005 at 09:01 AM

    Just uncheck the udicode checks active in the proram attributes in SE38.

    Cheers

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member
      Oct 07, 2005 at 10:02 AM

      Hi,

      question is: what can I do on a nonunicode system? than I cannt use the statement:

      open dataset DSN in legacy text mode for output/output.

      Regards Thomas

  • author's profile photo
    Former Member
    Oct 07, 2005 at 11:00 AM

    This is an indicator of a more basic problem. If you have systems on two different releases (eg dev on 46 and prod on 47), situations may occur where code from one system is not correct in another. And there is no resolution for this.

    In this specific case, you will need to edit the program on target (unicode) system,

    or,

    change the code as per unicode standards in the 46C system, ignore the syntax errors to activate it, transport it to prod, where it should work. You can then change the code back to a correct syntax on DEV system.

    Add comment
    10|10000 characters needed characters exceeded