Académique Documents
Professionnel Documents
Culture Documents
BCDOCTTC
Release 620
27.01.2004
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.
27.01.2004
Introduction
This quick guide to the SAP translation environment shows you how to use a piece list generated
for translation purposes in the Business Warehouse (BW) environment to generate worklists,
without the need for extensive training first. The quick guide only includes procedures that have
been taken from the standard documentation "Setting Up and Coordinating Translation". If you
need more detailed background information or a better understanding of how the various
transactions fit together, you are advised to refer to the appropriate sections of the standard
documentation. The headers used in the standard documentation and this quick guide are exactly
the same. Section Creating a Worklist has been taken from the standard documentation
Translation Tools for Translators.
To use all of the transactions described in this quick guide, you require authorization
S_ADMI_FCD with the value TRNR. If you need a finer definition of the authorizations, or if the
translators in your translation system do not have this authorization, you are advised to refer to
the following sections of the standard documentation: "Translator Profiles", "Maintaining
Translators", and "Assigning Packages".
27.01.2004
Content
Process Overview .................................................................................................................... 5
Setting Up the Target Language .............................................................................................. 6
Maintaining the Secondary Language Status .......................................................................... 7
Adding the Translation Client ................................................................................................... 8
Maintaining the Translation Graphs ......................................................................................... 9
Defining Object Groups for Translation.................................................................................. 10
Creating a Translator Profile .................................................................................................. 11
Maintaining Translators .......................................................................................................... 12
Assigning Packages ............................................................................................................... 13
Refreshing the Translation Hierarchy..................................................................................... 14
Scheduling an Initial Run........................................................................................................ 15
Defining Priorities and Default Servers .................................................................................. 16
Creating Object Lists .............................................................................................................. 17
Creating an Evaluation Run ................................................................................................... 18
Creating a Worklist ................................................................................................................. 19
27.01.2004
Process Overview
Before translation can start in an SAP system, you need to perform the following three steps:
1. Setup translation environment
2. Create translator profiles
3. Create translators
4. Assign packages to translators
5. Create an object list
6. Create an evaluation based on the object list
Steps 1 and 2 need to be performed only once.
Steps 2 to 6 may need to be repeated if new developments arrive in the system
Following is an overview of all activities that need to be performed:
Activity
Create translators
Assign packages
Create an evaluation
27.01.2004
Procedure
...
27.01.2004
Procedure
...
27.01.2004
Procedure
...
27.01.2004
Prerequisites
The target language into which you will translate has been set up in the translation system.
Procedure
...
27.01.2004
Procedure
...
10
27.01.2004
11
27.01.2004
Maintaining Translators
Prerequisites
Before you can create translators, translator profiles must be available in the translation
system. For more information, see Creating a Translator Profile [Page 11]. 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.
Activities
Creating Translators
...
12
27.01.2004
Assigning Packages
Prerequisites
The target language into which you will translate has been set up in the translation system.
Procedure
...
13
27.01.2004
14
27.01.2004
Procedure
...
You need to run this job only once, after you have set up your system for
translation.
15
27.01.2004
Procedure
...
16
27.01.2004
Procedure
...
17
27.01.2004
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 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.
7. 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.
8. Choose Continue. You can now schedule the evaluation run as a background job.
9. 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 16].
18
27.01.2004
Creating a Worklist
Prerequisites
You can only create a worklist of texts for those packages that have been assigned to you
Procedure
...
19