Vous êtes sur la page 1sur 112

HELP.

BCDOCTTC

Setting Up and Coordinating


Translation (BC-DOC-TTL)

Release 640

SAP Online Help

28.08.2003

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.

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

640

SAP Online Help

28.08.2003

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.

<Example text>

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

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

640

SAP Online Help

28.08.2003

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

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

640

SAP Online Help

28.08.2003

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)

640

SAP Online Help

28.08.2003

Setting Up and Coordinating Translation (BCDOC-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]

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

640

SAP Online Help

28.08.2003

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]

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

640

SAP Online Help

28.08.2003

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.

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

640

SAP Online Help

28.08.2003

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.

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

640

SAP Online Help

28.08.2003

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.

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

640

10

SAP Online Help

28.08.2003

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 translationrelevant 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.

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

640

11

SAP Online Help

28.08.2003

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.

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

640

12

SAP Online Help

28.08.2003

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

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

640

13

SAP Online Help

28.08.2003

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.

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

640

14

SAP Online Help

28.08.2003

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<source language ID><target language ID>.<system ID>
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.

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

640

15

SAP Online Help

28.08.2003

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

L_NAME

L_DATE1

01.01.2002

01.01.2001

L_DATE2

<current date>

<current date>

FL_PP

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

640

16

SAP Online Help

28.08.2003

FL_PPA

FL_PPX

BATCH

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

DOMANAM

BC

BC

MIN_STAT

90

L_NAME

L_DATE1

01.01.2001

01.01.2002

L_DATE2

<current date>

<current date>

FL_PP

FL_PPA

FL_PPX
BATCH

X
X

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

640

17

SAP Online Help

28.08.2003

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.

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

640

18

SAP Online Help

28.08.2003

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.

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

640

19

SAP Online Help

28.08.2003

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

FL_PP

FL_PPA

FL_PPX

BATCH

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:

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

640

20

SAP Online Help

28.08.2003

T_LANG

DE

EN

DOMATYP

DOMANAM

BC

BC

MIN_STAT

90

FL_PP

FL_PPA

FL_PPX
BATCH

X
X

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

640

21

SAP Online Help

28.08.2003

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 and Coordinating Translation (BC-DOC-TTL)

640

22

SAP Online Help

28.08.2003

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.

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

640

23

SAP Online Help

28.08.2003

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]

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

640

24

SAP Online Help

28.08.2003

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].

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. 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.

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

640

25

SAP Online Help

28.08.2003

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].

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.

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
...

1. Call up transaction SLWA.


2. Select your target language under the tab title Target language.
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.

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

640

26

SAP Online Help

28.08.2003

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.

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

640

27

SAP Online Help

28.08.2003

Maintaining the Translation Graphs


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

Procedure
...

1. Call up 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. 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]

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

640

28

SAP Online Help

28.08.2003

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]

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

640

29

SAP Online Help

28.08.2003

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.

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

640

30

SAP Online Help

28.08.2003

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]

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

640

31

SAP Online Help

28.08.2003

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
...

1. Call up transaction SLWA.


2. Select your target language under the tab title Target language.
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.

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

640

32

SAP Online Help

28.08.2003

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.

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

640

33

SAP Online Help

28.08.2003

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.
...

1. Call up transaction SLWA.


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.

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

640

34

SAP Online Help

28.08.2003

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
...

1. Call up transaction SLWA.


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.

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

640

35

SAP Online Help

28.08.2003

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.

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

640

36

SAP Online Help

28.08.2003

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

A7 Package List Administration

00 None

01 Create/Change
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

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

640

37

SAP Online Help

Q2 Distribute Quality Status

28.08.2003

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

00 None

For more information on these authorizations,


see: Translator Profiles [Ext.].

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].

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

640

38

SAP Online Help

28.08.2003

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


...

1. Call transaction SLWA.


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.

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

640

39

SAP Online Help

28.08.2003

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
...

1. Call transaction SLWA.


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].

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

640

40

SAP Online Help

28.08.2003

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 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 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.

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

640

41

SAP Online Help

28.08.2003

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]

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

640

42

SAP Online Help

28.08.2003

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.

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

640

43

SAP Online Help

28.08.2003

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

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

640

44

SAP Online Help

28.08.2003

Language

Alphabetic list of locked packages


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

Lock reason

Type (initial run, object list, evaluation)

Date on which the run took place

Target language

Worklist number

Run number

Original language of objects contained in


object list

Automatic distribution

Target language

(Object types in which automatic distribution is


active during evaluations)

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

Alphabetic list of package lists (including


information on author and change date)

Change date

Author

Language

Alphabetic list of object group (including


information on which languages translate
them)

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.

Locked packages

Run numbers

Evaluations

Object lists

Package lists

Object group assignment

Package overview

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

640

45

SAP Online Help

28.08.2003

Activities
...

1. Call up transaction SLWA.


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.
1. Call up transaction SLWA.
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.

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

640

46

SAP Online Help

28.08.2003

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.].

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

640

47

SAP Online Help

28.08.2003

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]

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

640

48

SAP Online Help

28.08.2003

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].

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

640

49

SAP Online Help

28.08.2003

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 the application hierarchy. You can now select the packages
from a specific application by double clicking the packages or application node(s)
you require, for example, and then choosing Save.

Result
Now you have the number of selected packages displayed in the field under Selection.
If you are selecting packages to assign or lock, you can now choose Assign, Lock, or Lock
globally. For more information, see:
Assigning Packages [Page 57]
Locking Packages [Page 59]
If you are selecting packages in order to display the statistics, you can now choose Save to return
to the Complex Statistics screen. For more information, see Working with the Complex Statistics
[Page 99].
If you are selecting packages in order to run an evaluation, you can now choose Save to return to
the Object List Creation dialog box. For more information, see Creating Object Lists [Page 82].

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

640

50

SAP Online Help

28.08.2003

Importing and Exporting Files for Package


Assignment
Use
You can use this function to export and import lists of packages to and from a local file.

Scenario for Importing: You have received a list of packages that are relevant for
a specific translation project via email. You now want to assign the packages that
are listed in this mail quickly and efficiently.
Scenario for Exporting: You want to download a list of packages that were
assigned in a specific translation system so that you can use it as the basis for
package assignment in future systems.
Scenario for Exporting to the Clipboard: You want to send an email to somebody
which lists all packages assigned for translation in a specific system.

Prerequisites
If you are importing a file containing a list of packages, you are recommended to use a file that is
in text format for best results. If you receive a list of packages via email, for instance, you are
recommended to copy this list to a text file, and save it in ASCII format (.txt).

Importing a File of Packages into the Translation Environment


...

1. Call up transaction SLWA.


2. Select your target language under the tab title Target language.
3. Choose the tab title Packages.
4. Under Selection Basis, choose Import.
A dialog box appears where you can choose the file you require.
5. Locate the directory and file that you require from this dialog box, then choose Open.
The number of packages contained in this file is now displayed in the field under Selection
Basis.
6. You can now either select all packages that were in the file or restrict your selection of
packages. You have the following options:
To select all packages displayed under Selection Basis, choose the Select All icon
under Selection.
Choose Table display. The packages you have already selected are now displayed
in alphabetical order. You can now select the packages you need, and then choose
Save.
Choose Hierarchy display. The packages you have already selected are now
displayed according to the application hierarchy. You can now select the packages
from a specific application by double clicking the packages or application node(s)
you require, for example, and then choosing Save.
The system returns to the initial Package Processing screen. You can see the number of
packages you have selected under Selection.

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

640

51

SAP Online Help

28.08.2003

7. You can now choose to Lock or Translate the package(s) you have selected by choosing
the respective button in the menu bar. For more information, see
Assigning Packages [Page 57]
Locking Packages [Page 59]

Exporting a List of Packages from the Translation Environment


...

1. You first need to select the set of packages that you want to save as a local file. For more
information, see Selecting Packages [Page 49].
2. Once the packages that you wish to export are displayed in the field under Selection,
choose Export.
A dialog box Save As appears.
3. Locate the directory in which you wish to save this file, and enter a name and extension for
the file.

You are recommended to save your file in text (.txt) format.


4. The system saves the list of packages as a text file that lists the packages in alphabetical
order. You can now import this file into transaction SLWA in another translation system, in
order to assign or lock these packages quickly and consistently.

Exporting a List of Packages to the Clipboard


...

1. You first need to select the set of packages that you want to save as a local file. For more
information, see Selecting Packages [Page 49].
2. Once the packages that you wish to export are displayed in the field under Selection,
choose Clipboard.
3. You can now open a document or an email and use the Paste function to insert an
alphabetical list of the packages that you selected.

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

640

52

SAP Online Help

28.08.2003

Working with Package Lists


Use
You can use package lists to group together packages according to their relevance for
translation. Package lists are valid across all target languages in the system.
You can use package lists to assign the same selection of packages to multiple target languages
quickly and efficiently.
You can display the statistics according to a specific package list, and you can also use package
lists to create an object list for an evaluation.
The graphic below displays the package list interface and the functions included in it:
SLWA

Extras

List
Description

Process Package List


REF_APO
All translation-relevant packages for APO

Read existing values from database


Import list of packages
from a file on your PC

Import selection from file

16 Edit selection
Remove packages
from your list

Display an existing
package list

Edit packages
in your list

Delete selected entries on database


Save selected entries to database

Delete your
package list

Save your
package list

Delete entire package list

This section describes how you can perform the following activities:

Create a package list

Add packages to a package list

Remove packages from a package list

Delete a package list

Use a package list to assign packages to translators

Display the statistics for a specific package list

Prerequisites
To create and edit a package list, your translator profile [Ext.] must contain authorization A7
(Package list administration) with value 1.
To call up the statistics for a package list your translator profile must contain authorization TS
(Statistics) with value 1 or higher.
Setting Up and Coordinating Translation (BC-DOC-TTL)

