Translate a Template 

Purpose

The project structure and the documents in a project are always displayed in the project language, which you specify when you create the project, and can only be changed in this language.

If you create a template in a project language in the company headquarters, and want to make it available in the subsidiary in another project language, translate it first in the company headquarters, and then deliver it to the subsidiary.

When you translate a template, the translation is only visible in the target language in the target project for which you have specified the target language as the project language, not in the source project. If a document is not available in the desired language, it is displayed in the original language.

The company headquarters creates the source project in the project language English, and translates the templates in it into Japanese.

The Japanese subsidiary creates the target project in the project language Japanese. After the subsidiary has copied the templates into the target project, the templates and their documents are available in the target project in Japanese.

Translation environment

Project structure, document name

The project structure, the document name and names of URLs, files, etc. which you have entered in the tabs, are translated in the translation transaction SE63.

You can also translate the project structure without document names and names of URLs, in the Business Blueprint (transaction SOLAR01) Goto → Translation.

Knowlege Warehouse documents

Knowlege Warehouse documents are translated with the Knowlege Warehouse translation function (transaction SI80). The system puts all documents which were created in the General Documentation and Configuration tabs in the source project, in the Knowledge Warehouse in the project context, in the folder SOLAR00. You should create a unique context for each project.

Project structure assignments

You do not need to translate the names of transactions, IMG objects and programs which you have assigned to the project structure. These names and their translations are automatically copied from the component systems when you deliver a template.

Prerequisites

●      You have created a template.

●      You have Set-Up the Translation Environment in the translation system.

You translate in the system from which you export the collective request with the entire template. This can be a development system, or a consolidation or translation system. All language entries are only transported in this collective request for the template.

Process Flow

...

       1.      Translate the project structure and document names:

                            a.      To translate the project structure only, select a structure element in the Business Blueprint (transaction SOLAR01) and choose Goto → Translation.

                            b.      To translate the project structure and document, URL and file names:

                                                  i.       Assign the package or packages in the project to the translator in your translation system.

                                                ii.       Generate Worklists for the packages in the project.

                                               iii.       The translator translates the packages which are assigned to him.

       2.      The translator translates the Knowlege Warehouse documents in the project context in the folder SOLAR00.

       3.      You release the template in the project administration and deliver it.

       4.      Whenever you change the project structure and/or the documentation in a translated template, in the company headquarters, translate the changes in the company headquarters before delivering to the subsidiaries.

If you have translated the template, you must translate every change, otherwise the changes are not visible in the project language of the subsidiaries.