SAP Web as 6.20 Translation System Setup

Setting Up and Coordinating Translation (BC-DOC-TTL)

HE

LP

.BC

DO

CT

TC

Re lease 640

SAP Online Help 28.08.2003

Setting Up and Coordinating Translation (BC-DOC-TTL) 640 2

Copyright Copyright 2003 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation. Example text Emphasized words or phrases in body text, titles of graphics and tables.EXAMPLE TEXT Names of elements in the system. These include report names,

program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Setting Up and Coordinating Translation (BC-DOC-TTL) ............................................................... 6 Preparing a System for Translation ............................................................................................. 7

System Resource Setup........................................................................................................... 9

Administrative Measures ........................................................................................................ 10

Proposal Pool Transport ............................................................................................................ 11 Exporting the Proposal Pool................................................................................................... 14

Importing the Proposal Pool ................................................................................................... 18

Setting Up the Translation Environment .................................................................................... 22 Setting Up the Target Language ............................................................................................ 23

Secondary Language Status.................................................................................................. 24

Maintaining the Secondary Language Status..................................................................... 25

Adding the Translation Client ................................................................................................. 26

Translation Graphs................................................................................................................. 27

Maintaining the Translation Graphs.................................................................................... 28

Exception Packages ........................................................................................................... 29

Defining Exception Packages ......................................................................................... 30

Object Groups and Object Types for Translation................................................................... 31

Defining Object Groups for Translation .............................................................................. 32

Checking Object Type Attributes ........................................................................................ 34

Refreshing the Translation Hierarchy..................................................................................... 35

Translator Profiles .................................................................................................................. 36

Creating a Translator Profile............................................................................................... 39

Maintaining Translators .......................................................................................................... 41

Displaying the Details of an Evaluation Run .......................................................................... 43

Working with the Information Center...................................................................................... 44

Package Assignment ................................................................................................................. 47 Selecting Packages................................................................................................................ 49

Importing and Exporting Files for Package Assignment ........................................................ 51

Working with Package Lists ................................................................................................... 53

Assigning Packages ............................................................................................................... 57

Locking Packages .................................................................................................................. 59

Checking a Translator's Packages......................................................................................... 61

Deleting a Translator's Package Assignment ........................................................................ 62

Checking Package Attributes ................................................................................................. 63

Checking Packages Assigned to Multiple Translators ........................................................... 64

Filtering Packages.................................................................................................................. 66



Copying Package Assignments from Another System .......................................................... 70

Displaying an Overview of a Target Language ...................................................................... 72

Working with the Translation Planner ........................................................................................ 74 Translation Planner: Overview Screen................................................................................... 75

Scheduling an Initial Run........................................................................................................ 77

Defining the Transports for Transport Evaluations................................................................. 78

Defining Priorities and Default Servers .................................................................................. 79

Object Lists............................................................................................................................. 80

Creating Object Lists .......................................................................................................... 82

Evaluations............................................................................................................................. 84

Creating an Evaluation Run................................................................................................ 87

Translation Planner: Checks .................................................................................................. 89

Automatic Distribution ................................................................................................................ 90 Setting Object Types for Automatic Distribution..................................................................... 91

Worklist Management ................................................................................................................ 93 Creating and Deleting Worklists ............................................................................................. 95

Statistics Functions for Coordinators ......................................................................................... 97 Working with the Complex Statistics ...................................................................................... 99

Organizing the Statistics....................................................................................................... 102

Displaying the Statistics History ........................................................................................... 103

Displaying the Statistics for All Languages .......................................................................... 105

Transport Recording ................................................................................................................ 106 Creating Requests in Transport Recording.......................................................................... 108

Filling Requests with Translations in Transport Recording.................................................. 110

Displaying Requests in Transport Recording....................................................................... 112



Setting Up and Coordinating Translation (BC-DOC-TTL) This documentation enables you to set up a system for translation and also to manage a translation project. For information on how to translate in an SAP system, see Translation Tools for Translators (BC-DOC-TTL) [Ext.].

The main components of this documentation are as follows:

Preparing a System for Translation [Page 7]

Setting Up the Translation Environment [Page 22]

Package Assignment [Page 47]

Working with the Translation Planner [Page 74]

Automatic Distribution [Page 90]

Worklist Management [Page 93]

Statistics Functions for Coordinators [Page 97]

Transport Recording [Page 106]



Preparing a System for Translation Purpose In order to translate in the R/3 System, you will need to maintain the translation environment.

You set up the translation environment in transactions SLWA and SLWB.

Implementation Considerations Before you start maintaining the translation environment, you should:

provide or extend system resources - please see System Resource Setup [Page 9] perform administrative measures and preparation - please see Administrative Measures

[Page 10]

The translation environment must be defined before the start of productive translation.

Integration After you have completed the above preparation, you start maintaining the translation environment in transaction SLWA.

Transaction SLWA is used to maintain the control tables for translation and to set up the translation environment.

Authorization for some of the functions used in SLWA depend on:

the profile S_ADMI_FCD with value TRNR, which is only assigned to administrators - this is assigned in the user master record

the authorizations assigned to users in the translator profile in transaction SLWA itself. After you have finished maintaining the translation environment in transaction SLWA, you will need to run an initial scan of the R/3 System, create language-independent object lists of objects whose texts need to be translated in the R/3 System, and evaluate these objects in order to create language-dependent worklists of objects for translation. For this purpose, you use the Translation Planner in transaction SLWB.

Features In transaction SLWA, you set up the translation environment. See Setting Up the Translation Environment [Page 22].

In transaction SLWB, you prepare objects for translation by performing the steps listed below:

schedule an initial run - please see Scheduling an Initial Run [Page 77] define the source systems for transport scans define the language priorities and default hosts create language-independent object lists - please see Object Lists [Page 80] run the evaluation to create language-dependent worklists and statistics - please see

Evaluation Run [Page 84]



Constraints Please remember that the respective codepage must be set for the languages involved in the translation process. These languages must be entered in the system profile of this server.



System Resource Setup Purpose In order to execute evaluation runs, various minimum requirements must be met. These are listed under Prerequisites.

Prerequisites In the SAP translation system, all the source language text objects must be imported and made accessible for translation. This results in system requirements greater than or equal to those in the customer system.

In a customer translation system, normally only the new developments and customer developments or modifications should be translated.

The specifications of database space, main memory, etc. are empirical values that can vary depending on the system size and load.

Process Flow These requirements must be met before the start of productive translation.



Administrative Measures Purpose In order to set up the translation environment, certain administrative measures must be carried out. These are listed under Prerequisites.

Prerequisites The respective codepage must be set for the target languages involved in the translation

process.