640

53

SAP Online Help

28.08.2003

Creating a Package List


...

1. Call up transaction SLWA.


2. Choose Extras Process Package List.
3. The dialog box Package Lists appears.
4. Enter a name for your package list in the field List (Maximum: 15 characters) and a
description in the field Description.
5. You now have several options for selecting the packages for your package list:
Import selection from file
You can use this option to upload packages contained in a file on your PC. Select
the directory and file name from the dialog box that appears and choose Transfer.
The number of packages you have uploaded is displayed on the Edit selection
pushbutton.
Edit selection
You can use this option to select packages in the same way as you select them
when you use the Filter function. For more information, see Filtering Packages
[Page 66].
6. Once you have selected the packages for your package list, choose Save selected entries
to database.

Adding Packages to an Existing Package List


...

1. Call up transaction SLWA.


2. Choose Extras Process Package List.
3. The dialog box Package Lists appears.
4. Enter the name of your package list in the field List.
5. Choose Read existing values from database.
6. The system displays the number of packages in the package list, beside Edit selection
7. Choose Edit selection.
8. Choose Table display (icon

).

9. From this list, select the packages that you want to add to the group.
10. Choose Save.
11. Choose Save.
12. Choose Save selected entries to database.

Removing Packages from an Existing Package List


...

1. Call up transaction SLWA.


2. Choose Extras Process Package List.
The dialog box Package Lists appears.
3. Enter the name of your package list in the field List.
4. Choose Read existing values from database.
The system displays the number of packages in the package list, beside Edit selection

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

640

54

SAP Online Help

28.08.2003

5. Choose Edit selection.


6. Choose Table display of selection (icon

).

7. Choose Deselect all, and then select those packages that you want to remove from the
group.
8. Choose Save.
9. Choose Save.
10. Choose Delete selected entries on database.

Deleting an Entire Package List


...

1. Call up transaction SLWA.


2. Choose Extras Process Package List.
The dialog box Package Lists appears.
3. Enter the name of your package list in the field List.
4. Choose Delete entire package list.

Using a Package List to Assign Packages to Translators


...

1. Call up transaction SLWA.


2. Enter the target language you require under the Target language tab title.
3. Choose the Packages tab title.
4. Under Selection Basis, choose the Filter pushbutton.
The dialog box Filter for Package Selection Basis appears.
5. Under Optional criteria choose F4 on the Delivery field.
The dialog box Package Selection appears and lists the options you can use to filter the
packages available in this system.
6. Double-click 006 Package List.
7. Enter the name of your package list in the field Parameters that appears. You can choose
F4 on this field to help you.
8. Now choose Or relationship.
The system displays number of packages contained in this package list in the Current
selection field at the top of this dialog box.
9. Save your selection by choosing the icon

You now return to the Packages screen. The number of packages you selected now
appears in the box under Selection Basis.
10. If you want to assign 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 the application hierarchy. You can now select the packages

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

640

55

SAP Online Help

28.08.2003

from a specific application by double-clicking the packages or application node(s)


you require, for example, and then choosing Save.
11. You can now see the number of packages that you have selected in the field under
Selection. To assign these packages to a translator, choose Assign.
A dialog box appears containing a list of all the translators defined for the target language
you have selected.
12. To assign the packages that you have selected to a translator in this list, double-click the
translator's user name.

Displaying the Statistics for a Package List


...

1. Call up transaction SLLS.


2. Choose Complex Statistics.
3. Under Select packages, choose Selection of Packages.
The Package Selection screen appears.
4. Under Selection Basis, choose Package list.
A dialog box appears and lists all the package lists available in the system.
5. To select the package list for which you wish to display the statistics, double-click its name
in this list.
The number of packages contained in this package list now appears in the box under
Selection Basis.
6. If you want to display the statistics 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 the application hierarchy. You can now select the packages
from a specific application by double clicking the packages or application node(s)
you require, for example, and then choosing Save.
7. You can now see the number of packages that you have selected in the field under
Selection. Choose Save.
8. You now return to the Complex Statistics screen. To display the statistics for this package
list, choose Display.

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

640

56

SAP Online Help

28.08.2003

Assigning Packages
Use
You can use this function to assign packages to translators. Packages that are not assigned will
not be translated.

Prerequisites
The target language into which you will translate has been set up in the translation system.
Your translator profile [Page 39] should contain authorization A5 with value 1 or higher.
Each package should be assigned to one translator only, to avoid inconsistencies and confusion
of responsibilities.

Procedure
The default status of a package is Open.
...

1. Call up transaction SLWA.


2. Select your target language under the tab title Target language.
3. Choose the tab title Packages.
4. You first need to select the packages that you want to assign to a translator. For more
information, see Selecting Packages [Page 49].
You can now see the number of packages you have selected under Selection.
5. Choose Assign from the application toolbar.
A dialog box appears containing a list of all the translators that are defined for the target
language you have selected.
6. To assign the packages that you have selected to a translator in this list, double-click the
translator's user name.
The screen Package Assignment appears. The system displays the following information;
you can click on the respective button to view the packages in question:
Number of locked packages
Number of open packages
Number of packages already assigned to this translator
Number of packages already assigned to other translators
7. You can now choose between the following options:
Assign All Selected Packages
The system assigns all packages that are assigned to this translator in the source
system, regardless of whether they are locked in the target system.
Assign All Selected Unlocked Packages
The system only assigns those packages that are assigned to this translator in the
source system and that are not locked in the target system

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

640

57

SAP Online Help

28.08.2003

Cancel
If you do not want to assign any of the packages that are assigned to this translator
in the source system, you can choose Cancel.

Result
The packages that you selected are now assigned to the translator that you chose. The lines still
to be processed in these objects will now appear in this translator's statistics. When this translator
calls up a worklist, it will now contain objects, which belong to these packages and which contain
lines to be processed. If the packages you assigned initially had status Open, they will now have
status Translated.

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

640

58

SAP Online Help

28.08.2003

Locking Packages
Use
You can use this function to lock packages that are not relevant for translation. Locked packages
do not appear in worklists and are not translated.

Prerequisites
The target language into which you will translate has been set up in the translation system.
To lock a package for one specific target language, your translator profile [Page 39] should
contain authorization A5 with value 2 or higher.
To lock a package globally (for all target languages available in the system), your translator
profile [Page 39] should contain authorization A5 with value 3.

Procedure
The default status of a package is Open.
...

1. Call up transaction SLWA.


2. Select your target language under the tab title Target language.
3. Choose the tab title Packages.
4. You first need to select the packages that you want to assign to a translator. For more
information, see Selecting Packages [Page 49].
You can now see the number of packages you have selected under Selection.
5. To lock the package(s) that you have selected for the target language that you chose,
choose Lock from the application toolbar. To lock the package(s) that you have selected for
all target languages in the system, choose Lock globally from the application toolbar.
The screen Lock Packages appears. The system displays the following information; you
can click on the respective button to view the packages in question:
Number of already locked packages
Number of open packages
Number of packages already assigned to translators
Number of unknown packages
6. In the Lock reason field, enter why you are locking these packages.
7. You can now choose between the following options:
Lock All Selected Packages
The system locks all packages, regardless of whether they are already assigned to
translators for this language.
Assign All Selected Unassigned Packages
The system only locks those packages that are not already assigned to translators
for this language.

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

640

59

SAP Online Help

28.08.2003

Result
The packages that you selected are now locked (either for the individual target language that you
selected, or for all target languages defined in the system). The lines still to be processed in these
objects will no longer appear in the translators' statistics. You will only be able to see statistics for
these locked packages when you specifically call up statistics for Locked packages. Translators
are no longer able to call up worklists for objects, which belong to these packages and which
contain lines to be processed. If the packages you locked initially had status Open, they will now
have status Locked.

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

640

60

SAP Online Help

28.08.2003

Checking a Translator's Packages


Use
You can use this function to check which packages are assigned to a specific translator in the
system.

Prerequisites
You (or another coordinator) have assigned packages to translators in this system.

Procedure
...

1. Call up transaction SLWA.


2. Select your target language under the tab title Target language.
3. Choose the tab title Translators.
4. Select the respective translator and choose the button Details from the application toolbar.

Result
The system displays all the packages assigned to this translator. You can now remove packages
from this assignment if you wish. For more information, see Deleting a Translator's Package
Assignment [Page 62].

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

640

61

SAP Online Help

28.08.2003

Deleting a Translator's Package Assignment


Use
You can use this function to unassign some/all packages that have been already assigned to a
specific translator.

Prerequisites
You (or another coordinator) have already assigned packages to this translator.

Procedure
...

1. Call up transaction SLWA.


2. Select the target language into which this user translates under the tab title Target
language.
3. Choose the tab title Translators.
4. Select the respective translator and choose Details from the application toolbar.
The system displays a list of all the packages assigned to this translator.
5. To remove packages from the translator's assignment, select the package(s) and then
choose Delete assignments.

Result
As long as the packages that you removed from this translator were not also assigned to other
translators for this target language, the packages that you removed now have status Open (and
no longer have status Translated) in transaction SLWA. The system also removes these
packages from the translator's worklist and statistics.

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

640

62

SAP Online Help

28.08.2003

Checking Package Attributes


Use
You can use this function to check which users translate a specific package and for which target
languages this package is locked.

Prerequisites
You (or another coordinator) have either assigned packages to translators or locked packages in
this system

Procedure
...

1. Call up the transaction SLWA.


2. Choose Extras Package Attributes.
A dialog box Translation Attributes of a Package appears.
3. Enter the respective package and choose Continue.

You can also access this function from the tab title Packages in transaction SLWA,
by choosing Package Info from the application toolbar.

Result
The system displays the attributes of the package, including the description of the package.
Under Translated, the system lists the target languages and users who translate this package.
Under Locked, the system lists the target languages that have locked this package, together with
the lock reason.
You can also see the Component hierarchy node to which this package belongs, along with the
responsible Author of this package and the name of the Original System in which this package
was created.

