SAP ABAP Data Element LXEWLISTID (Worklist Number)
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-DOC-TTL (Application Component) Translation Tools
     SLXE (Package) New MLT Environment
Basic Data
Data Element LXEWLISTID
Short Description Worklist Number  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type LXEWLISTID    
Data Type CHAR   Character String 
Length 4    
Decimal Places 0    
Output Length 4    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 WL ID 
Medium 17 Worklist ID 
Long 20 Worklist ID 
Heading 17 Worklist ID 
Documentation

Definition

The translation worklist is a pool of language-specific objects that need to be translated into a specific target language. It is generated in Translation Administration (transaction LXE_MASTER) on the basis of a language-independent object list.

There are two ways of creating a new worklist:

  • Implicitly, by scheduling an evaluation run for which a new worklist number is used. In this case, the new worklist is generated automatically and the description of the evaluation is used to describe the new worklist too.
  • Explicitly, by calling LXE_MASTER and choosing Evaluations -> Worklists. You can then enter your own description.

Irrespective of how the worklist was created, you can change its description at any time by calling LXE_MASTER and choosing Evaluations -> Worklists.

Use

The worklist is used to assign work to translators (by assigning collections to translators). These "personal worklists" can be called up and processed in the translation editor (transaction SE63).

Dependencies

In theory, it is possible to create up to 9999 different worklists. In practice, you always use - and therefore refresh - the same worklist for evaluations that run time and time again.

A translation object can only exist in one worklist at a time. If objects belong to more than one worklist, they are always stored in the last worklist that was generated.

Example

History
Last changed by/on SAP  20110908 
SAP Release Created in 610