Transaction SE63

Use

Transaction SE63 enables you to perform the following activities:

·        Call up an individual object to translate it directly

·        Call up a personal worklist to find and translate objects that need translating in the collections assigned to you

·        Define your settings to suit the way you want to work with the translation tools

Integration

You can use transaction SE63 to access the following translation tools:

·        Translation Statistics

·        Proposal Pool

·        Translation Environment

Prerequisites

·        To call up an individual object for translation, you need to specify its object type and technical name.

·        To call up objects for translation via a personal worklist, the system must be set up for translation. For more information, see Setting Up and Coordinating Translation (BC-DOC-TTL).

Features

Transaction SE63 enables you to translate texts in the following three kinds of objects:

·        ABAP objects:

These objects are classic objects created in an SAP system. ABAP objects are primarily divided into the following main categories:

Ў        Short texts

Short texts consist of text fragments that appear on the user interface (for example, Save, Print, Create Order.) The text elements for data elements and programs are examples of short text objects.

Ў        Long texts (documentation)

Long text objects are documentation objects written in transaction SE61, such as message documentation and program documentation.

Ў        Other long texts

These objects include SAPscript forms, styles, and SAP Smart Forms.

Ў        Special texts XSS area pages

Table texts from the XSS area, which are technically defined as STRING types.

Ў        Transport objects

This enables you to translate objects that belong to a transport request, such as R3TR PROG ZZ_CREATE_INVOICE. For more information, see Translating Transport Objects.

·        Non-ABAP objects

These objects have been created outside an ABAP system using a programming language other than ABAP. Non-ABAP objects are primarily divided into three main categories:

Ў        Interface texts (fragments)

These are short, independent texts that consist of just a few words (such as pushbuttons and column headers.) They do not contain any continuous text.

Ў        Interface texts (sentences)

These sentences belong together to form continuous text (for example, a short set of instructions). Formatting is only possible at the end of a sentence (end of paragraph).

Ў        Objects with own formatting

This text type contains continuous text and information on how each individual line is formatted.

Activities

Translating Individual Objects

For more information, see Translating Objects Directly.

Translating Multiple Objects via a Personal Worklist

For more information on translating ABAP objects and non-ABAP objects via a personal worklist, see Calling Up a Personal Worklist.

Defining Your Translator Settings

Whenever you start working in a new SAP system for the first time, you need to define the following settings:

...

       1.      On the initial screen of transaction SE63, choose Utilities ®Settings.

       2.      Under Languages, check that your default source and target languages are correct. If they are not correct, you have to specify the source and target languages each and every time you call up a personal worklist.

       3.      Under Short Text Editor, proceed as recommended in Short Text Editor Settings.

       4.      Under Long Text Editor, proceed as recommended in Long Text Editor Settings.

       5.      Under Worklist, proceed as recommended in Worklist Settings.

Accessing the Statistics from Transaction SE63

On the initial screen of transaction SE63, choose Goto ®Statistics.

Accessing the Proposal Pool from Transaction SE63

On the initial screen of transaction SE63, choose Goto ®Proposal Pool.

Accessing the Translation Environment from Transaction SE63

On the initial screen of transaction SE63, choose Goto ®Administration.