The parameter zsca/installed languages must be maintained in your respective R/3 System profile in transaction RZ10.

You must have made the codepage settings as described in notes 15023 and 42305 in the SAP Online Service System. For a detailed explanation of the settings, see note 73606.

Process Flow These requirements must be met before the start of productive translation.



Proposal Pool Transport Use Whenever a new translation system is set up or a development (or part of a development) moves from one translation system to another, you may need to transport the proposal pool [Ext.] from the source system (such as the legacy system, a general reference system, or the system previously used to translate the development) to the new translation system (target system). This ensures that the target system contains proposals for translations that already exist. The source text lines in question therefore have the translation status [Ext.] Translated and do not need to be edited again. You can also use translations stored in the source systems proposal pool for source text lines that need to be translated in the new translation system, or for which you want to perform automatic distribution [Page 90].

Prerequisites A suitable proposal pool exists. For example, it originates from one of the following systems:

Legacy system of the system to be set up General reference system System in which the imported development, or part of a development, was originally

translated

Features You can transport a translation systems entire proposal pool to another translation system, or you can transport just part of a proposal pool (delta). For example, you could restrict the transport to proposals changed after a certain date, or proposals that belong to a specific domain. When deciding whether to export the entire proposal pool or just part of the proposal pool, you must consider the following:

Type of Target System { If you set up a translation system whose contents are based on an existing

translation system (for example, a translation system in which a later release of the same product is translated), it is usually the case that many of the translation-relevant domains match. (Domains are the approximate equivalent of components in earlier releases of the ABAP environment.) In this situation, it is a good idea to import the source systems entire proposal pool. The prerequisite is that the quality of proposals in the source systems proposal pool is satisfactory. For more information, see the next point.

{ If just some of the target systems contents match the contents of an existing translation system (for example, part of a development moves from one system to another), it is usually the case that most components do not match. In this situation, you should only transport that part of the proposal pool for which the target system contains suitable source text entries.



The standard translation system at your company has been used to translate source texts from the domains Basis (BC), Financial Accounting (FI), Payroll (PY), and Logistics (LO). A new translation system for the area of banking is needed to translate source texts from the domain Bank Components (IS-B), and source texts from the domains BC and FI. The domains PY and LO are irrelevant for the banking translation system. In this situation, you should only transport the proposal pool for the domains BC and FI from the standard translation system to the banking translation system.

Quality of Existing Proposal Pool { If you transport a proposal pool, all of the source text lines in the target system for

which the transported proposal pool contains valid translations are assigned the translation status [Ext.] Translated. This means they are no longer automatically included in translation worklists. Therefore, you should only transport proposal pools if you are sure that their translations are relevant and correct for the new translation system. However, if you know that the legacy system contains many translations whose terminology is incorrect (because the legacy systems proposal pool already contains a mixture of other systems proposal pools, for example, or because the translations in the legacy system are incorrect), you are advised to refrain from importing the proposal pool into the new translation system or to use a proposal pool from a reference system whose terminology is correct.

{ If you do not import a proposal pool, the system cannot assign valid proposals to the translations in the new translation system, so that the translations are assigned the translation status [Ext.] Modified. You can then check the quality of the translations manually. However, if you import a proposal pool from a reference system whose terminology is correct, translations that were created in your new translation systems legacy or original system will probably be missing. The advantage though is that you can be sure the imported proposals are correct.

If some but not all of the proposal pool is incorrect or of dubious quality, you can use the selection criteria for exports and/or imports to ensure that low-quality parts of the proposal pool are excluded from the transport, while the correct parts of the proposal pool are transported. For example, if translations belonging to the domain Finances are the only ones that are incorrect in a legacy system, you can transport the proposal pool for all other domains in the system.

You can also import proposal pools from several source systems into a target system. This could be necessary if, for example, you need to set up a new banking system that also contains a number of Basis functions. If the Basis functions and banking functions have been translated in different translation systems, you need to set up the new banking system by importing the proposal pools from the Basis and banking systems.

In this situation, it is possible for the same source text to have different translations in the two translation systems. If both source texts have been defined as a system standard [Ext.] or application standard [Ext.] for the same domain, and if the system standards or application standards have the same quality status, then a conflict occurs. The system then inserts both terms at the same level and with the same quality status into the proposal pool.



Example You are setting up a new banking system for which you need proposal pools from the Basis and legacy banking systems. In the Basis system, the term Client has been translated into German as Mandant and defined as a system standard with quality status S. In the banking system, the term has been translated as Kunde and also defined as a system standard with quality status S. If you import both proposal pools into the new banking system, the resulting proposal pool will contain two German translations of the English source text Client, namely Mandant and Kunde. Both are system standards with quality status S.

If the proposal pool contains two proposals at the same level with the same quality status, the best proposal and automatic distribution are turned into a lottery for the source text in question because either of the coexistent proposals could be selected. You can usually avoid this situation by always defining proposals as application standards, and then turning them into system standards only after you are absolutely sure that the translation is unique.

Activities The proposal pool transport consists of the following steps: ...

1. Export [Page 14] the proposal pool(s) from the source system(s)

2. Import [Page 18] the proposal pool(s) into the target system



Exporting the Proposal Pool Use You can only transport proposal pools [Page 11] if the proposal pool(s) has/have already been exported from the source system(s). You can export the entire proposal pool [Ext.] or just part of the proposal pool.

When exporting or importing a proposal pool, you can set parameters to restrict the exported and/or imported data. For example, if a proposal pool already exists in the target system, or if you need to import proposal pools from several systems into the target system, you can avoid conflicts when the data is imported by setting appropriate export and/or import parameters. Such conflicts can arise if the same source text has different translations in different proposal pools, and these various translations all exist at the same level (that is, as a system standard [Ext.] or application standard [Ext.] for the same domain) and with the same quality status [Ext.]. You can export the following parts of a proposal pool individually or in combination with each other:

Source language Target language Domain type Domain

The domain is the equivalent of the highest component level of the application component hierarchy in earlier releases of the R/3 environment.

Quality status Date of last change Translator who last changed a translation Export of proposals only Export of abbreviations only Export of exceptions only For examples of proposal pool exports, see the examples below.

You do not have to import the exported proposal pool file in its entirety. The import parameters enable you to import just parts of the export file. You should therefore ask yourself whether you want to import the export file into just one other system, or whether you want to import the export file into more than one system. The latter scenario can arise if a translation system is used as the basis of many other translation systems, or if its terminology is considered the standard on which terminology in other translation systems is based.

If you only want to import the export file into one other translation system, you are advised to set the export parameters so that they meet as many of the target systems requirements as possible. This reduces the size of the export file, and accelerates the transport process. However, if you intend to import the export file into numerous translation systems, you are advised to perform a complete export and then use the import parameters to ensure that only relevant data is imported into each target translation system.



Prerequisites A source system exists with a proposal pool containing proposals that are suitable for the target system.

You are authorized to start reports in transaction SE38 and write export files to a directory. This directory could be the source systems transport directory. However, it could also be any other directory on a server or computer that the source system can access.

Procedure ...

1. In the source system, call up transaction SE38.

2. Start report RS_TRANSLATION_EXPORT_PP.

3. Enter the source language in the S_LANG field, and the target language in the T_LANG field. Each of these entries consists of four characters.

You can also use the input help function to display a list of available source and target languages.

4. Specify the name of the export directory under DIRECTRY, and the name of the export file under FILENAME.

You are advised to enter a meaningful name for the export file. You could use the following naming convention:

TRM.

For example, TRMDE.BA1 indicates that this export file was created to export the proposal pool (translation memory = TRM) with source language German and target language English from translation system Banken1. The export file does not have a preset file name extension.

5. Enter the name of the domain under DOMATYP.

The domain type for ABAP applications is R. The domain type for non-ABAP applications is X. If you want to export proposals irrespective of the domain type, enter *.

6. If you want to export proposals that belong to a specific domain, enter the name of the domain in the DOMANAM field. For example, BC for proposals from the Basis domain. If you want to export proposals from all domains, enter * in the field.

If you want to export proposals from several domains, start a separate export for each domain.

7. Enter the numerical value of the quality status as of which proposals are exported in the MIN_STAT field.

8. If you only want to export proposals created by a specific translator, enter this translators user name in the L_NAME field. If you want to export proposals created by all translators, enter *.

If you want to export proposals created by several translators, start a separate export for each translator.

9. Enter the last change date as of which proposals are exported in the L_DATE1 field. Enter the last change date up to which proposals are exported in the L_DATE2 field.



10. To export proposals, select the FL_PP field. If you do not want to export proposals, leave the field blank.

11. If you want to export abbreviations [Ext.], select the FL_PPA field. If you do not want to export abbreviations, leave the field blank.

12. The FL_PPX field enables you to export exceptions [Ext.]. If you do not want to export exceptions, leave the field blank.

For example, if you only want to export abbreviations, just select the FL_PPA field. If you want to export abbreviations and proposals, select the FL_PP and FL_PPA fields.

13. To start the export as a background job, select the BATCH field.

If you execute the report online, the export job could quickly terminate. This depends on the timeout setting for online processes in your system. You are therefore advised to schedule these export jobs as background processes.

14. If necessary, repeat the procedure for each additional domain to be exported, or for each additional translator whose proposals need to be exported. If you require proposal pools from several source systems, follow the same procedure in the other source systems.

Result The system creates an export file containing proposals that satisfy the criteria you entered.

Example Complete Export 1 To translate version 2 of your bank software, you want to set up a new translation system called Banken2 for English, German, French, and Spanish. Version 1 of this software has been translated into English and German in translation system Banken1 since January 01, 2001. The domains in the source and target text systems all originate from the ABAP area and are virtually identical. You do not want to make any terminology changes.

You export the entire proposal pool for German and English from translation system Banken1 with the following parameters:

T_LANG EN DE

DOMATYP * *

DOMANAM * *

MIN_STAT 1 1

L_NAME * *

L_DATE1 01.01.2002 01.01.2001

L_DATE2

FL_PP X X



FL_PPA X X

FL_PPX X X

BATCH X X

Complete Export 2 Basic domains such as the ABAP domains Basis (BC), Financial Accounting (FI), and Payroll (PY) have been translated since January 01, 2001 in translation system Standard1. You assume that some of these domains are needed as a basis for translation in many other areas, such as a banking system for asset/liability management and another system for loans. You therefore run a complete export from the Standard1 system, but only import proposals into other translation systems for the domains that exist in both the source and target translation systems. You enter the export settings as described under Complete Export 1.

Partial Export You need to set up a new banking translation system called Banken2. It will be used to translate banking-specific texts from the ABAP domain Bank Components (IS-B), and texts from the ABAP domain Basis (BC), into English and German. The banking-specific texts have been translated into German and English in translation system Banken1 since January 01, 2002. The Basis texts have been translated into German, English, French, and Italian in translation system Standard1 since January 01, 2001. Translation system Standard1 is also used to translate texts from the ABAP domains Financial Accounting (FI), Payroll (PY), and Logistics (LO). However, you do not need these domains in translation system Banken2. A number of inexperienced translators have recently translated into German in translation system Standard1 and you have not had time to check the quality of these translators work. You are satisfied with the quality of the English translations.

You run a complete export for German and English from translation system Banken1. You do this by following the instructions under Complete Export 1. You run a partial export from translation system Standard1 using the following parameters:

T_LANG DE EN

DOMATYP R R

DOMANAM BC BC

MIN_STAT 90 1

L_NAME * *

L_DATE1 01.01.2001 01.01.2002

L_DATE2

FL_PP X X

FL_PPA X X

FL_PPX X

BATCH X X



Importing the Proposal Pool Use If you import proposal pools [Ext.] into a translation system, translations that have been written before in other translation systems are made available in this translation system to support the translation of different objects. This enables you to access best proposals [Ext.] created in other translation systems, which means you do not need to retranslate source texts that have already been translated in other systems. However, there is also a danger of you transporting [Page 11] the wrong translations from one translation system to another, or translations whose terminology is incorrect. This is particularly likely to happen if translations are written for specific domains, but defined in the proposal pool as system standards instead of application standards. The same applies if there is a large gap between the release levels of both systems, such as if the source system is on Release 4.6B but the target system is on Release 6.40. It is safe to assume in such cases that major terminology changes have occurred between the two releases. To avoid such situations, use the following criteria to restrict the data that is imported from the export file:

Source language Target language Domain type Domain

The domain is the equivalent of the highest component level of the application component hierarchy in earlier releases of the R/3 environment.

Quality status Export of proposals only Export of abbreviations only Export of exceptions only

If you import proposal pools from several source systems, and if different proposals exist in these proposal pools for the same source text, and if these various proposals are all assigned to the same level (system standard, application standard) and have the same quality status, then the proposals are all inserted at the same level and with the same quality status into the target systems proposal pool. This turns the best proposal and automatic distribution into a lottery for this source text because any of the coexistent proposals could be selected.

Prerequisites The proposal pool has been exported [Page 14] from at least one suitable source system.

You are authorized to run reports using transaction SE38. The target system can access the directory that contains the files to be imported.



Procedure ...

1. In the target system, call up transaction SE38.

2. Start report RS_TRANSLATION_IMPORT_PP.

3. Enter the source language in the S_LANG field, and the target language in the T_LANG field. Each of these entries consists of four characters.

4. Enter the name of the directory that contains the proposal pool export file to be imported under DIRECTRY. Specify the name of the export file under FILENAME.

5. Enter the name of the domain under DOMATYP.

The domain type for ABAP applications is R. The domain type for non-ABAP applications is X. If you want to import proposals irrespective of the domain type, enter *.

6. If you want to import proposals that belong to a specific domain, enter the name of the domain in the DOMANAM field. For example, BC for proposals from the Basis domain. If you want to import proposals from all domains included in the export file, enter * in the field.

If you do not want to import proposals that belong to domains included in the proposal pool export file, you must start a separate import for each domain to be imported.

7. Enter the numerical value of the quality status as of which proposals are imported in the MIN_STAT field.

8. To import proposals, select the FL_PP field. If you do not want to import proposals, leave the field blank.

9. If you want to import abbreviations [Ext.], select the FL_PPA field. If you do not want to import abbreviations, leave the field blank.

10. The FL_PPX field enables you to import exceptions [Ext.]. If you do not want to import exceptions, leave the field blank.

For example, if you only want to import abbreviations, just select the FL_PPA field. If you want to import abbreviations and proposals, select the FL_PP and FL_PPA fields.

11. To start the import as a background job, select the BATCH field.

12. If necessary, repeat this procedure for each additional domain to be imported. If you require proposal pools from several source systems, follow the same procedure for each export file.

The more proposal pools you import into your target system from different source systems, the greater the risk of conflicts occurring.

Result The system writes proposals from the export files into the target systems proposal pool in accordance with the criteria you selected.



Example Complete Import To translate version 2 of your bank software, you want to set up a new translation system for English, German, French, and Spanish. Version 1 of this software has been translated into English and German in translation system Banken1 since January 01, 2001. The domains in the source and target text systems all originate from the ABAP area and are virtually identical. You do not want to make any terminology changes. The complete proposal pool has already been exported from translation system Banken1. You import the entire proposal pool for German and English from translation system Banken1 with the following parameters:

T_LANG DE EN

DOMATYP * *

DOMANAM * *

MIN_STAT 1 1

FL_PP X X

FL_PPA X X

FL_PPX X X

BATCH X X

Partial Import You need to set up a new banking translation system called Banken2. It will be used to translate banking-specific texts from the ABAP domain Bank Components (IS-B), and texts from the ABAP domain Basis (BC), into English and German. The banking-specific texts have been translated into German and English in translation system Banken1 since January 01, 2002. The Basis texts have been translated into German, English, French, and Italian in translation system Standard1 since January 01, 2001. Translation system Standard1 is also used to translate texts from the ABAP domains Financial Accounting (FI), Payroll (PY), and Logistics (LO). However, you do not need these domains in translation system Banken2. A number of inexperienced translators have recently translated into German in translation system Standard1 and you have not had time to check the quality of these translators work. You are satisfied with the quality of the English translations. The proposal pools in translation systems Banken1 and Standard1 have already been exported in their entirety.

You import the complete proposal pool from translation system Banken1, as described under Complete Import. You import the proposal pool from translation system Standard1 using the following parameters:



T_LANG DE EN

DOMATYP R R

DOMANAM BC BC

MIN_STAT 90 1

FL_PP X X

FL_PPA X X

FL_PPX X

BATCH X X



Setting Up the Translation Environment Before translation can start in an SAP system, you need to perform the following activities:

Activity For more information, see ...

Define each target language into which you want to translate

Setting Up the Target Language [Page 23]

Define the status of objects to be translated Maintaining the Secondary Language Status [Page 25]

Define the client in which translation takes place

Adding the Translation Client [Page 26]

Maintain the source language(s) for each target language

Maintaining the Translation Graphs [Page 28]

Define the object groups that each target language is to translate

Object Groups and Object Types for Translation [Page 31]

Refresh the translation hierarchy Refreshing the Translation Hierarchy [Page 35]

Create profiles for translators' authorizations Creating Translator Profiles [Page 39]

Create translators Maintaining Translators [Page 41]

Assign packages to translators and lock packages that are not relevant for translation

Package Assignment [Page 47]

Define the object types for automatic distribution during the evaluation runs

Setting Object Types for Automatic Distribution [Page 91]

After you have set up the translation environment, you can run an evaluation to create worklists and statistics in the system. For more information, see Working with the Translation Planner [Page 74].



Setting Up the Target Language Use Before the start of productive translation, you need to set up the target language (the language into which you will translate). It is not possible to perform any of the subsequent activities in the translation environment (defining the secondary language status, translation client, translation graphs, translators, and package assignment) until you have created the target language.

Prerequisites The target language into which you will translate has been defined as a language in the

translation system. For more information, see Preparing a System for Translation [Page 7].

Your user profile must contain authorization object S_ADMI_FCD with value TRNL in the field System Administration Function.

Your translator profile [Page 39] must contain authorization A1 (Language attributes administration) with value 1.

Procedure ...

1. Call up transaction SLWA. 2. Under the tab title Target language, select the desired target language. You can choose F4

on this field and then select a target language from the dialog box that appears.

3. Choose Create language.

The system displays a dialog box asking if you want to create this target language.

4. Choose Yes.

5. Repeat this procedure for all other languages into which you want to translate.

Result The system creates your language as a target language. You can now continue to set up the translation environment.



Secondary Language Status Use The secondary language status controls what type of texts appear in the worklists and the statistics, according to their status. This is particularly important when the source language of an object you are translating is actually not the original language of the object, in other words it is a translation. There are four possible attributes which you can select for each target language.

Integration The secondary language status is defined in transaction SLWA for each target language

when a translation is set up.

These settings are used in the worklists and evaluated by the translation scheduler in transaction SLWB during the evaluation run.

You can also display the translation statistics according to the secondary language status in transaction SLLS.

Features The settings made in this function allow worklists to be generated for the respective objects in transaction SE63. If the relevant statuses are not set to Translate, it will not be possible to call a worklist for the respective objects in SE63.

For example, if status 1 is set, the translator will be able to call a worklist of those objects in which the source language has been evaluated and the secondary language has been evaluated.

The statuses have the following meanings and relate to objects, not individual text lines:

Status 1: Source text is "correctly" translated, and the objects have been evaluated in the runs.

Status 2: Source text is "correctly" translated, but no evaluation has yet taken place. Status 3: Source text is not "correctly" translated, for example, contains modified texts that

have not yet been translated, but the target language needs to translate.

Status 4: Source text is not in the same system. The status of the source text is unknown. See also: Maintaining the Secondary Language [Page 25]



Maintaining the Secondary Language Status Prerequisites

The target language into which you will translate has been set up in the translation system. For more information, see Setting Up the Target Language [Page 23].



Procedure ...

1. Call up transaction SLWA. 2. Select your target language under the tab title Target language.

3. Choose the tab title Attributes.

This screen contains a table containing the secondary language statuses.

4. Select the statuses that you want to translate.

We recommend that you select all four statuses. If, however, your target language will be translating from a source language that is itself a translation, you can keep status 3 hidden until a few weeks before the translation deadline. This ensures that languages that use a translation as a source language, do not translate the same object multiple times (every time the source text (translation) changes), but instead wait until such objects are completely available in the source language.

5. Choose Translate in the menu bar.

If you want to hide a status, in other words, not translate objects with this status, select the status and choose Hide in the menu bar.

Result The system changes the text under Status accordingly.



Adding the Translation Client Use Before the start of productive translation, you need to create the translation clients in the translation system.

You can only create a client. You cannot delete a client once it has been set up.

Prerequisites The target language for which you wish to assign packages has been created in the

system. For more information, see Setting Up the Target Language [Page 23].



You should make sure that all client-specific objects, which are relevant for translation, are available in the client in which you want to translate.

Procedure ...


3. Choose the tab title Attributes.

4. Choose Add client.

The Translation Clients screen appears.

5. Enter the translation client in the field Client

6. Choose Save.

7. Repeat this procedure if you need to define additional translation clients for this target language.

8. Repeat this procedure for all target languages into which you want to translate.

Result The system displays the translation client you have added in the table Translation clients.

You can now translate within this client and it is possible for evaluations to run in this client.



Translation Graphs Use The purpose of the translation graphs is to allow translation of multilingual development in a translation system.

The graphs are language-based, not package-based (except for the Exception Packages [Page 29]).

Before the start of productive translation, you need to define the translation graphs for your translation language.

Integration The worklists that are generated in the translation system are based on the entries made in this function.

Prerequisites Languages that are entered as source languages in this function must be set up as a translation language in the translation system.

Features Using this function, you can define the source and target languages for all original languages in which development has taken place.

This means that you can translate any original language by defining the correct source language, and that you will be able to translate all objects with an original language that is not your source language (for example DE EN JA. or PT EN JA). You can display the graph that you have defined in the form of a hierarchy tree structure.

In this structure:

Red means that the language you have entered is inactive. In this system, translation does not take place into this language, so that you cannot translate into this language in the system.

Green means that translation takes place into this language in this system. The source language is accepted as such.

Yellow means that the language is translated, but the source language is not translated in this system. A language transport is required from the respective system.

Activities This action is performed by language coordinators. The language coordinator performs this action only once, before the start of productive translation.

The system ADMINISTRATOR must decide which languages to enter here.



Maintaining the Translation Graphs Prerequisites The target language into which you will translate has been set up in the translation system.

Procedure ...


3. Choose the tab title Graphs.

The system displays a table containing the translation graphs.

4. For each Original language containing objects that have to be ultimately translated in your translation system, enter the Source language from which you will actually translate and press Copy in the menu bar.

The system automatically displays the Independent languages and the Dependent languages in this table.

If a language remains in red in this table, it means that the language has not been set up for translation in this system. You cannot translate from this language. You must fetch the texts from a language import.

Result Example: Original language German is translated into English, French and Italian. English is then used as the source language for Korean.

Choose English as the target language.

Where German is the original language, define German as the source language, and press Copy in the menu bar.

Now do the same for Italian and French.

Choose Korean as the target language.

Where German is the original language, define English as the source language and press Copy in the menu bar.

You can now translate German to English and English to Korean.

To see the graph as a hierarchical tree structure, press Graph in the Translation Environment Graphs screen. The system shows the structure of the translation sequence you have defined.

If your language is shown in yellow, this means that the source language is not translated in this system, and that you need a language transport from the respective system in order to translate the language. In this case, the source language is shown in red, and the translation language is shown in yellow.

See also: Exception Packages [Page 29]



Exception Packages Use You can define translation of multilingual development in a translation system for certain packages, in the same way as for languages, as described under Translation Graphs [Page 27].

Before the start of productive translation, you need to define the exception packages for your translation language.

Exception packages either do not need to be translated into a particular language or only need to be translated into certain languages. For example:

A package which is developed in Spanish, and only needs to be translated into English A package which is only relevant for Western Europe, and therefore does not need to be

translated into Eastern European or Asian languages.

Integration The exception packages work according to exactly the same principles as the translation graphs. For more information, see Translation Graphs [Page 27].

Any settings you make here control which packages appear in the worklists for each language. For example if your translation system is set up for French, Spanish and English, and you define an exception package for translation into French only, then this package will not be included in the worklists and statistics for Spanish and English.

See also: Defining Exception Packages [Page 30]



Defining Exception Packages Prerequisites The target language into which you will translate has been set up in the translation system.

Procedure To maintain the exception packages, proceed as follows: ...

1. Call up the initial screen for transaction SLWA. 2. Select your target language under the tab title Target language.

3. Choose the tab title Graphs. The system displays a table containing the translation graphs.

4. Choose Exception DC's in the menu bar.

The system show a table of exception packages. You can add or delete entries using the buttons New entry or Delete entry in the menu bar.

If you choose Edit entry, the system takes you to the same screen as described under Maintaining the Translation Graphs [Page 28]. Please follow this procedure.



Object Groups and Object Types for Translation Definition An object group is a collection of object types of a similar translation priority, such as A_S3 (ABAP texts) or A_S4 (Repository texts). Object groups enable you to define the scope of translation for each target language. For example, you can define that a "major" language (such as English) translates all object types, and a "minor" language (such as Korean) only translates selected short text object groups.

Use After you have set up a target language [Page 23] in transaction SLWA, you need to activate object groups for translation into this language. You can only activate entire object groups, not individual object types.

The default status of an object group is Locked. If you want this object group (and all object types contained in it) to be translated into this target language, you need to set the status to Translated.

Structure You can find out the object groups and object types available for translation in transaction SLWA, by choosing Object Groups Details. Integration Once you activate an object group for a target language, all the object types contained in this object group appear in the worklists and statistics for this language, after an evaluation [Page 84] has run. If an object group is locked for a target language, the object types in this object group do not appear in the worklists and statistics. If all object groups have status Locked for a specific target language, then no evaluation takes place for this language.

If you decide at a later stage to exclude a language from the translation process, you can set the status of all object groups to Locked for this language. This ensures that the system excludes this target language from all future evaluations.

To remove objects of a specific object group from existing worklists, you need to set the status of this object group to Locked, and then schedule an evaluation with deletion. For more information, see Creating an Evaluation Run [Page 87].

See also: Defining Object Groups for Translation [Page 32]

Checking Object Type Attributes [Page 34]



Defining Object Groups for Translation Use Object groups enable you to define the scope of translation for each target language. For example, you can define that a "major" language (such as English) translates all object types, and a "minor" language (such as Korean) only translates selected short text object types. For more information, see Object Groups and Object Types for Translation [Page 31].

The default status of an object group is Locked. If you want an object group (and all object types contained in it) to be translated, you need to set the status to Translated for the target language you require.

Prerequisites The target language must be set up in this system. For more information, see Setting Up

the Target Language [Page 23].

Your translator profile [Page 39] must contain authorization A3 (Object groups administration) with value 1.

Procedure ...


3. Choose the tab title Object Groups.

The system displays a table containing the object groups. The object groups with status Translated are marked in black. The object groups with status Locked are highlighted in blue.

4. To assign object groups for translation, select the object group(s) you require and choose Translate from the application toolbar.

5. To lock object groups for translation, select the object group(s) you require and choose Lock from the application toolbar.

Result The object groups you selected are now assigned for translation. The next time an evaluation runs, it will evaluate the object types belonging to the object groups you assigned for this target language.

You can see exactly which object types are now locked and assigned for your target language by choosing Details from the application toolbar in this screen. The Object types screen appears. The assigned object types are highlighted in yellow.



Example You want to define the object groups for French so that this target language will translate short texts only. Long texts and Online Text Repository (OTR) objects are to remain locked. ...

1. Call up transaction SLWA. 2. Enter FR in the Target language field. 3. Choose the tab title Object Groups.

4. Select the following object groups: AS_1, AS_2, AS_3, AS_4, AS_5, AS_6, and CA_1. 5. Choose Translate from the application toolbar.



Checking Object Type Attributes Use You can use this function to display the following information for a specific object type:

The languages that translate this object type The object group of the object type

You can access this function from both the translation environment (transaction SLWA) and the statistics display [Ext.] (transaction SLLS).

Prerequisites You (or another coordinator) have assigned object groups for translation. For more information, see Assigning Object Groups for Translation [Page 32].

Procedure ...

1. Call up transaction SLWA.

2. Choose Extras Object Type Attributes. The dialog box Attributes of an Object Type appears.

3. Enter the abbreviation for the object type in the Object Type field. You can use F4 on this field to help you select the object type you require. For more information on object types and their abbreviations, see Object Groups and Object Types for Translation [Page 31].

Result You can now view the following information in this dialog box:

The Object Group of the object type you entered. A list of all Target Languages that translate this object type.

Example You want to find out which languages translate documentation for the Implementation Guide. ...


2. Choose Extras Object Type Attributes. 3. Enter HY in the Object Type field.

The system now displays an alphabetical list of all target languages that translate the object type Hypertext modules in this system.



Refreshing the Translation Hierarchy Use This function copies the current application hierarchy to the translation hierarchy that is available in the translation environment.

You need to refresh the translation hierarchy at the start of your translation project and each time new packages are transported to / created in the system where you are translating.

This ensures that the system offers the correct proposals for the source texts from each specific application (for example, Basis application standards if you are translating objects that belong to a Basis package).

Prerequisites Your user profile must contain authorization object S_ADMI_FCD with value TRNL in the field System Administration Function.

Procedure ...


2. Choose Environment Refresh Hierarchy. A dialog box appears, asking for you to confirm that you want to refresh the translation hierarchy.

3. Choose Yes.



Translator Profiles Use Translator profiles are groups of individual authorizations that determine which activities can be performed by translators and coordinators in the translation system, and which cannot. For example, you can create a profile that enables translators to change all proposals in the proposal pool, and another profile that enables coordinators to assign and lock packages.

The individual authorizations that are available are determined by the roles assigned to the end users in the translation system. The system administrator assigns roles to end users using transaction SU01 [Ext.]. The translator profiles in transaction SLWA facilitate fine-tuned control of authorizations.

There are various values for each authorization that determine the authorizations exact meaning.

Features The system includes the following standard translator profiles:

Translator Profile Meaning

AA Standard User Translator without proposal pool authorization [Ext.]

TA Translator Level 1 Inexperienced translator with very few rights in the proposal pool.

TG Translator Level 2 Standard translator with standard rights in the proposal pool.

TN Translator Level 3 Standard translator with extended rights in the proposal pool. Cannot flag proposals for automatic distribution or lock translations to prevent them from being changed.

TQ Translator Level 4 Standard translator with extended rights in the proposal pool. Cannot flag proposals for automatic distribution or lock translations to prevent them from being changed. The translator has coordinator status in the proposal pool. He or she can use the complex statistics to view other translators statistics.

TS Translator Level 3 (Automatic/Lock) Standard translator with extended rights in the proposal pool. Can flag proposals for automatic distribution and lock translations to prevent them from being changed.

VG Coordinator Translation coordinator with no authorization to lock packages for translation.

VN Coordinator with Lock Authorization Translation coordinator with authorization to lock packages for translation.



XH Superuser for Individual Languages Without Automatic Set

Superuser who can assign packages for different languages but cannot edit the contents.

XL Superuser for Individual Languages Superuser who can assign packages for different languages and edit the contents.

XQ Superuser With Global Lock Authorization Superuser who is authorized to lock packages globally for all languages.

XU Superuser With Translation Graph Maintenance

Superuser who is authorized to maintain exception packages.

XZ Superuser Global Superuser with all available authorizations

ZG Translation Graph (Only) User who is authorized to maintain exception packages.

The following authorizations can be assigned to translator profiles with the following values:

Authorization (Abbreviation and Definition) Value (Abbreviation and Definition)

A1 Language Attributes Administration 00 None 01 Create/Change

A2 Translation Graphs Administration 00 None 01 Create/Change 02 Exception Package (All Languages)

A3 Object Groups Administration 00 None 01 Create/Change

A4 Translator Maintenance Administration 00 None 01 Create/Change

A5 Package Administration 00 None 01 Assign 02 Assign/Lock/Unlock 03 Assign/Lock/Unlock (Global)

A6 Automatic Distribution [Page 90] Administration

00 None 01 Create/Change

A7 Package List Administration 00 None 01 Create/Change

Q1 Assign Quality Status [Ext.] 00 None 01 Quality status X 02 Quality status B 03 Quality status S 04 Quality status A



Q2 Distribute Quality Status 00 None 01 Quality status A 02 Quality status S 03 Quality status B 04 Quality status X

S1 Worklist Management 00 None 01 Create/Change

T1 Proposal Pool Maintenance For more information on these authorizations, see: Translator Profiles [Ext.].

00 None 01 Junior 02 Senior 03 Advanced 04 Coordinator 05 Superuser

T2 Proposal Pool Automatic Distribution 00 None 01 Automatic/Lock

T3 Proposal Pool Worklists (authorization for proposal pool administration)

00 None 01 Level 1 02 Level 2 03 Level 3

TS Statistics 00 None 01 Complex statistics 02 Create/Delete

For an overview of which authorizations are currently assigned to which standard SAP translator profile, call transaction SLWA. Choose Environment Translator Profiles and then Extras Overview.

Activities SAP systems are delivered with standard translator profiles. You can use them immediately. You can also create your own translator profiles. For more information, see: Creating a Translator Profile [Page 39].



Creating a Translator Profile You must assign a profile to every translator and coordinator created in the system. Each user can have just one profile per target language. For more information, see Maintaining Translators [Page 41].

You cannot create translators until translator profiles [Page 36] have been defined in the system. Each profile can include one or more authorizations.

You can create your own translator profiles or upload the SAP standard profiles into your system.

The Profile Swap function enables you to change translator authorizations globally. For example, you can assign profile XX to all translators with profile YY.

Procedure Importing Standard Profiles ...

1. Call transaction SLWA.

2. Choose Environment Translator Profiles. 3. Choose Extras Sample Profiles.

This takes you to the Create Sample Translator Profiles screen.

4. To overwrite all of the translator profiles in the system, enter X in the Overwrite Existing Values field.

5. Choose Execute.

6. Return to the Translation Environment: Translator Profiles screen by choosing Back.

The system has created 14 different translator profiles.

7. To display the authorizations assigned to a profile, select the profile and choose Detail.

8. To display an overview of all profiles together with the authorizations assigned to them, choose Extras Overview.

Creating Your Own Profiles ...


2. Choose Environment Translator Profiles. 3. Choose Create/Change.

This takes you to the Change/Create Translator Profile screen.

4. Enter a two-character name for your profile in the Translator Profile field.

5. Enter a brief description of your profile in the Description field.

6. The table of authorizations and authorization values includes a column that is ready for input. Use this column to enter an authorization value for each authorization that you require. Input help enables you to display the authorization values that are available for each authorization. You do not have to select a value for each authorization. For example, if you do not want to include the Package Administration authorization in the profile, leave authorization A5 blank. For an overview of available authorizations and authorization values, see: Translator Profiles [Page 36].

7. Save your profile.



8. Repeat these steps for all of the profiles you want to create.

9. To display an overview of all existing profiles with their authorizations, choose Extras Overview.

Swapping Profiles ...


2. Choose Environment Translator Profiles. 3. Choose Extras Profile Swap.

This takes you to the Translator Profiles: Global Swap screen.

4. In the Target Language field, enter the target language of the translators whose profile you want to swap. If you want to execute a profile swap for all of the translators in the system, irrespective of the target language, enter * in this field.

5. Enter the name of the profile to be replaced in the Old Profile field.

6. Enter the name of the profile that replaces the old profile in the New Profile field.

7. Choose Execute.

Result The translator profiles are now available in the system. You can now create translators. For more information, see Maintaining Translators [Page 41].



Maintaining Translators Use You maintain translators in the system to control what activities each user can perform in the translation system. It also enables you to assign packages to translators, and thus distribute the translation workload.

Prerequisites Before you can create translators, translator profiles must be available in the translation

system. For more information, see Creating Translator Profiles [Page 39]. Each translator can have only one profile per target language. If a user translates/coordinates translation for several languages, you need to create this user as a translator for each individual target language.

Each translator that you wish to create in the translation environment must already have a user in this system. Otherwise, the error message User name not known will appear when you try to create the translator.


Your translator profile [Page 39] must contain authorization A4 (Translator maintenance administration) with value 1.

Activities Creating Translators ...

1. Call up transaction SLWA. 2. Select your target language in the tab title Target Language.

3. Choose Translators.

4. Choose Create/Change.

The Translators screen appears.

5. In the Translator field, enter the user name of the translator you want to create.

6. In the Profile field, enter the translator profile that you want to assign to this user. You can use F4 on this field, and select a translator profile from the dialog box that appears.

7. Choose Save.

The system creates the translator, and displays the translator's user name, along with the translator's profile under No. of translators entered in the tab title Translators. You can now assign packages to this translator.

8. Repeat this procedure until you have created all the translators you require for this target language.



Deleting Translators Before you delete a translator, we recommend that you first delete the translator's package assignment. For more information, see Deleting a Translator's Package Assignment [Page 62]. ...

1. Call up transaction SLWA. 2. Select your target language in the tab title Target Language.

3. Choose Translators.

4. Select the user name of the translator you want to delete under No. of translators entered.

5. Choose Delete.

See also: Package Assignment [Page 47]

Checking a Translator's Packages [Page 61]

Deleting a Translator's Package Assignment [Page 62]



Displaying the Details of an Evaluation Run Use The Evaluations tab enables you to display the existing evaluations for the target language that you have selected.

At the top of this screen, the system displays the following details of the last evaluation run for this target language:

Run number of the evaluation (this is assigned by the system when you create an evaluation)

Start date Start time Status

On the left side of the Evaluations screen, the system contains a table of all evaluations available in the system, along with the following information:

Worklist number of the evaluation Source language defined for this target language Number of objects evaluated for this target language Description of evaluation Run number of the evaluation (this is assigned by the system when you create an

evaluation)

Date and time of the evaluation run Prerequisites Evaluation runs have taken place in the system.

Procedure ...

1. Call up transaction SLWA. 2. Enter the target language you require in the Target language tab.

3. Choose the tab title Evaluation.

4. Select an evaluation for a specific worklist number from the table on the left of the screen, and choose Detail view.

Result In the table on the right of the screen, the system displays the number of objects per object type that were evaluated for this target language in this specific evaluation run.



Working with the Information Center Use The Information function in transaction SLWA provides you with a global overview of all the data maintained in the translation environment (transaction SLWA). This function enables you to answer questions such as the following:

For which target languages is user SMITH entered as a translator/coordinator? Which translators have profile XL (Superuser for individual languages) assigned to them? Which translator profiles allow translators/coordinators to lock packages globally? Which target languages translate object group B_L1 (IMG)?

Integration The Information function contains all the data maintained in the translation environment (transaction SLWA) and information on all runs that have taken place in the translation planner (transaction SLWB). You can only use the Information Center for display purposes. It is not possible to maintain the translation environment via the Information function.

Prerequisites Before you can analyze data in the Information Center, the translation environment must be set up for at least one target language, and at least one evaluation run.

Features The table below shows you the areas of the translation system that you can analyze in the Information Center. You can display some areas according to several perspectives. For example, you can display Translators in the following ways:

All translators in the system are sorted according to the target language for which they were created.

All translators in the system listed alphabetically, along with the language for which they were created, and their translator profile. You can use this option to find users who are translators/coordinators for multiple languages.

All translators in the system are sorted according to their translator profile. You can use this option to find out which translators have a specific profile.

You can use the icons Plus and Minus to switch between display perspective.

Area Display according to ...

Translators Languages Alphabetic list of translators (including

target language and translator profile information)

Translator profiles Translator profiles All subauthorizations Authorizations Translator profiles



Locked packages Language Alphabetic list of locked packages

(including information on languages for which it is locked, and lock reason)

Lock reason Run numbers Type (initial run, object list, evaluation)

Date on which the run took place Evaluations Target language

Worklist number Object lists Run number

Original language of objects contained in object list

Automatic distribution

(Object types in which automatic distribution is active during evaluations)

Target language Active/Inactive

Target languages Alphabetic list of target languages (including information on the priority and server defined in transaction SLWB)

Priority Priority and server Server

Package lists Alphabetic list of package lists (including information on author and change date)

Change date Author

Object group assignment Language Alphabetic list of object group (including

information on which languages translate them)

Package overview Packages are sorted according to the first character of their name. Target languages are displayed (using their 1-character IDs) across the top of the screen. If a package is assigned for this language, it is marked with an X.



Activities ...


2. Choose Extras Information. A dialog box appears listing the areas that you can analyze.

3. Double-click the area that you want to analyze. For example, to find out which translator profiles contain authorization A5 with value 3, double-click Authorizations.

4. Choose Plus or Minus to switch your view on the data.

Example User JONES has left the company. You want to delete him in all instances where he was entered as a translator/coordinator in transaction SLWA. You first need to find out the target languages for which JONES was a translator/coordinator.


2. Choose Extras Information. 3. Double-click Translators from the list that appears.

4. Choose Plus once, so that the tree Translators appears.

5. Scroll down until you locate the node JONES in this alphabetical list.

6. Expand the JONES node to see the languages for which JONES was a translator/coordinator.



Package Assignment Purpose To enable translation of a package, you need to assign it to a translator in the system.

You should only assign the packages that are relevant for translation, before the start of productive translation and before worklists are created.

You can prevent unnecessary translation by locking the packages that are not relevant for translation.

You can lock packages for one specific target language, or you can lock it globally (for all target languages in the system).

The default status of a package is Open. You can leave packages as Open until you are certain whether to assign or lock them.

Prerequisites In order to be able to assign and lock packages, your user profile must contain authorization object S_ADMI_FCD with value TRNL in the field System administration function. You also need the following authorizations in your translator profile [Page 39]:

Activity Translator Profile

Assigning packages A5 (Package administration) with value 1 or higher

Locking and unlocking packages

A5 (Package administration) with value 2 or higher

Locking packages globally

A5 (Package administration) with value 3

Before package assignment is possible, the following activities must be carried out:

The target language for which you wish to assign packages has been created in the system. For more information, see Setting Up the Target Language [Page 23].

The translators to whom you wish to assign the packages have been created in the system. For more information, see Creating Translators [Ext.].



Process Flow A large number of functions are available to help you with the task of assigning and locking packages.

Activity For more information, see:

Selecting packages in order to assign them to a translator / lock them

Selecting Packages [Page 49]

Importing a list of packages that you wish to assign (or lock) from a file on your local PC

Importing and Exporting Files for Package Assignment [Page 51]

Using package lists to help you with your package assignment

Working with Package Lists [Page 53]

Assigning packages to a translator Assigning Packages [Page 57]

Locking packages and locking packages globally

Locking Packages [Page 59]

Checking which packages are assigned to a specific translator

Checking a Translator's Packages [Page 61]

Removing packages from a specific translator's assignment

Deleting a Translator's Package Assignment [Page 62]

Finding out to which translators a specific package is assigned and for which target languages it is locked

Checking Package Attributes [Page 63]

Pinpointing which packages have been assigned to more than one translator for a specific target language

Checking Packages Assigned to Multiple Translators [Page 64]

Using the Filter function to copy package assignments/locks from one language to another.

Filtering Packages [Page 66]

Copying package assignments from one system to another

Copying Package Assignments from Another System [Page 70]

Displaying an overview of packages for a specific application component and target language

Displaying an Overview of a Translation Language [Page 72]



Selecting Packages Use You need to select packages in order to perform the following activities in a translation system:

Assigning a specific set of packages to a translator Locking a specific set of packages Displaying the statistics for a specific set of packages Running an evaluation for a specific set of packages

This topic explains how you can select the packages you need for one of the above purposes, by using the Package Selection screen.

Procedure ...

1. Call up transaction SLWA. 2. Select the target language under the tab title Target Language.

3. Choose the tab title Packages.

4. You can now select the scope of packages that you require under Selection Basis. The following options are available:

{ To select all packages available in the system, choose the Total pushbutton.

{ To select all packages that still have status "Open" (in other words, packages that are neither assigned nor locked), choose the Open button.

{ To select all packages that are locked for your target language, choose the Locked pushbutton.

{ To select all packages already assigned for translation, choose the Translated pushbutton.

{ To select all packages assigned to one specific translator, choose the Translator pushbutton. You can select the translator you require from the dialog box that appears by double-clicking the translator's user name.

{ To select a generic list of packages (e.g. all packages whose name starts with Z), choose Generic and enter the initial character(s) of the packages you require in the dialog box that appears. You can also use this option to select an individual package, by entering its entire name.

{ To select packages that belong to a specific package list [Page 53], choose the Package list pushbutton. You can select the package list you require from the dialog box that appears by double-clicking the name of the package list.

{ To select packages which were created in a specific system (e.g. all packages originating from the current Basis development system), choose the Orig. system pushbutton. You can enter the name of the system in the dialog box that appears.

{ If you have a list of packages saved locally in a file on your hard drive, you can upload it to this selection screen, in order to see which packages in this list are assigned to more than one translator. To do this, choose Import, locate the file on your hard drive, then choose Open. For more information, see Importing and Exporting Files for Package Assignment [Page 51].



5. The system displays the number of selected packages in the field under Selection Basis. If you want to assign/lock/display statistics/run an evaluation for all these packages, choose the Select All icon under Selection.

If you want to further restrict the scope of your selection, you have the following options:

{ Choose Table display. The system displays the packages you have already selected in alphabetical order. You can now select the packages you need, and then choose Save.

{ Choose Hierarchy display. The system displays the packages you have already selected according to th

Documents

SAP Web as 6.20 Translation System Setup