Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

System language change

Former Member
0 Kudos
3,624

Hello,

I just want to ask if there is way to change standard system language. Now we have DE and supplementation is also DE. We want to change system language to EN and supplementation to DE.

Thx.

1 ACCEPTED SOLUTION

Former Member
0 Kudos
289

HI Jan,

Use

Use the language supplementation function to fill in the gaps in a language that has not been translated completely.

Supplementation actions are client-specific. The languages are supplemented in the client in which you are logged on. If you use multiple clients, you must supplement the languages explicitly in each production client.

You can also access the texts stored in cross-client database tables from all clients simultaneously. The default setting specifies that cross-client tables are supplemented when you are logged on to client 000.

Procedure

1. Go to the language that you want to supplement and choose or Language ® Supplement Language.

2. On the next screen, enter a description of your supplementation. This helps you to recognize the supplementation you have started in the transaction SMLT overview.

3. In the center of the dialog box, enter the conditions for selecting the tables you want to supplement. These fields are set with SAP defaults that depend on the logon client, however, you can change them.

Client-specific Customizing tables are subject to special handling during language imports. This has resulted in the following supplementation strategies being created:

· Combined with RSREFILL (standard setting when logging on to clients other than 000)

· Combined with Client Maintenance

· Supplement Only

For more information on these strategies, choose Information on Table Selection in the system, or see the section Customizing Tables.

4. Enter a start time and (optional) target server, and then you are ready to supplement the language by choosing Execute. This action schedules a background job that performs the supplementation.

5. The overview screen of transaction SMLT creates a supplementation entry for the appropriate language. Choose the corresponding icon to administer and monitor the supplementation.

The overview contains the following icons:

Display supplementation log (in table)

Display job information

Display job log

Restart action, if it has terminated for technical reasons

6. The icon at the start of the line indicates the status of the import.

The icons have the following meanings:

The selected table was supplemented without errors.

There were warnings during the supplementation. You can analyze these warnings by displaying the supplementation log. To display the supplementation log, choose or double-click the name of the supplementation action.

There were errors during supplementation. Analyze them as described above.

The action is scheduled. Choose to display job information, such as the start time and target server.

The action is currently running.

The action has terminated for technical reasons. To find out the cause of the error, see the job log (choose ).

7. The supplementation log gives you detailed information about the tables that have been supplemented.

Each line of the log contains the name, class, description, and other information about a supplemented table. The status, client, and supplementation mode appear first, followed by statistics about how many rows in the table have been processed, inserted, and modified. You can also see a return code.

All tables that have been processed fully are given a status based on the return code. This status is indicated by a green, yellow, or red light.

For information about the meaning of the return codes, display the F1 help for the return code (RC) column.

see this link also

http://help.sap.com/saphelp_nw04s/helpdata/en/37/3e3d38b611b065e10000009b38f889/frameset.htm

thanks

abdul

reward me points if usefull

6 REPLIES 6

Former Member
0 Kudos
290

HI Jan,

Use

Use the language supplementation function to fill in the gaps in a language that has not been translated completely.

Supplementation actions are client-specific. The languages are supplemented in the client in which you are logged on. If you use multiple clients, you must supplement the languages explicitly in each production client.

You can also access the texts stored in cross-client database tables from all clients simultaneously. The default setting specifies that cross-client tables are supplemented when you are logged on to client 000.

Procedure

1. Go to the language that you want to supplement and choose or Language ® Supplement Language.

2. On the next screen, enter a description of your supplementation. This helps you to recognize the supplementation you have started in the transaction SMLT overview.

3. In the center of the dialog box, enter the conditions for selecting the tables you want to supplement. These fields are set with SAP defaults that depend on the logon client, however, you can change them.

Client-specific Customizing tables are subject to special handling during language imports. This has resulted in the following supplementation strategies being created:

· Combined with RSREFILL (standard setting when logging on to clients other than 000)

· Combined with Client Maintenance

· Supplement Only

For more information on these strategies, choose Information on Table Selection in the system, or see the section Customizing Tables.

