Multilingual Capabilities 

Use

cProjects distinguishes between application languages and text languages. Not all application languages are text languages.

Prerequisites

You defined text languages in Customizing for Collaboration Projectsunder Specify Text Languages. You can only enter texts in cProjects in these languages. One of these text languages is the default language.

Application Language

You can log on to cProjects in various languages. The system first attempts to determine the application language using the language parameter in the cProjects URL (for example, sap-language=DE). If no parameter has been specified in the URL, the system uses the language settings in your browser to determine the application language. If no language has been entered there either, the user settings in the back-end system apply.

Text Language

You can enter the texts for a project in any of the languages you specified in Customizing. The following texts in cProjects are language-dependent:

●      Project element name

●      Project element description

●      Name of responsible project role

If no texts exist in the text language currently set, the corresponding text fields are blank.

When you create projects, project templates, or checklist templates, the system provides an original language. You cannot change the original language once the objects have been created. The original language applies to the whole project or template – all project elements have the same original language.

Original language when creating objects without a template

If you create a project, project template, simulation version, or checklist template without a template and the logon language is a permitted text language, the system sets the logon language as the original language. If the logon language is not a permitted text language, the system sets the default language. You can also select an original language of your choice.

Original language when creating objects with a template

If you create a project, project template, or checklist template with a template, you can use the appropriate pushbutton to specify that the original language of the template is also the original language for the new project or template. Otherwise the same conditions apply as for creating objects without a template.

Opening objects

In the user settings you make the default setting for whether you want to open objects in the logon language or in the original language:

●      Logon language

If the logon language is not a permitted text language, the object is opened in the default language. If no texts exist in the default language, the text fields are blank.

●      Original language

If you open several objects with different original languages, they are opened in the logon language provided that this is a permitted text language. If this language is not permitted, the default language is used.

Resolving checklist references in operational projects

When you resolve checklist references, the original language of the project also becomes the original language for the checklist and the checklist elements. The system transfers the texts in all existing languages.

If the checklist template has a different original language to the project, the checklist template can contain project elements for which no text has been entered in the original language of the project. If this is the case, the system copies the texts in the original language of the checklist template when it resolves the reference. If, for example, the original language of the project is English and the checklist template only contains German texts, the German texts are copied and are displayed for both the text language German and text language English.

Required-entry-field check for language-dependent fields

Here, the system only checks whether you made the entries in the original language with which the project was opened. If you change the language afterwards, the system does not carry out any more checks.

 

See also:

Using Language-Dependent Functions