This is a display tool that you cannot use for any maintenance actions.

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

640

63

SAP Online Help

28.08.2003

Checking Packages Assigned to Multiple Translators


Use
You can use this function to view all the cases where the same package has been assigned to
more than one translator for a specific target language.

Procedure
1. Call up transaction SLWA.
2. Select the target language under the tab title Target Language.
3. Choose Extras Packages with multiple assignments.
The screen Package Selection appears.
4. You can now select the scope of packages for which you want to view the multiple
assignments under Selection Basis. Only the following options make sense:
To view multiple assignments for all packages assigned for translation, choose the
Translated pushbutton.
To see which packages one specific translator "shares" with other translators,
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 view a generic list of packages assigned to multiple translators, choose Generic
and enter the initial character(s) of the packages you require in the dialog box that
appears. For example, you can use this option to find out which packages whose
name begin with a Z are assigned to more than one than one translator.
To find out which packages from a specific package list are assigned to multiple
translators, 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.
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. Now you have the number of selected packages displayed in the field under Selection
Basis. If you want to display multiple assignments 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 the application hierarchy. You can now select the packages
from a specific application by double-clicking the packages or application node(s)
you require, for example, and then choosing Save.
6. Now you have the number of selected packages displayed in the field under Selection. To
display the multiple assignments for the packages you have selected, choose Save.

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

640

64

SAP Online Help

28.08.2003

Result
The Translation hierarchy screen appears, and lists the packages from your selection that are
assigned to multiple translators for this target language. The packages are displayed according to
the application hierarchy.
You can use the Package Attributes function to find out exactly to which translators a specific
package has been assigned. For more information, see Checking Package Attributes [Page 63].

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

640

65

SAP Online Help

28.08.2003

Filtering Packages
Use
The Filter function allows you select packages according to additional criteria and also enables
you to compare certain sets of packages with each other (for example, you can compare
packages assigned to English translators with packages assigned to Japanese translators).
You can also use this function to select the packages that were either locked or assigned in a
different translation system (for example, you can use this function to guarantee that the same
packages are always locked for your target language in every translation system in which you
work).

Prerequisites
If you want to use the Filter function to compare assignments or locks between two systems, you
need to ensure that an RFC connection exists. This should be available in the system in which
you want to use the Filter function and should be defined for the system with which you wish to
compare locks/assignments. You can check if an RFC destination exists in transaction SM59. For
more information, see Displaying, Maintaining and Testing Destinations [Ext.].

Procedure
...

1. Call up transaction SLWA.


2. Select your target language under the tab title Target language.
3. Choose the tab title Packages.
4. Under Selection Basis, first choose the packages you want to filter, if necessary (for more
information, see Selecting Packages [Page 49]). You can omit this step if you want to filter
all packages, or if you do not want to make a comparison. For example, if you want select
all packages that are locked for a specific target language in a different system.
5. Choose the button Filter under Selection Basis.
The dialog box Filter for Package Selection Basis appears. The Current selection field in
this screen refers to the selection you made in step 4 (if you made any). You now have the
following options:
Compare against this selection.
Filter these packages further
Start to select packages according to the additional criteria available in this dialog
box
You can choose one of the following options to filter packages:
Assignments from another language
Locks from another language
Optional criteria
Filtering packages according to assignments from another language
1. Under Assignments from other target language, enter the name of the RFC destination for
the system where the assignments were made in the field RFC destination. If you want to
assignments from this system, leave this field empty.
2. In the field Language, enter the target language whose assignments you wish to use.
Setting Up and Coordinating Translation (BC-DOC-TTL)

640

66

SAP Online Help

28.08.2003

3. If you want to filter packages further, according to packages assigned to one specific
translator of this target language, enter the translator's user name in the Translator field.
4. Choose OR relationship to select the packages that fulfill one or both of the criteria (either
assigned for the target language you selected, or belong to the selection you made under
Selection Basis (if you made any), or both). If you did not select any packages under
Selection Basis, OR operation will provide you with all packages that match the criteria you
entered under Assignments from other target language.
5. Choose AND relationship to select the packages that fulfill both of the criteria (both
assigned for the target language you selected, and belong to the selection you made under
Selection Basis (if you made any)). If you did not select any packages under Selection
Basis, AND operation will not provide you with any packages, as your Selection Basis is
zero packages.
Filtering packages according to locks from another language
1. Under Locks from other target language, enter the name of the RFC destination for the
system where the packages were locked in the field RFC destination. If you want to use
locks from this system, leave this field empty.
2. In the field Language, enter the target language whose locks you wish to use.
3. Choose OR relationship to select the packages that fulfill one or both of the criteria (either
locked for the target language you selected, or belong to the selection you made under
Selection Basis (if you made any), or both). If you did not select any packages under
Selection Basis, OR operation will provide you with all packages that match the criteria you
entered under Locks from other target language.
4. Choose AND relationship to select the packages that fulfill both of the criteria (both locked
for the target language you selected, and belong to the selection you made under Selection
Basis (if you made any)). If you did not select any packages under Selection Basis, AND
operation will not provide you with any packages, as your Selection Basis is zero
packages.
Filtering packages according to optional criteria
...

1. Under Optional criteria, choose F4 on the Delivery field.


A dialog box appears, listing the additional options you can use to filter packages
2. You can now select one of the following options with a double-click:
Choose Delivery to select all packages that are flagged for delivery.
Choose No delivery to select all packages that are not flagged for delivery.
Choose Exception package to select all packages are defined as exception
packages.
Choose Not an exception package to select only packages are not defined as
exception packages.
Choose Generic to make a generic selection of packages, and enter the string (for
example, enter ZZ for all packages whose names begin with ZZ) in the Parameter
field that appears.
Choose Package list to select all packages that belong to a specific package list,
and enter the name of the package list in the Parameter field that appears.
Choose Import from local file to import a list of packages that you have saved as a
text (.txt) file on your hard drive. Choose F4 on the Parameter field and locate the
directory and file in the dialog box that appears.

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

640

67

SAP Online Help

28.08.2003

Choose Import from clipboard to import a list of packages from your clipboard.
3. Choose OR relationship to select the packages that fulfill one or both of the criteria (they
either match the optional criteria you defined in step 2, or belong to the selection you made
under Selection Basis (if you made any), or both). If you did not select any packages under
Selection Basis, OR operation will provide you with all packages that match the criteria you
entered under Optional criteria.
4. Choose AND relationship to select the packages that fulfill both of the criteria (they both
match the optional criteria you defined in step 2, and belong to the selection you made
under Selection Basis (if you made any)). If you did not select any packages under
Selection Basis, AND operation will not provide you with any packages, as your Selection
Basis is zero packages.
5. Choose XOR relationship to select the packages that fulfill one of the criteria, but not both
(they either match the optional criteria you defined in step 2, or belong to the selection you
made under Selection Basis (if you made any), but do not fulfill both criteria). If you did not
select any packages under Selection Basis, AND operation will only provide you with the
packages that satisfy the optional criteria that you defined, as your Selection Basis is zero
packages.

Result
The system displays the packages that you have selected in the field Current selection. To
display your current selection, choose Table display or Hierarchy display. You can now select
additional packages or deselect packages that you do not require. To select the exact opposite of
your selection, choose Invert.
You can also export the results of your filtering to a local file on your PC (icon ), or to the
clipboard (icon ). For more information, see Importing and Exporting Files for Package
Assignment [Page 51].
Once you have finished filtering the packages choose Save to return to the Package Processing
screen. 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 the application hierarchy. You can now select the packages from a specific
application by double clicking the packages or application node(s) you require, for
example, and then choosing Save.
The system displays the number of selected packages in the field under Selection.

If you are selecting packages to assign or lock, you can now choose Assign, Lock, or Lock
globally (depending on the authorizations in your translator profile). For more information, see:
Assigning Packages [Page 57]
Locking Packages [Page 59]

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

640

68

SAP Online Help

28.08.2003

Examples
Copying locks from one system to the next
Translation is moving from system TR1 to system TR2. You want to ensure that the packages
that were locked in system TR1 for target language Spanish are also locked in the new
translation system.
...

1. Make sure that an RFC destination to system TR1 is maintained in system TR2.
2. In system TR2, call up transaction SLWA.
3. Enter target language ES under the tab title Target language.
4. Choose the tab title Packages.
5. Choose the button Filter under Selection Basis.
6. Under Locks from other target languages, enter TR1 as RFC destination and ES as the
Language.
7. Choose OR relationship.
The system displays the number of packages that are locked for Spanish in system TR1 in
the field Current selection.
8. Choose Save.
The system returns to the Package Processing screen.
9. Under Selection, choose the Select All icon.
10. Proceed as described in Locking Packages [Page 59], from step 5 onwards.

Comparing assignments for two different languages


You want to compare the packages you have assigned for English against the current
assignment for Japanese in this system.
...

1. Call up transaction SLWA.


2. Enter target language EN under the tab title Target language.
3. Choose the tab title Packages.
4. Under Selection Basis, choose Translated.
5. Choose the button Filter under Selection Basis.
The dialog box Filter for Package Selection Basis appears.
6. Under Assignments from other target language, leave the field RFC destination blank and
enter JA in the Language field.
7. Choose OR operation.
In the Current selection field, the system displays those packages that are either assigned
for English, or assigned for Japanese, or both.
8. Choose AND operation.
In the Current selection field, the system displays those packages that are both assigned
for English, and assigned for Japanese.
You can further restrict this selection by entering the user name of a Japanese translator in the
Translator field.
To display the exact opposite of your Current selection, choose Invert.
Setting Up and Coordinating Translation (BC-DOC-TTL)

640

69

SAP Online Help

28.08.2003