4. Enter a start time and (optional) target server, and then you are ready to supplement the language by choosing Execute. This action schedules a background job that performs the supplementation.

5. The overview screen of transaction SMLT creates a supplementation entry for the appropriate language. Choose the corresponding icon to administer and monitor the supplementation.

The overview contains the following icons:

Display supplementation log (in table)

Display job information

Display job log

Restart action, if it has terminated for technical reasons

6. The icon at the start of the line indicates the status of the import.

The icons have the following meanings:

The selected table was supplemented without errors.

There were warnings during the supplementation. You can analyze these warnings by displaying the supplementation log. To display the supplementation log, choose or double-click the name of the supplementation action.

There were errors during supplementation. Analyze them as described above.

The action is scheduled. Choose to display job information, such as the start time and target server.

The action is currently running.

The action has terminated for technical reasons. To find out the cause of the error, see the job log (choose ).

7. The supplementation log gives you detailed information about the tables that have been supplemented.

Each line of the log contains the name, class, description, and other information about a supplemented table. The status, client, and supplementation mode appear first, followed by statistics about how many rows in the table have been processed, inserted, and modified. You can also see a return code.

All tables that have been processed fully are given a status based on the return code. This status is indicated by a green, yellow, or red light.

For information about the meaning of the return codes, display the F1 help for the return code (RC) column.

see this link also

http://help.sap.com/saphelp_nw04s/helpdata/en/37/3e3d38b611b065e10000009b38f889/frameset.htm

thanks

abdul

reward me points if usefull

0 Kudos
289

Seem the qustion is not clear enough.

Is it possible to change master language. or at least change supplementation (not to install new language) ?

0 Kudos
289

You can change the profile parameter


zcsa/system_language = E

in your instance profile and restart the instance.

Markus

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos
289

Hi Jan,

1) zcsa/system_language -

The system language has two basic functions:

- It determines the language on the logon screen.

- It is the basic language for all user dialogs (screens).

2) zcsa/second_language -

If you want to display texts in a language in which the texts are not

available, SAP Web AS attempts to display certain objects in another

language, the secondary language. This secondary language option is

supported for the following objects from SAP Web AS Release 6.20:

- ABAP text elements

- Screen (including texts from the ABAP Dictionary)

- GUI status

- OTR (Online Text Repository)

The secondary language must be a completely translated language. The

secondary language is independent of the logon language.

3) Supplementation Language

The secondary language option cannot be implemented for all texts for

performance reasons. To use a language, supplement it with transaction

SMLT.

A language supplementation replaces any missing texts in the logon

language with texts in the supplementation language.

Unlike the secondary language, you can set a different supplementation

language for each language.

Secondary Language Access and Language Supplementation:

There are two different concepts for missing translations: Secondary

language access and supplementation language. It is best to set the same

language as the secondary language and supplementation language, since

both concepts then have the same effect.

If the supplementation language is different from the secondary

language, the supplementation language 'wins' for reasons of

consistency. The secondary language is not accessed.

Now to your question:

a) Changing system language (profile parameter zcsa/system_language) does not influence the system reaction regarding missing translation. I do not see a problem with this.

b) However I would recommend to keep Supplementation and secondary language in sync. Otherwise Screens might come up with texts in two different languages.

c) A supplementation language cannot be changed once supplementation was executed. The only way could be to do this during an upgrade.

Best regards,

Nils Buerckel

Solution Management

Globalization Services

SAP AG

0 Kudos
289

Hello NIls,

This indeed was a very nice piece of information. However, this doesnt seem to be working when it comes to BW queries. We want the system to look up the English text (supplemental and secondary language) which exists when there is no foriegn text when the user is logged in a non-english language

I will really appreciate any more inputs that you may have on this

Thanks!

Missy

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos
289

Hi Missy,

I am not a BW specialist, but please check whether the relevant texts are stored in table RSZELTTXT.

If this is the case, then you might need to "undo" SAP note 1034278 and redo the supplementation of the according language keys with EN.

Best regards,

Nils Buerckel

SAP AG