Skip to Content
author's profile photo
Former Member

problems in unicode upgrade

I am conducting an analysis on how upload of foreign characters are received in SAP BW without a unicode upgrade of the system.

We are interested in knowing, whether it can cause any problems in a unicode upgrade that characters not contained in the code page of the system are loaded into the system beforehand. I.e., we are concerned about whether the weird characters that might be the result of loading a file with characters not contained in the code page will be a problem in a unicode upgrade?

Example:

1. We are running a single unicode system with Western Europe codepage

2. We are loading in some text field into SAP BI containing local characters from another codepage.

3. In our current system (single codepage) these signs only get displayed as '#' (but that is ok for us right now)

4. Will 1 - 3 mean any technical upgrade problem when doing the unicode upgrade ?

Thanks & Regards:

Giridhar. N

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Posted on Sep 25, 2007 at 10:58 AM

    check

    647495 - RFC for Unicode ./. non-Unicode Connections

    If you´re concerned about the "#", it doesn´t give you problems during conversion but those characters are destroyed.

    --

    Markus

    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 28, 2007 at 12:12 PM

    Hi Gridhar,

    Non-supported characters will be converted either to a corresponding supported character encoded with the same Hex code or will be converted to # (this is the same as the display behaviour of SAPGUI in MDMP).

    Therefore the technical conversion will have no problem, but of course the data is not usable anymore. However you might be able to repair this data using the SUMG functionality.

    Best regards,

    Nils Buerckel

    Solution Management

    Globalization Services

    SAP AG

    Add comment
    10|10000 characters needed characters exceeded