cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple languages issue with load of 0CUSTOMER_ATTR sort key

Former Member
0 Kudos
87

We're in the process of preparing to go live with more countries next year - with different languages. We're having issues in our testing of the load of 0CUSTOMER_ATTR, the sort key for example - because of characters in other languages.

For example in the sort key field: BEGOÑA. The Ñ character is considered invalid by BW.

Of course we can get around this by adding this character to RSKC, but in this case it seems we'd be adding entire language alphabets to RSKC!

Is there something else perhaps that is not installed on our BW system? Do we need to install a language set or something?

Thanks,

Chris

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Chris,

you do not need to install something on your BW. The sort field in 0CUSTOMER_ATTR is a quite common problem. In BW all InfoObjects are somehow key fields - and to avoid problems of selections if a letter is not known in other languages, SAP has decided to use only the most common international letters as allowed characters.

You should think about what you need the sort field for. May be you do not really need it as InfoObject for selections but just as Display information - than you can link the sort field to a text in BW (there all characters are allowed). Otherwise you could think about some transformation rules (change Ñ to N). I do not recommend to add all characters to RSKC.

Stephan

Former Member
0 Kudos

Hi Stephan,

Can you please elaborate on what you mean by "link the sort field to a text in BW". Do you mean switch on the attribute only flag in InfoObject maintenance?

We do NOT have it switched on as a navigational attribute so we eliminated that as a possibility.

Chris

Former Member
0 Kudos

Hi Chris,

I am thinking of an update rule (using flexible update) where the sort field is mapped with e.g. the short text of an Info Object.

You can use 0CUSTOMER for that, having one update rule for the standard text from 0CUSTOMER_TEXT mapped with the medium text and another update rule from 0CUSTOMER_ATTR where the sort field is mapped to the short text. You will need some ABAP to handle the language field if you need more than one language.

In the Query you can display short and medium text to see both information.

The advantage of this scenario is that the sort field is not checked against the allowed characters.

Hope that helps

Stephan

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Chris,

you should try in RSKC the setting ALL_CAPITAL only, for some times it has helped us.

/manfred