mySAP Global Implementation

[Former Member]

Hi, All

We are going to implement mySAP ECC glabally which include USA, EU and Asia countries. And we are evaluating the general procedures so the whole solution can support different geography local users. I have several questions below:

1. For IMG configuration, should all the configuration value need to be configured seperately for each of the lanugage, like Chinese, English, Thai?

2. Someone talked about the translation capabilty of SE63, can SE63 be used to ABAP development object text translation as well as IMG configuration ?

3. What is the best practice to build the translation pool in SE63 so they can be re-used as much as possbile in future project? I mean how we normally organize those translation activties for SAP implementation.

4. Is there any sap system configuration that allow the system to act like this: when reading configuration value in on-line transaction screen, it will first try to find the current log-on language specific configuration values, if not found, a default language configuration value can also be displayed? (Let's say English will always be the default lanuage.) Is this possible?

Thanks for help. Sorry if too many questions in one post...

[Former Member]

Thanks for responsing. So for the last question, to set up the language x and y, is this done in I18N or somewhere else?

Thank again.

[Former Member]

Well it's some parts in order to work with the languages.

First you have report RSCPINST (started with tcode SA38),

where you define which languages you want to use.

You can simulate the change in order to see what instance-parameters

you need to add or change.

After successful RSCPINST activation, call transaction SMLT.

Here you can create, import and supplement languages.

Please note that if you import a language and you are on a higher patchlevel

in the system compared to when you installed the system,

then you have to import languages in the supportpackages as well.

All this is done via SMLT.

[Former Member]

Hi,

This was some questions in one post, but I try to answer them

1. For IMG configuration, 
should all the configuration value need to be configured seperately
for each of the lanugage, like Chinese, English, Thai?

I would recommend you to choose one corporate language to base your

configuration on, then whenever needed, translate into other languages.

I depends on the configuration.

Some of them are language independent and some of them are not.

Sometimes you simply have to logon the the "other" language

and add the texts there.

2. Someone talked about the translation capabilty of SE63, 
can SE63 be used to ABAP development object text translation 
as well as IMG configuration ?

One again, it depends.

However, all development objects can be translated in SE63.

3. What is the best practice to build the translation pool in SE63 
so they can be re-used as much as possbile in future project? 
I mean how we normally organize those translation activties for SAP 
implementation.

It's more common sense then best practices.

If the translation is done in a similar way,

the translation pool can be re-used and translation is performed much faster.

If a new word need to be defined, discuss it in the implementation group

instead of having several people defining their own way of describing things.

That's the best tip I can give you.

4. Is there any sap system configuration that allow the system to act like this: 
when reading configuration value in on-line transaction screen, 
it will first try to find the current log-on language specific configuration values,
if not found, a default language configuration value can also be displayed?
(Let's say English will always be the default lanuage.) Is this possible?

When you setup a new language X in the system

you also define what is going to be the supplemental language Y.

When the language X has been imported you run an supplemental job

which copies all missing texts from Y into X.

This job can be repeated later on in order to supplement new missing texts.