Copying Package Assignments from Another System


Use
You can use this function to copy the assignments of packages to translators from one system to
the next.

Translation is moving from system TR1 to system TR2. You want to copy the
assignments of packages to translators for target language French from TR1
(source system) to TR2 (target system), so that they are identical in both systems.

Prerequisites
You (or another coordinator) must have assigned packages to translators in the system from
which you want to copy the assignments.
The translators for whom you want to copy the package assignments must be available as
Translators in the target system. For more information, see Maintaining Translators [Page 41].
An RFC connection exists in the target system (the system to which you want to copy the
assignments. The RFC destination should be defined for the system from which you wish to copy
the assignments. You can check if an RFC destination exists in transaction SM59. For more
information, see Displaying, Maintaining and Testing Destinations [Ext.].

Procedure
...

1. Call up transaction SLWA.


2. Enter the target language you require under the tab title Target language.
3. Choose the tab title Packages.
4. Choose Extras Copy Package Assignments.
The dialog box RFC Link appears.
5. Enter the name of the system from which you copy the package assignments, and choose
Save.
The screen Package Assignment appears for the first translator entered in SLWA for this
target language. The system displays the following information; you can click on the
respective button to view the packages in question:
Number of locked packages
Number of open packages
Number of packages already assigned to this translator
Number of packages already assigned to other translators
6. You can now choose between the following options:
Assign All Selected Packages
The system assigns all packages that are assigned to this translator in the source
system, regardless of whether they are locked in the target system.
Assign All Selected Unlocked Packages
The system only assigns those packages that are assigned to this translator in the
source system and that are not locked in the target system
Setting Up and Coordinating Translation (BC-DOC-TTL)

640

70

SAP Online Help

28.08.2003

Cancel
If you do not want to assign any of the packages that are assigned to this translator
in the source system, you can choose Cancel to branch to the next user.
7. The system now branches to the next translator for this target language. Repeat step 6
until you have copied the assignments for all translators.

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

640

71

SAP Online Help

28.08.2003

Displaying an Overview of a Target Language


Use
You can use this function to display an overview of a specific target language with regard to one
or all components/subcomponents of the application hierarchy.
The language overview displays the following information for each package in the component(s)
that you select:

Whether the package is delivered

Status of the package (Translated, Locked, or Open)

Whether the package is an exception package

Translator(s) to which the package is assigned (if the package has status Translated)

Lock reason (if the package has status Locked)

You can display the overview either sorted alphabetically by application component or sorted
alphabetically by package.

Procedure
...

1. Call up transaction SLWA.


2. Choose Extras Language Overview.
The screen Overview of Target Language appears.
3. In the field Application hierarchy area, enter a component or subcomponent of the
application hierarchy. You can use F4 on this field to help you with your selection. To
display an overview for the entire system, enter * in this field.
4. In the field Target language, enter the target language for which you want to display the
overview.
5. To display the overview sorted alphabetically by package, activate the checkbox Sort
according to package.
6. Choose Execute.

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

640

72

SAP Online Help

28.08.2003

Result
The system displays an overview of the packages in the component(s) that you selected for the
target language that you entered.
The following information is displayed for each package:
Column

Information

tpc (Delivery)

If the package is delivered, the system


displays an X in this column

Status

If the package has status Translated, the


system displays a T in this column

If the package has status Locked, the


system displays a - in this column

If the package has status Open, the


system displays an o in this column

Applicat. hierarchy

The system displays the component of the


application hierarchy to which this package
belongs

Translator or lock reason

If the package has status Translated, the


system displays the translator(s) to which
this package is assigned

If the package has status Locked, the


system displays the lock reason

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

640

73

SAP Online Help

28.08.2003

Working with the Translation Planner


The Translation Planner enables you to create worklists of objects that are relevant for your
translation project. You do this by running an evaluation. Translators can then call up their part of
the worklist (on the basis of the packages assigned to them) and translate the objects quickly and
efficiently. The evaluation also produces translation statistics which translators and coordinators
can use to monitor their personal/overall progress during the translation project.
This table gives you a brief outline of the three main steps that you need to carry out to produce
worklists in the Translation Planner.
Initial Run

An initial run resets all temporary tables used within the translation environment.
You only need to schedule an initial run once, at the start of your translation
project, and before you create an object list and run an evaluation. For more
information, see Scheduling an Initial Run [Page 77].

Object List
Run

After you have executed the initial run, you create an object list, which should
contain all the objects that are relevant for your translation project. You need to
create a new object list each time new, translation-relevant objects are
transported to / created in the translation system.
You can create object lists according to the following criteria:

A specific set of object types and packages

All object types and packages (complete system)

A specific transport request

A generic set of transport requests

For more information, see Object Lists [Page 80].


Evaluation
Run

Once an up-to-date object list is available, you then need to evaluate it. The
evaluation run analyzes the objects in the object lists. The evaluation run results
in language-specific worklists and worklist statistics for all target languages.
You can schedule the evaluation to run directly after the creation of the object list,
or you can choose to run the evaluation separately, once the object list is created.
You can run an evaluation in a variety of ways:

Without deletion: the evaluation run simply updates the previous worklists in
the system

With deletion: the evaluation run firstly deletes all previous worklists and
creates a new worklist on the basis of the new object list that it evaluates.

With automatic distribution: flagged/unique/best proposals (depending on the


setting made in transaction STMA) are distributed in new and modified texts
for the object types defined in transaction SLWA

For more information, see Evaluations [Page 84].

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

640

74

SAP Online Help

28.08.2003

Translation Planner: Overview Screen


Use
The Translation Planner: Overview screen is the initial screen of transaction SLWB.
This screen gives you general information on the status of jobs and languages in the translation
system.

Features
The Overview screen displays the following information:
No. of active jobs

This displays the number of jobs that are


currently running or planned in the system.
This number only refers to the Translation
Planner jobs (initial run, object list run, and
jobs that are part of an evaluation).

Initial run

Last run

This displays the following information about


the initial run:

Run number, which is assigned


automatically by the system

User who created this job

Start date and time

Status of the job

This displays the following information about


the last Translation Planner job that ran in the
system:

Run number, and description of the run

User who created this job

Start date and time

Status of the job

Languages in server profile

This displays the languages that have been


set up in the server profile.

Target languages in client

This displays the translation languages that


have been set up to translate in this client of
the system.

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

640

75

SAP Online Help

28.08.2003

Activities
The following functions are available in the application toolbar of this screen:

Initial run
You schedule an initial run from this screen. For more information, see Scheduling an Initial
Run [Page 77].

Job overview
To display the status of the Translation Planner jobs (both past and present) choose Job
overview. You can display the logs for these jobs and also schedule jobs that have status
Released from this overview.

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

640

76

SAP Online Help

28.08.2003

Scheduling an Initial Run


Use
You can schedule an initial run at the start of a translation project to reset all the temporary tables
required for running an evaluation. The initial run should take place at least once in a translation
system.

Prerequisites
The system has not been supplemented with a translation language.

Procedure
...

1. Call up transaction SLWB.


2. Choose Initial run from the application toolbar.
The system asks whether you want to schedule the job immediately or at a given time.
If you want to schedule the job immediately, choose the button Immediate and save
your setting.
If you want to schedule the job at a given time, specify the Date/time and save your
settings.
3. Enter a printer name and press Continue.
4. Now choose a Background server and schedule the job.

Result
The system resets all temporary tables used for the object lists and evaluations.

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

640

77

SAP Online Help

28.08.2003

Defining the Transports for Transport Evaluations


Use
You can use the Settings I tab to define the transport requests that the system should scan when
creating an object list.
You only need to define transports under Settings I if you plan to us the option Transport
evaluation according to settings to create an object list. For more information, see Creating
Object Lists [Page 82].

Procedure
...

1. Call up transaction SLWB.


2. Choose the tab title Settings I.
3. Choose Create/Change from the application toolbar.
The screen Transport Selection for Translation Environment appears.
4. In the field Transport (generic), define the source system from which the transports should
originate. You need to make a generic entry in this field. For example, if you want to define
system ABC as the source system for transport scans, you need to enter ABCK* in this
field. If you wan to scan all transport requests, regardless of their source system, enter * in
this field.
5. On the field Transport type, choose F4 to display all possible transport types, and select
one by double-clicking it. If you want to scan transport requests of all types, enter * in this
field.
6. From the table below these two fields, select the status(es) of the transport requests that
you want to scan.
7. Choose Save.
8. Repeat this procedure if you need to make further entries. For example, if you wish to scan
transports from two different source systems, or if you wish to scan two different transport
types from the same source system.

Result
When you return to the Settings I screen, the system displays the entries you have made. To
delete an entry, select the entry and choose Delete from the application toolbar.
The next time you create an object list according to the option Transport evaluation according to
settings, this object list will contain all objects included in the transport requests that match the
criteria you specific here.

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

640

78

SAP Online Help

28.08.2003

Defining Priorities and Default Servers


Use
The Settings II tab enables you to define the following for each language that is created as a
target language in transaction SLWA:

Priority: this controls the sequence in which the individual jobs per target language run
during the evaluation. An evaluation cannot run if these priorities are not defined.

Server: you can define a default background server for each language, so that the
evaluation jobs for this target language always run on this server. If your translation system
has multiple servers, you can use this function to distribute the individual background jobs,
of which the evaluation consists, evenly over several servers.

Prerequisites
Before you can define the priorities and servers for a language, you need to create it as a target
language first in transaction SLWA. For more information, see Setting Up the Target Language
[Page 23].

Procedure
...

1. Call up transaction SLWB


2. Choose the tab title Settings II.
3. Select a target language from the table and choose Change priority.
4. Select one of the seven priorities (they range from Extremely high to Extremely low).
5. If you want to define the default background server for a language, select a target language
and choose Change server.
6. Select one of the servers from the dialog box that appears.
7. Repeat this procedure for all target languages displayed in this table.

Result
The system displays the priorities and the servers you maintained in the Settings II screen for
each language.
The system takes the priorities into account when the evaluation program runs. The evaluation
jobs run first for the target language(s) with the priority Extremely high, then for the languages
with the priority Very high, and so on.
If you defined default servers, the evaluation jobs for a specific target language run on the server
you defined here.

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

640

79

SAP Online Help

28.08.2003

Object Lists
Use
The Object lists tab in transaction SLWB enables you to create and manage object lists in the
Translation Planner.
An object list should contain all objects relevant for translation, and you can create object lists
according to a variety of criteria.

Integration
The evaluations use the language-dependent object lists as the basis for creating the languagedependent translation worklists.
You need to create a fresh object list every time new objects or corrections are imported into the
system. You can then run a new evaluation to analyze the objects in this object list and thus
update the worklists.

Prerequisites
You need to successfully execute an initial run before you create an object list. For more
information, see Scheduling an Initial Run [Page 77].

Features
The object list creation program scans the system for translation-relevant entries, in accordance
with the criteria you specify (which packages, object types, transport requests should be
scanned). This determines the objects and texts that appear in the worklists.
An object can only appear in one object list. For example, if a specific object matches the criteria
of two object lists in the system, the last object list to be created will contain the object.
On the left side of the Object lists tab, the system contains a table of all object lists available in
the system, along with the following information on each object list:

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

Number of objects contained in the object list

Description of the object list

Date and time of the object list run

Activities
For information on how to create an object list, see Creating Object Lists [Page 82].
The following functions are also available in the Object lists tab, to help you manage your object
lists:
Display details of objects in existing object lists
Select an object list from the table on the left of the screen, and choose Detail view. In the table
on the right of the screen, the system displays the number of objects per original language and
object type.

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

640

80

SAP Online Help

28.08.2003

Delete entire object lists


Select an object list from the table on the left of the screen and choose Delete. The system
deletes the object list.
Merge multiple existing object lists
You can create one object list by merging several separate object lists. For example, you have
created one object list according to a set of packages, and a second object list according to
transport requests.
To do this, select two or more object lists and choose Merge. Enter a Description text for the new
object list in the dialog box that appears, and choose Continue. You can now schedule this as a
background job.
The system deletes the objects from the selected object lists and inserts them into the new object
list. Once the job has finished, the selected object lists will contain 0 objects, while the new object
list contains all the objects from the selected lists.
Select objects to create a new object list
You can use this function to create a new object list by selecting objects from existing object lists.
Select an existing object list and choose Select. Make the following entries in the Select Object
List dialog box that now appears:

Description text: Enter a description for the new object list for reference purposes.

Object list: Choose F4 on this field to select an existing object list. You can now select the
object types and packages from the object list you have selected. The objects that match
the packages and object types you select will now be included in the new object list.

No object types: Choose this button to select the object types that you want to include in
the new object list. You can select individual types or entire object groups by doubleclicking the object type or object group in the next screen, and saving your entries. When
you return to the dialog box, the button Object types will display the number of object types
you have selected.

No packages: Choose this button to select the packages that you want to include in the
new object list. The system displays the Package Selection screen. You can now proceed
as described in Selecting Packages [Page 49], and save your entries. When you return to
the dialog box, the button Packages will display the number of packages you have
selected.

Choose Continue. The system removes the objects that match your criteria from the existing
object list and inserts them into the new object list. This procedure will not, however, insert any
other objects that were not available in the existing object list.
Display a job overview
You can display the status of Translation Planner jobs by choosing Job overview. You can display
the logs for these jobs and also schedule jobs that have status Released from this overview.

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

640

81

SAP Online Help

28.08.2003

Creating Object Lists


Use
An object list should contain all objects relevant for translation, and you can create object lists
according to a variety of criteria.
Object lists serve as the basis for the evaluation run, and resulting creation of worklists and
statistics. Only the objects contained in the object list appear in the worklists and statistics.
You can create object lists according to the following criteria:

For the entire system

For a selection of packages and object types

For a generic set of transport requests from a specific date range.

For a single transport request

Prerequisites

You need to successfully execute an initial run before you create an object list. For more
information, see Scheduling an Initial Run [Page 77].

If you want to create an object list according to a generic set of transport requests, you
need to maintain the required information under Settings I. For more information, see
Defining the Transports for Transport Evaluations [Page 78].

If you want to create an object list on the basis of a single transport request, then you need
to create a transport request that contains all translation-relevant objects, and ensure that it
is available in this system.

Procedure
...

1. Call up transaction SLWB.


2. Choose the tab title Object lists.
3. Choose Create.
The dialog box Object List Creation appears.
4. Enter a description for the object list for reference purposes in the field Description.
5. If you want to create an object list according to some/all object groups and some/all
packages, proceed as follows under System evaluation:
Choose No object types and in the screen that appears, select the object types that
you want to include in the object list. You can select individual types or entire object
groups by double-clicking the object type or object group, and saving your entries.
When you return to the dialog box, the button Object types will display the number
of object types you have selected.
Choose No packages to select the packages that you want to include in the object
list. The system displays the Package Selection screen. You can now proceed as
described in Selecting Packages [Page 49], and save your entries. When you return
to the dialog box, the button Packages will display the number of packages you
have selected.

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

640

82

SAP Online Help

28.08.2003

6. If you want to create an object list according to one or more transport requests, proceed as
follows under Transport evaluation:
To create an object list on the basis of a single transport request, choose F4 on the
No evaluation field, and select Single transport from the dialog box that appears.
You now return to the Object List Creation dialog box, where you can now enter the
name of the transport request that you wish to scan in the Parameter field.
To create an object list on the basis of a generic selection of transport requests (as
defined under Settings I), choose F4 on the No evaluation field, and Transport
evaluation by settings from the dialog box that appears. You now return to the
Object List Creation dialog box, where you can now specify a date range for the
transport requests you wish to scan (for example, all transport requests from the last
month).
7. If you want the evaluation program to run automatically, immediately after the object list has
been created, activate the checkbox Start evaluation in next step.
The dialog box Worklist Number and Explanatory Text appears in which you can now
create the evaluation. For more information on how to create the evaluation, see Creating
an Evaluation Run [Page 87]. As soon as the object run finishes, the evaluation run starts
automatically.
8. Choose Continue. You can now schedule the object list run as a background job.

Result
The system creates an object list according to the criteria you specified. As soon as the object run
is finished, you can schedule an evaluation run to analyze the objects in this object list. For more
information, see Creating an Evaluation Run [Page 87].

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

640

83

SAP Online Help

28.08.2003

Evaluations
Use
The Evaluations function in transaction SLWB enables you to create and monitor evaluation runs
in the Translation Planner.

Integration
An evaluation run performs the following activities:

Scans all objects in a specific object list [Page 80] for each target language, according to
the object groups [Page 32] defined per target language

Calculates the translation status [Ext.] of each line of each object per target language

Creates / updates the worklists [Ext.] and statistics [Ext.] accordingly for all users and
target languages set up in the system

Prerequisites
Before you can create an evaluation, you need to set up the translation environment. See Setting
Up the Translation Environment [Page 22].
You can only run an evaluation if an object list already exists. See Creating Object Lists [Page
82].

Features
You can schedule the evaluation to run directly after the creation of the object list, or you can
choose to run the evaluation separately, once the object list is created.
You can run an evaluation in a variety of ways:

Without deletion: the evaluation run simply updates any existing worklists in the system, by
adding new objects and updating the status of objects in the previous worklists and
statistics.

With deletion: the evaluation run firstly deletes all existing worklists and creates a new
worklist based on the new object list that it evaluates. This means the new worklist will only
contain the objects available in the object list that you evaluate. If you decide to remove
objects from the worklist translation process (for example by locking an object group for a
specific target language), the objects in question will only disappear from the worklists if
you run the evaluation with deletion.

With automatic distribution: during the evaluation, the system performs automatic
distribution [Page 90] as follows:
For new lines with proposals whose quality status [Ext.] is equal to or higher than
the defined quality status
In object types defined for distribution
In packages that are assigned for translation.
For more information, see Automatic Distribution [Page 90].

You can use the evaluations to create more than one worklist, by assigning each evaluation a
different worklist number. This enables you to keep several projects (which have different
translation-relevant objects) separate in the same translation system.

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

640

84

SAP Online Help

28.08.2003

Make sure you communicate the number of the worklist(s) containing objects
relevant for translation to all parties involved in translation.
An object can only appear in one worklist. For example, if a specific object matches the criteria of
two worklists in the system, the last worklist to be created will contain the object.
Displaying Information on Evaluation Runs
On the left side of the Evaluations tab page, the system contains a table of all evaluations
available in the system, along with the following information for each target language included in
the evaluation:

Worklist number

Target language

Source language(s) defined for this target language

Number of objects evaluated for this target language

Description of evaluation

Run number of the evaluation (the system assigns this number when you create an
evaluation)

Date and time of the evaluation run

Activities
For information on how to schedule an evaluation, see Creating an Evaluation Run [Page 87].
The following functions in the Evaluations tab page enable you to manage your evaluations:
Display details of an evaluation run
Select an evaluation for a specific target language and worklist number from the table on the left
of the screen, and choose Detail view. In the table on the right of the screen, the system displays
the number of objects per object type evaluated for this target language.
Delete entire evaluation for a specific worklist number and target language
Select one or more evaluations from the table on the left of the screen and choose Delete. The
system deletes the evaluation. This means that translators for this target language can no longer
call up worklists with this worklist number. The statistics for this target language and worklist
number are still available. You can delete the statistics in transaction SLLS. See Organizing the
Statistics [Page 102].
Display job overview
Choose Job overview to display the individual jobs of an evaluation. You can display the logs for
these jobs and schedule jobs that have status Released from this overview.
Display last run
Choose Last run to display the status of the last/current evaluation run scheduled in the system. If
the evaluation is still running, you can choose Refresh to update the status of the individual steps
of the evaluation.

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

640

85

SAP Online Help

28.08.2003

The system displays the status of each step as follows:

Steps that are already finished are green

Steps that are currently running are blue

Steps that have not yet started are white

This function is for display purposes only. You cannot change the evaluation from
this screen.

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

640

86

SAP Online Help

28.08.2003

Creating an Evaluation Run


Use
An evaluation run provides you with worklists [Ext.] and statistics [Ext.] for all target languages
defined in the system and for the objects contained in the object list [Page 80] used in the
evaluation.

Prerequisites
You can only run an evaluation if an object list already exists. For more information, see Creating
Object Lists [Page 82].
To run an evaluation with automatic distribution, you need to define the object types for
distribution in transaction SLWA. You also need to ensure that the packages in which you want
distribution to take place are assigned for translation.
See also:
Setting Object Types for Automatic Distribution [Page 91]
Package Assignment [Page 47]

Procedure
...

1. Call up transaction SLWB and choose the tab title Evaluation.


2. Choose Create.
The dialog box Worklist Number and Explanatory Text appears.
3. Choose F4 on the field Object list for evaluation and select the object list that you wish to
evaluate from the dialog box that appears. The system uses this object list as the basis for
the evaluation.
4. In the field Worklist number, enter the number of the worklist that you want this evaluation
to create. The default worklist number is 1. If you do not wish to create a worklist with
worklist number 1, you can enter a different number. For example, if you have two different
translation projects in the same system.

Whatever worklist number you enter, you need to inform all parties involved
in translation of the worklist number.
5. In the Description field, enter a text for the evaluation run for reference purposes.
6. If you only want to run an evaluation for test purposes (for example, to calculate how long
an evaluation takes to run) activate Test run (do not change worklists). The system
evaluates the objects, but does not update the worklists or statistics.
7. If you want to run an evaluation without deletion, activate Write the worklists. The system
only performs inserts and updates to the worklists, based on the object list used for the
evaluation. The system does not delete any objects from the worklists and statistics.
8. If you want to run an evaluation with deletion, activate Write worklists and delete
beforehand. The system then deletes and rebuilds the worklist based on the objects in the
object list you are evaluating. The system deletes all objects from the worklists and
statistics, except those contained in the object list. Objects that are not included in the
object list will then no longer be available in the worklists.

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

640

87

SAP Online Help

28.08.2003

9. If you want to run an evaluation with distribution, activate Automatic distribution. The
system then runs automatic distribution [Page 90] during the evaluation.
10. To refresh the usage counters [Ext.] in the system, activate Refresh usage counters (long
runtime!). This will prolong the time it takes for the evaluation to complete, especially if your
proposal pools contain more than 10,000 entries per source and target language
combination.
11. Choose Continue. You can now schedule the evaluation run as a background job.
12. Choose Default server to ensure that the jobs for each target language run on the server
you defined in Settings II. See Defining Priorities and Default Servers [Page 79].

Result
Once the evaluation run has finished successfully, up-to-date worklists and statistics are available
for all target languages in the system.

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

640

88

SAP Online Help

28.08.2003

Translation Planner: Checks


Use
The Checks function in transaction SLWB shows you whether there are any evaluations running
in the system.
If, for example, you have started a job that cannot be continued but that does not terminate in the
appropriate manner, you can see the job under Checks. You can also terminate it here, so that
you can start a new evaluation.
Normally, a job that encounters problems should either terminate or restart. If this is not the case,
you might not be able to start the job again in the normal manner.
To terminate an evaluation that has encountered problems, choose Checks in transaction SLWB.
Then select the job and choose Cancel from the application toolbar.

You can only start a new evaluation run if no jobs are listed in the Checks screen.

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

640

89

SAP Online Help

28.08.2003

Automatic Distribution
Use
Automatic distribution supplies source texts with a suitable target text translation and then saves
the objects translated in this way.
Once you have set up automatic distribution, you can reduce the manual translation workload by
translating source texts via this method.

Integration
Automatic distribution inserts and saves translations as follows:

For new lines [Ext.] containing a source text with a proposal [Ext.] whose quality status is
equal to or higher than the quality status defined for distribution.

In object types defined for distribution [Page 91].

In packages assigned for translation [Page 57].

During an evaluation run [Page 84].

Prerequisites
Before automatic distribution can take place for a target language, proposals must exist in the
proposal pool for the source and target language in question. See Creating Proposals in the
Proposal Pool [Ext.].
To set up automatic distribution in a translation system, you need to perform the steps listed
under Activities.

Activities
Setting Object Types for Automatic Distribution [Page 91]
Assigning Packages [Page 57]
Creating an Evaluation Run [Page 87]

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

640

90

SAP Online Help

28.08.2003

Setting Object Types for Automatic Distribution


Use
You can use the Distribution function in transaction SLWA to define the object types in which
automatic distribution [Page 90] should take place during evaluations for each target language.
You also define the minimum quality status [Ext.] of the proposals that the system distributes. For
instance, if you choose quality status S, the system distributes proposals with quality status S and
higher (i.e. S and A). You can define different quality levels for different object types. See the
Example below.
You can then run automatic distribution when you run an evaluation [Page 84] in transaction
SLWB.

Prerequisites
To define object types for distribution, you need the following authorizations:

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 A6 (Automatic distribution
administration) with value 1.

You need to perform the following two steps in transaction SLWA before you can define object
types for distribution:

Create the target language. See Setting Up the Target Language [Page 23]

Assign object groups for translation into this target language. See Defining Object Groups
for Translation [Page 32].

To ensure that automatic distribution takes place during an evaluation, you need to perform the
following activities:

Assign packages that are relevant for translation to translators. See Assigning Packages
[Page 57].

Activate the flag Automatic distribution in transaction SLWB each time you run an
evaluation. See Creating an Evaluation Run [Page 87].

For automatic distribution to work effectively, proposals must exist in the proposal pool [Ext.] with
a sufficient level of quality status. See Creating Proposals in the Proposal Pool [Ext.].

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

640

91

SAP Online Help

28.08.2003

Procedure
...

1. Call up transaction SLWA.


2. Select your target language under the tab title Target language.
3. Choose the tab title Distribution.
The system displays all the object types in the system.
4. Select the object type(s) you require and choose Distribute.
The Distribution From Level dialog box appears.
5. Double-click the quality status of proposals that you want to distribute in the selected object
type(s). For best results, we recommend that you choose either A or S.
6. Repeat steps 4 and 5 as required.

Result
The quality status that you selected now appears in the Status column for the object type. In
future, the system distributes proposals with this quality status or higher in objects belonging to
this object type, as long as the Prerequisites above are satisfied.
To stop distribution, select the object type(s) and choose Do not distribute.

Example
To save translation resources, you decide to implement automatic distribution for target language
French.

For texts that appear on the user interface (object groups A_S1 to A_S4), you decide to
distribute only the highest quality proposals. You therefore define quality status A as the
minimum quality status for distribution.

For lower priority texts (object groups A_S5 and A_S6), you decide to distribute proposals
with quality status S and higher.

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

640

92

SAP Online Help

28.08.2003

Worklist Management
Use
You can use the Worklist management function to view and process the worklists of translators
when technical problems arise.
You can also use this function to reset the worklists of translators who are absent or who are no
longer working on this project, so that other translators can all up the objects that these worklists
contain.

Prerequisites
Your translator profile [Page 39] must contain authorization S1 (Worklist management) with value
1.
You also need to ensure that the translator is not currently editing his/her worklist before you try
to access it. Otherwise you may not be able to perform certain activities, such as releasing
objects from the worklist.

Features
The worklist management screen is organized according to target language and translator and
gives you an overview of the worklists for all translators who have already called up a worklist in
the system and for all languages in the system.
To view the status of translators and worklists, expand the entries for the respective language.
The translator names are listed alphabetically and the worklists are displayed in one of the
following colors:

Red: This means that the translator is currently processing the objects in his/her worklist.
You have the following restrictions:
You cannot fetch any additional objects
You cannot remove any objects from the worklist

Yellow: This means that the translator has called up a worklist and this worklist contains
objects for processing. However, the translator is not currently processing the objects in it.
You can double-click this worklist to call it up and work in the same way as the translator.

Green: This means that the translator does not currently have a worklist. In other words the
translator has either not yet called up a worklist, or has finished processing the objects in
the worklist and has released them. You can, however, still call up this "empty" worklist and
call up objects from packages assigned to this translator.

Activities
In transaction SE63, choose Worklist Worklist management. The list of translators' worklists
appears, sorted according to target language.
Expand the node of the target language you require and then double-click the user name of the
translator whose worklist you wish to process. The translator's current worklist appears. If the
translator is currently working in this worklist, you receive a warning message.
To access the worklist of a specific translator, simply pace your cursor on the user name of the
translator and choose Edit Choose. You can now perform the following activities:

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

640

93

SAP Online Help

28.08.2003

Check the translator's user settings [Ext.] by choosing Utilities Settings.

Call up an object in this worklist by double-clicking the object name. Transport Recording
[Page 106] is not, however, active in Worklist Management. Any texts you translate via
Worklist Management are not written to the transport request used in Transport Recording.

Call up additional objects in this worklist by choosing Get worklist.

Release objects from this worklist, by selecting the objects in question and choosing
Release translation.

Reset the worklist and remove all objects contained in it by choosing Worklist Reset
worklist. This now means other translators can now call up these objects in their worklists,
as long as you have assigned the relevant packages to them.

See also:
Creating and Deleting Worklists [Page 95]

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

640

94

SAP Online Help

28.08.2003

Creating and Deleting Worklists


Use
You can use the Worklist Management function to create and delete worklists for translators.

Prerequisites

Your translator profile [Page 39] must contain authorization S1 (Worklist management) with
value 1.

You cannot create a worklist for a specific translator if this translator has already called up
a worklist.

You cannot delete a worklist for a specific translator if the translator is currently processing
this worklist.

Before you create a worklist for a translator, you need to ensure that you (or another
coordinator) have assigned packages to the respective translator in transaction SLWA.

Procedure
Creating a worklist for a translator
...

1. Call up transaction SE63.


2. Choose Worklist Worklist management in the initial screen of SE63.
The Worklist: Overview screen appears.
3. Place your cursor on the respective target language and choose Edit Create.
The system displays the dialog box
4. Enter the user name of the translator for whom you wish to create a worklist in the User
name field.
5. Check that the Source language and Target language fields contain the correct information.
6. Enter the number of the worklist that you wish to create in the field Worklist number. You
can check in transaction SLWA under Evaluations to see which worklist numbers are
available. For more information, see Displaying the Details of an Evaluation Run [Page 43].
If this translator already has a worklist open under a different worklist number, then you
need to delete this worklist first. For more information, see below under Deleting a
translator's worklist.
7. Choose Enter.
The system takes you to the Worklist: Object List for User screen, which lists the object
groups open for translation into this language.
8. Place your cursor on the desired node in this list and choose Get worklist.
You can now proceed in the same way as when creating a normal worklist. For more
information, see Creating a Worklist [Ext.].
Deleting a translator's worklist
To delete a worklist, select the respective worklist in the Worklist: Overview screen and choose
Edit Delete worklist no. You can now call up a different worklist with a different worklist number
for this translator, if you require.

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

640

95

SAP Online Help

28.08.2003

See also:
Worklist Management [Page 93]

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

640

96

SAP Online Help

28.08.2003

Statistics Functions for Coordinators


Purpose
Transaction SLLS displays detailed translation statistics. It enables translators to monitor their
personal progress. Coordinators can check the overall translation status for one or more target
languages. You can display the statistics according to a wide range of criteria. It is also possible
to translate objects via transaction SLLS.

Features
The system creates the statistics in the last step of each evaluation. Coordinators can also
update the statistics at regular intervals.
You can display the statistics at any time and analyze them according to different criteria.
The following options are available to translators and translation coordinators in transaction
SLLS:
Tab Title

Activity

Statistics

Display statistics for packages assigned to you

Translators

Display statistics for all packages assigned for


translation

Translation
coordinators

Display statistics for all packages in the system

Translate via the statistics

Use the Package Selection screen to select


packages for the statistics

Translation
coordinators

Display statistics for locked packages

Display the statistics according to specific


object types/groups

Display the statistics according to secondary


language status

Translate via the statistics

Refresh the statistics for current target


language

Refresh statistics for all target languages in the


system

Translation
coordinators (with
superuser status in
SLWA)

Delete old statistics

Display a statistics history

Compare the statistics

Translation
coordinators

Display statistics for some or all languages

Translation
coordinators

Complex
statistics

Organization

History
All
Languages

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

Available to ...

640

97

SAP Online Help

28.08.2003

Activities
For more information, see:
Working with the Statistics [Ext.]
Statistics Display [Ext.]
Working with the Complex Statistics [Page 99]
Organizing the Statistics [Page 102]
Displaying the Statistics History [Page 103]
Displaying the Statistics for All Languages [Page 105]

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

640

98

SAP Online Help

28.08.2003

Working with the Complex Statistics


Use
The Complex statistics function allows you to display statistics for the following:

All packages in the system

All packages assigned for translation

Your own statistics

A selection of packages (which you can select in the same way as in transaction SLWA)

Locked packages

Object types

According to secondary language status

According to translators

Prerequisites
Your translator profile [Page 39] must contain authorization TS with value 1 or higher.
An evaluation must run at least once for statistics to be created.

Procedure
...

1. Call up transaction SLLS.


2. Select the Source Language and Target Language for which you want to display the
statistics.
3. In the Worklist number field, choose the Worklist Number for which you want to display the
statistics. The default value is ALL (statistics for all worklist numbers in the system).
4. Choose the tab title Complex Statistics.
5. Under Statistics Run, choose the date of the statistics that you want to display.
The default date is the last time the system updated the statistics to the database.
To display statistics from earlier dates, choose the
icon (Change Date) and
select a different statistics run from the dialog box that appears.
6. Under Select Packages, choose one of the following options:
All Packages
This option enables you to display the statistics for all packages, regardless of their
status (Open, Translated, or Locked).
Packages to Translate
This option enables you to display the statistics for all packages that are assigned
for translation into this target language.
My Packages
The option enables you to display the statistics for the packages that are assigned
to you.
Selection of Packages

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

640

99

SAP Online Help

28.08.2003

If you select this option, the Package Selection screen appears. You can now select
the packages for which you want to display the statistics in exactly the same way as
you select packages in transaction SLWA. For more information, see Selecting
Packages [Page 49].
Locked Packages
This option enables you to display the statistics for all packages that are locked for
this target language.
7. Under Format, you can define how you want to display the statistics:
Display Percentages
Activate this option if you want to display the statistics in terms of both lines and
percentages.
Only Display not Completely Translated Objects
Deactivate this option to display all objects, regardless of whether they still contain
lines to translate. You can then locate all objects for a specific package and object
types, if you need to make terminology changes, for example.
Applications
Activate this option if you want to display the statistics according to application
components.
Object Groups
Activate this option if you want to display the statistics according to object groups.
Translators
Activate this option if you want to display the statistics according to individual
translators.
8. Under Select Object Types, you can define the object types for which you want to display
the statistics. The default value is all object types in the system (option All). You can
change this value as follows.
Selection
If you select this option, the Object Types screen appears. You can now
deselect/select the object types you require with a double-click. You can
deselect/select all object types belonging to a specific object group by doubleclicking the object group. Choose Save to return to the Complex Statistics screen.
Translated
This option enables you to display the statistics for all object types that are assigned
for translation into this target language.
9. Under Secondary Language Status, you can define the secondary language status [Page
24] for which you want to display the statistics, by simply activating/deactivating the
checkboxes for each of the four available values. The default setting is the same as the
setting made in transaction SLWA.
10. Choose Display.

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

640

100

SAP Online Help

28.08.2003

Result
The system displays a list of statistics according to the criteria you selected. You can expand the
statistics according to package or object type. Arrows then indicate where you will find objects
containing texts for translation.
See also:
Statistics Display [Ext.]

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

640

101

SAP Online Help

28.08.2003

Organizing the Statistics


Use
The Organization function in transaction SLLS enables you to do the following:

Refresh the statistics for current target language

Refresh statistics for all target languages in the system

Delete old statistics

Prerequisites
Your translator profile [Page 39] must contain authorization TS with value 2.

Procedure
...

1. Call up transaction SLLS.


2. Select the Source Language and Target Language for which you want to display the
statistics
3. Choose the tab title Organization.
The Organization screen appears. The system displays a list of all statistics runs available
for this target language in the system. You can now perform the following activities:
Refresh the statistics for the current target language
To update the statistics for the target language you selected in step 2, choose Write
Statistics to DB (Current Lang.). Confirm the dialog box that appears, and then enter
a comment for your statistics run in the next dialog box. Select a background server
from the dialog box that appears. The system starts a background job called
TR_STAT_<today's date>_<Target language> which you can monitor in transaction
SM37. You can return to the Organization and choose Refresh until your statistics
run appears at the top of the list. You can recognize it by the comment you entered.
Refresh the statistics for all target languages
To update the statistics for all target languages in the system, choose Write
Statistics to DB (All Languages). Confirm the dialog box that appears, and then
enter a comment for your statistics run in the next dialog box. Select a background
server from the dialog box that appears. The system starts a background job called
TR_STAT_<today's date>_* which you can monitor in transaction SM37. You can
return to the Organization and choose Refresh until your statistics run appears at
the top of the list. You can recognize it by the comment you entered.
Deleting statistics for a specific target language
To delete older versions of the statistics that are no longer needed, select the
version(s) of the statistics you wish to delete from the list in this screen and choose
Delete. The system deletes these statistics from the database.

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

640

102

SAP Online Help

28.08.2003

Displaying the Statistics History


Use
You can use the History function in transaction SLLS to do the following:

Compare several versions of the statistics with a Reference version of the statistics, so that
you can see the difference in number of lines between the various sets of statistics

Display multiple statistics to see the development of the statistics over a longer period of
time

You can also display the statistics history according to the criteria available in Complex statistics
(according to specific packages, object groups, secondary language status).

Prerequisites
Your translator profile [Page 39] must contain authorization TS with value 2.
An evaluation must run at least once for statistics to be created.

Procedure
1. Call up transaction SLLS.
2. Select your Source Language and Target Language for which you want to display the
statistics.
3. In the Worklist number field, choose the Worklist Number for which you want to display the
statistics. The default value is ALL (statistics for all worklist numbers in the system).
4. Choose the tab title History.
5. If you wish to make a comparison, choose the date of the statistics with which you compare
the other statistics under Reference statistics. The default date is the last time the system
updated the statistics to the database. To use a reference from an earlier date, choose the
icon (Change Date) and select a different statistics job from the dialog box that appears.
If you do not want to make a comparison (but simply want to list multiple statistics from
different dates), you can leave the date as the default value.
6. Under Select packages, Format, Select object types, and Secondary language status you
can define the criteria for which you want to display the statistics. For more information on
these options, see Working with the Complex Statistics [Page 99] (steps 6 to 9).
7. To perform a comparison, activate the checkbox Difference to Reference Statistics under
Format.
8. In the table at the bottom of the screen, select the all the statistics runs that you want to
display / with which you want to compare the reference statistics.
9. Choose Display.

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

640

103

SAP Online Help

28.08.2003

Result
The system now displays a list of the statistics runs from the dates you selected. The date of
each statistics run is displayed in the column Statistics Run. To increase the width of this column,
click the column title and select the width you require from the dialog box that appears. For more
information on the functions available in this screen, see Statistics Display [Ext.].
If you left the option Difference to Reference Statistics deactivated, the system displays a list of
the separate statistics runs that you selected, according to the criteria you defined in step 6.
If you activated the option Difference to Reference Statistics, the system displays the differences
in lines between each statistics run and the reference statistics for each statistics run that you
selected in step 8.

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

640

104

SAP Online Help

28.08.2003

Displaying the Statistics for All Languages


Use
The All Languages function enables you to display the statistics for all (or some) languages
translating in the system.
You can display the statistics for all languages according to the criteria available in Complex
statistics:
You can also change the statistics date to display older statistics for all languages.

Prerequisites
Your translator profile [Page 39] must contain authorization TS with value 2.
An evaluation must run at least once for statistics to be created.

Procedure
1. Call up transaction SLLS.
2. In the Worklist number field, choose the Worklist Number for which you want to display the
statistics. The default value is ALL (statistics for all worklist numbers in the system).
3. Choose the tab title All Languages.
4. Under Select packages, Format, Select object types, and Secondary language status you
can define the criteria for which you want to display the statistics. For more information on
these options, see Working with the Complex Statistics [Page 99] (steps 6 to 9).
5. The table at the bottom of this screen contains the most recent statistics run for each target
language for which statistics exist in the system. If you want to display statistics from an
earlier date for a specific target language, select the language, and choose Change
Selection. You can now select a different statistics run from the dialog box that appears.
6. All target languages are automatically selected in this table. If you only want to display the
statistics for some (and not all) languages, deselect the target languages for which you do
not want to display the statistics.
7. Choose Display.

Result
The system now displays the statistics for all languages that you selected. The statistics are
organized as follows: statistics for locked packages for each language, then statistics for open
packages, and then statistics for assigned packages are displayed for each date and language.
The date of each statistics run is displayed in the column Statistics Run. To increase the width of
this column, click the column title and select the width you require from the dialog box that
appears. For more information on the functions available in this screen, see Statistics Display
[Ext.].

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

640

105

SAP Online Help

28.08.2003

Transport Recording
Purpose
Transport Recording enables you to collect translations for a specific target language in a
transport request. You can then use this transport request to transport the translations to other
systems.
This means you can provide test and productive systems with all English translations created this
week, for instance. You can thus avoid having to perform language transports for the whole
system or a set of packages, for example.

Integration
Transport Recording enables you to create transport requests per target language. You can then
run a program to collect translations saved in transaction SE63 [Ext.] over a specific date range.
The system writes these translations to the transport request that you specify.
You can manage transport requests created in Transport Recording in exactly the same way as
standard transport requests. For more information, see Transport Organizer (BC-CTS-ORG)
[Ext.].

Features
When you collect objects in a Transport Recording request, the system writes a detailed log,
listing any translations that could not be written to the request.
The transport requests in Transport Recording are filled with LANG objects. They do not contain
the original development objects. For instance, the translation of message SKTY 009 is recorded
as follows:
LANG MESS SKTY009
This means that you do not harm development objects when you transport translations using
Transport Recording requests.

Translations of the following two object types are recorded as R3TR TABU entries in
Transport Recording requests:
Hierarchy node texts (SHI3)
Extensions of a hierarchy (SHI5)

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

640

106

SAP Online Help

28.08.2003

Activities
To use Transport Recording to transport translations to other systems, you need to proceed as
follows:
...

1. Create transport requests for each target language translating in the system.
See Creating Requests in Transport Recording [Page 108].
2. Collect translations for each target language in the transport requests that you created.
See Filling Requests with Translations in Transport Recording [Page 110].
3. Display the transport requests.
See Displaying Requests in Transport Recording [Page 112].
4. Release the requests and transport the translations to other systems.
Here you proceed in exactly the same way as for standard transport requests. See the
corresponding documentation Transport Organizer (BC-CTS-ORG) [Ext.] from topic
Request Editor [Ext.] onwards.

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

640

107

SAP Online Help

28.08.2003

Creating Requests in Transport Recording


Use
Before you can start recording translations, you need to create a transport request in Transport
Recording. You can then fill this request with the translations saved in transaction SE63 [Ext.] for
a specific date range and target language.

Prerequisites
To use Transport Recording, your user profile must include authorization object S_TRANSLAT
with activity A8 for the target language(s) you want to record.
You also require sufficient authorization for creating transport requests. The default request type
in Transport Recording is Transport of Copies. To create a transport of copies, you require
authorization object S_TRANSPRT with activity 01 (Create) for request type TRAN (Transport of
Copies).

Procedure
In t...

1. In transaction SE38, execute program RS_LXE_RECORD_TORDER directly (choose F8).


The screen LXE Collect Translations in Transport Request appears.
2. Choose the

icon (Create Transport Request).

The Create Transport Request dialog box appears.


3. If a Transport Recording request already exists for this target language, a message
appears in the status bar to inform you. You can display existing Transport Recording
requests from this dialog box as follows:
Choose the

icon to display transport requests for the current target language.

Choose the

icon to display transport requests for all target languages.

4. Make the following entries in this dialog box:


Client

This field already contains the client in which you are currently logged
on. You cannot change this field.

Language

Enter the target language of translations to be recorded in this


transport request. The default language is your logon language. To
change the contents of this field, choose F4 and select a language
from that list that appears.

Request Type

The default request type is Transport of Copies. This ensures that any
transport requests that are released unintentionally are not
automatically imported into other systems.
You can also choose Consolidation transport. This ensures that, when
it is released, this request is automatically imported into target
systems on the same transport route.

Target System

This entry is not obligatory. You can enter any target system.
However, when you release the transport request, you must enter the
correct target system.

Request
Changeable

Activate this checkbox if you want it to be possible to change the


attributes (e.g. owner) of this request at a later stage.

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

640

108

SAP Online Help

Short Text for


Request

28.08.2003

The short text for the request consists of two parts:

Under Generated Part, the system enters a short text


containing the following information: Translation <Target
Language> <Client> <Date>.

Under Variable Part, you can enter a short text to help you
recognize this request when you fill it with translations.

5. Choose Save to save your transport request.

Result
The system creates a transport request for the target language you selected. You can now
execute the program to fill this transport request with translations for this target language.
For more information, see Filling Requests with Translations in Transport Recording [Page 110].

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

640

109

SAP Online Help

28.08.2003

Filling Requests with Translations in Transport


Recording
Use
You can fill a Transport Recording request with translations as follows:

For a specific target language.

For a selection of object types translated in the system.

For a specific date range.

For a specific user.

You can fill a Transport recoding request with translations for target language
English of all object types saved since the start of the current week by user SMITHJ.

Prerequisites
You must first create a transport request for the target language in question. See Creating
Requests in Transport Recording [Page 108].
To use Transport Recording, your user profile must include authorization object S_TRANSLAT
with activity A8 for the target language(s) you want to record.

Procedure
...

1. In transaction SE38, execute program RS_LXE_RECORD_TORDER directly (choose F8).


The screen LXE Collect Translations in Transport Request appears.
2. In the Target Language field, enter the 2-character ID of the target language for which you
want perform Transport Recording.
3. In the Object Type fields, you can enter one, several, or a range of object types for which
you want to collect translations. If you leave these fields blank, translations of all object
types are written to the transport request.
4. In the Editing Period fields, enter the date range of the translations you want to collect in
the transport request. To collect translations regardless of the date when they were saved,
leave these fields blank.
5. In the Object Processor fields, you can specify the translator(s) whose translations you
want to collect. To collect translations saved by all users, leave these fields blank.
6. To run this job in the background, activate the checkbox Schedule Background Run. We
recommend that you run this job in the background if you plan to collect a large amount of
translations, or if the system load is high.
7. Choose Execute (F8).
The dialog box Choose a valid transport request appears, listing all valid Transport
Recording requests that exist for this target language.
8. Double-click the request in which you want the system to collect the translations.

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

640

110

SAP Online Help

28.08.2003

Result
The system writes the translations that match your selection criteria to the transport request that
you selected.
The system also writes a detailed log, listing any objects that could not be written to the transport
request.
You can now display this request to view the objects for which the system collected translations.
You can also release this request in order to supply other systems with the translations. For more
information, see Displaying Requests in Transport Recording [Page 112].

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

640

111

SAP Online Help

28.08.2003

Displaying Requests in Transport Recording


Use
You can display the transport requests that you have created and filled with translations in
Transport Recording. The system takes you to the functionality of the standard transport request
transaction SE09.
You can then release the Transport Recording requests, in order to transport the translations to
further systems.

Prerequisites
To use Transport Recording, your user profile must include authorization object S_TRANSLAT
with activity A8 for the target language(s) you want to record.
When you display requests in Transport recording, the system only displays the requests that
have been created in Transport Recording. If you create other transport requests using outside
Transport Recording, the system does not display them in this screen.

Procedure
...

1. In transaction SE38, execute program RS_LXE_RECORD_TORDER directly (choose F8).


The screen LXE Collect Translations in Transport Request appears.
2. Proceed as follows, to display the Transport Recording requests:
To display requests for an individual target language, enter the 2-character
language ID in the Target Language field, and choose the
icon.
Choose the

icon to display transport requests for all target languages.

The screen Transport Requests Used in Translation Environment appears, listing the
request(s) created in Transport Recording.
3. Double-click a request from the list to display and release it.

Result
The system displays the request, and you can now release it, in order to transport the translations
it contains to further systems.
Here you proceed in exactly the same way as for standard transport requests. See the
corresponding documentation Transport Organizer (BC-CTS-ORG) [Ext.] from topic Request
Editor [Ext.] onwards.

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

640

112