BCDOCTTC
Release 640
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.
640
28.08.2003
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style
Description
Example text
Example text
EXAMPLE TEXT
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.
640
28.08.2003
640
28.08.2003
640
28.08.2003
640
28.08.2003
Implementation Considerations
Before you start maintaining the translation environment, you should:
provide or extend system resources - please see System Resource Setup [Page 9]
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]
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]
640
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.
640
28.08.2003
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.
640
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.
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.
640
10
28.08.2003
Prerequisites
A suitable proposal pool exists. For example, it originates from one of the following systems:
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:
640
11
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.
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.
640
12
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
640
13
28.08.2003
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
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.
640
14
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
...
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 *.
640
15
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
640
16
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
640
17
28.08.2003
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
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.
640
18
28.08.2003
Procedure
...
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.
640
19
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:
640
20
28.08.2003
T_LANG
DE
EN
DOMATYP
DOMANAM
BC
BC
MIN_STAT
90
FL_PP
FL_PPA
FL_PPX
BATCH
X
X
640
21
28.08.2003
Create translators
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].
640
22
28.08.2003
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
...
Result
The system creates your language as a target language. You can now continue to set up the
translation environment.
640
23
28.08.2003
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]
640
24
28.08.2003
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
...
Result
The system changes the text under Status accordingly.
640
25
28.08.2003
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
...
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.
640
26
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.
640
27
28.08.2003
Procedure
...
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]
640
28
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]
640
29
28.08.2003
Procedure
To maintain the exception packages, proceed as follows:
...
640
30
28.08.2003
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]
640
31
28.08.2003
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
...
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.
640
32
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.
...
640
33
28.08.2003
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
...
Result
You can now view the following information in this dialog box:
Example
You want to find out which languages translate documentation for the Implementation Guide.
...
640
34
28.08.2003
Prerequisites
Your user profile must contain authorization object S_ADMI_FCD with value TRNL in the field
System Administration Function.
Procedure
...
640
35
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
TA Translator Level 1
TG Translator Level 2
TN Translator Level 3
TQ Translator Level 4
VG Coordinator
640
36
28.08.2003
XZ Superuser Global
The following authorizations can be assigned to translator profiles with the following values:
00 None
01 Create/Change
00 None
01 Create/Change
02 Exception Package (All Languages)
00 None
01 Create/Change
00 None
01 Create/Change
A5 Package Administration
00 None
01 Assign
02 Assign/Lock/Unlock
03 Assign/Lock/Unlock (Global)
00 None
00 None
01 Create/Change
01 Create/Change
00 None
01 Quality status X
02 Quality status B
03 Quality status S
04 Quality status A
640
37
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
00 None
01 Junior
02 Senior
03 Advanced
04 Coordinator
05 Superuser
00 None
01 Automatic/Lock
00 None
01 Level 1
02 Level 2
03 Level 3
TS Statistics
00 None
01 Complex statistics
02 Create/Delete
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].
640
38
28.08.2003
Procedure
Importing Standard Profiles
...
640
39
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
...
Result
The translator profiles are now available in the system. You can now create translators. For
more information, see Maintaining Translators [Page 41].
640
40
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
...
640
41
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].
...
640
42
28.08.2003
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:
Description of evaluation
Run number of the evaluation (this is assigned by the system when you create an
evaluation)
Prerequisites
Evaluation runs have taken place in the system.
Procedure
...
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.
640
43
28.08.2003
Which translators have profile XL (Superuser for individual languages) assigned to them?
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
Translators
Languages
Translator profiles
Translator profiles
All subauthorizations
Authorizations
Translator profiles
640
44
28.08.2003
Language
Lock reason
Target language
Worklist number
Run number
Automatic distribution
Target language
Active/Inactive
Target languages
Priority
Server
Change date
Author
Language
Locked packages
Run numbers
Evaluations
Object lists
Package lists
Package overview
640
45
28.08.2003
Activities
...
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.
640
46
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
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.].
640
47
28.08.2003
Process Flow
A large number of functions are available to help you with the task of assigning and locking
packages.
Activity
Displaying an Overview of a
Translation Language [Page 72]
640
48
28.08.2003
Selecting Packages
Use
You need to select packages in order to perform the following activities in a translation system:
This topic explains how you can select the packages you need for one of the above purposes, by
using the Package Selection screen.
Procedure
...
640
49
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].
640
50
28.08.2003
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).
640
51
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]
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.
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.
640
52
28.08.2003
Extras
List
Description
16 Edit selection
Remove packages
from your list
Display an existing
package list
Edit packages
in your list
Delete your
package list
Save your
package list
This section describes how you can perform the following activities:
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
28.08.2003
).
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.
640
54
28.08.2003
).
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.
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
640
55
28.08.2003
640
56
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.
...
640
57
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.
640
58
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.
...
640
59
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.
640
60
28.08.2003
Prerequisites
You (or another coordinator) have assigned packages to translators in this system.
Procedure
...
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].
640
61
28.08.2003
Prerequisites
You (or another coordinator) have already assigned packages to this translator.
Procedure
...
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.
640
62
28.08.2003
Prerequisites
You (or another coordinator) have either assigned packages to translators or locked packages in
this system
Procedure
...
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.
640
63
28.08.2003
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.
640
64
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].
640
65
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
...
640
66
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
...
640
67
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]
640
68
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.
640
69
28.08.2003
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
...
640
70
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.
640
71
28.08.2003
Translator(s) to which the package is assigned (if the package has status Translated)
You can display the overview either sorted alphabetically by application component or sorted
alphabetically by package.
Procedure
...
640
72
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)
Status
Applicat. hierarchy
640
73
28.08.2003
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:
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.
640
74
28.08.2003
Features
The Overview screen displays the following information:
No. of active jobs
Initial run
Last run
640
75
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.
640
76
28.08.2003
Prerequisites
The system has not been supplemented with a translation language.
Procedure
...
Result
The system resets all temporary tables used for the object lists and evaluations.
640
77
28.08.2003
Procedure
...
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.
640
78
28.08.2003
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
...
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.
640
79
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)
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.
640
80
28.08.2003
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.
640
81
28.08.2003
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
...
640
82
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].
640
83
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.
640
84
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
Description of evaluation
Run number of the evaluation (the system assigns this number when you create an
evaluation)
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.
640
85
28.08.2003
This function is for display purposes only. You cannot change the evaluation from
this screen.
640
86
28.08.2003
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
...
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.
640
87
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.
640
88
28.08.2003
You can only start a new evaluation run if no jobs are listed in the Checks screen.
640
89
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.
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]
640
90
28.08.2003
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.].
640
91
28.08.2003
Procedure
...
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.
640
92
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:
640
93
28.08.2003
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.
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]
640
94
28.08.2003
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
...
640
95
28.08.2003
See also:
Worklist Management [Page 93]
640
96
28.08.2003
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
Translators
Translation
coordinators
Translation
coordinators
Translation
coordinators (with
superuser status in
SLWA)
Translation
coordinators
Translation
coordinators
Complex
statistics
Organization
History
All
Languages
Available to ...
640
97
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]
640
98
28.08.2003
A selection of packages (which you can select in the same way as in transaction SLWA)
Locked packages
Object types
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
...
640
99
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.
640
100
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.]
640
101
28.08.2003
Prerequisites
Your translator profile [Page 39] must contain authorization TS with value 2.
Procedure
...
640
102
28.08.2003
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.
640
103
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.
640
104
28.08.2003
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.].
640
105
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)
640
106
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.
640
107
28.08.2003
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...
Choose the
This field already contains the client in which you are currently logged
on. You cannot change this field.
Language
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
640
108
28.08.2003
Under Variable Part, you can enter a short text to help you
recognize this request when you fill it with translations.
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].
640
109
28.08.2003
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
...
640
110
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].
640
111
28.08.2003
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
...
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.
640
112