Skip to Content

How to allow loading non-english characters

Hi guys,

How do you load data coming from non-english characters? Yes we can implement a routine to allow only the characters we wanted like this ',<>?/\:;"''ABCDEFGHI JKLMNOPQRSTUVWXYZ!%^&*()__+=1234567890'. But I need to load those special characters like '^ÖܲÖ\'. How can I load them aside from adding them in RSKC? Because right now we are already using ALL_CAPITAL_PLUS_HEX in RSKC but the characters I mentioned are still giving me error when loading them.

Any idea?



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Nov 28, 2018 at 08:08 AM

    Hi Loed,

    If you BW system is unicode and if you select the right code page (at the infoPackage level for file or at the RFC level for SAP source system), you should be able to load non-english characters into your system with this customizing (ALL_CAPITAL_PLUS_HEX).

    Only 6 characters are definitively forbidden and should be explicitly removed (see here).



    Add comment
    10|10000 characters needed characters exceeded

  • Nov 28, 2018 at 02:19 PM

    There is a field "Unicode syst" (Yes or no) in the System/status screen.

    The code page defines the character set of data (unicode is a code page). When loading a file you define the code page that you want to use:

    screen.jpg (50.4 kB)
    Add comment
    10|10000 characters needed characters exceeded

  • Nov 29, 2018 at 08:08 AM

    So, your BW system is unicode. Your source system is. Your RFC destination is well defined (unicode). Your customizing is fine

    The sceen shot I gave you with the code page is only for file source. Here this is not relevant.

    Did you identify the character that cause the error ?

    Add comment
    10|10000 characters needed characters exceeded

    • Yes I did identify. They are German characters I guess. Sample characters which is causing an error while loading.


      Any idea how to allow these characters? Right now they were added in RSKC so I can load them fine. But I have no idea what other characters will be loaded in the future. I don't want to add them individually.

      Any idea to solve this?

      Thank you.


  • Nov 29, 2018 at 05:05 PM

    I have no more clue. ALL_CAPITAL or ALL_CAPITAL_PLUS_HEX should definitively work for these characters (there was only the ALL_CAPITAL_PLUS_HEX string in the RSKC, right ? you should have only this string with no other characters nor mispelling ;-) ).

    You can have a look to the note 1151294. I didn't see any relevant point for you but maybe you can...

    Add comment
    10|10000 characters needed characters exceeded