cancel
Showing results for 
Search instead for 
Did you mean: 

How to allow loading non-english characters

Loed
Active Contributor
0 Kudos

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?

Thanks.

Loed

Accepted Solutions (0)

Answers (4)

Answers (4)

FCI
Active Contributor
0 Kudos

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...

Loed
Active Contributor
0 Kudos

Yes, we only have ALL_CAPITAL_PLUS_HEX in our RSKC. I will check your note.

Thanks.

Loed

FCI
Active Contributor
0 Kudos

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 ?

Loed
Active Contributor
0 Kudos

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.

Loed

FCI
Active Contributor
0 Kudos

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:

Loed
Active Contributor
0 Kudos

Hi,

How about if my datasource is a standard one? For example, for 0MATERIAL_ATTR.

Also, we are using ODP.

Thanks.

Loed

FCI
Active Contributor
0 Kudos

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).

Regards,

Frederic

Loed
Active Contributor
0 Kudos

Hi Frédéric,

I have questions:

1. What do you mean by the "right code page"? Where can I see that?

2. How will I know if our BW system is unicode?

3. What if our system is not unicode? How can I load non-english characters?

Thank you.

Loed

EDIT 1:

I just checked our system, it is unicode. Is this correct?

So what do you mean by the "right code page"? Where can I see that?

EDIT2:

Is this the "right code page" that you are saying? How will I know the correct setting?

EDIT 3:

So you mean I need to add this code to 0MATERIAL and other objects which I think will give me the six (6) invalid characters? What objects do you usually place this code?

https://wiki.scn.sap.com/wiki/display/Snippets/Code+to+eliminate+hexadecimal+or+invisible+characters...