Source language of texts in top text objects

In the LANGUAGE field, enter the language in which the source texts should appear in the top text objects.

For example, if you are creating top texts for a target language that translates from source language German, enter deDE in this field.

Worklist number

Choose F4 on the WLISTID field and in the dialog box that appears, select the worklist that should be the basis for the top texts.

Target language

In the TARG_LAN field, enter the target language for which you want to create top texts.

Source language

If your target language translates from more than one source language (this happens in very rare cases), you can restrict the top texts so that they only contain source texts of one of the source languages. Otherwise, we recommend that you do not change the default value for the SOUR_LAN field.

Status of objects in worklist

To improve system performance, we recommend that you enter the value N in the STATTRN field, so that only objects with at least 1 new line are included in the scan to create top texts. This ensures that objects that are already 100% translated are not included in the scan, which speeds up the job.

Name of top texts

Enter a text string in the NAME field that will help you recognize the top texts when you call them up in transaction SE63.

Description of top texts

You can enter a description of up to 40 characters in the DESCRIPT field to document how you created the top texts, for example.

Frequency of source texts

Enter the minimum repetition level of the source texts in the MIN_FREQ field. For example, if you only want the top texts to contain source texts that occur three times or more in the worklist for this target language, enter 3 in this field.

Target language

Enter the target language again in the T_LANG field. This entry ensures that the system uses the correct proposal pool if you change the entries in the next 2 fields.

Status of proposals

Here you can restrict the source texts that the top texts contain according to whether proposals exist for the source text yet. For example:

●      To create top texts that only contain source texts for which no proposals exist as yet, leave the MIN_STAT field blank and enter 1 in the MAX_STAT field.

●      To create top texts that only contain source texts for which status B proposals exist (to check the work of beginner translators, for example), choose F4 on the MIN_STAT field and select status B, then choose F4 on the MAX_STAT field and select status B again. The system enters the lower and upper numeric values of quality status B respectively.

●      To create top texts that only contain source texts for which proposals of status B or S exist (to find any proposals that could be upgraded to status A), choose F4 on the MIN_STAT field and select status B, then choose F4 on the MAX_STAT field and select status S.

Status of texts to be scanned

You can also restrict the source texts contained in the top texts according to the translation status of the lines in which the source texts occur in the worklist you are scanning. For example:

●      To create top texts that only contain source texts that occur in new lines (where the best distribution potential exists), ensure that the NEW_FLAG field contains the value X, and the MOD_FLAG and TRA_FLAG fields are blank.

●      To create top texts that only contain source texts that occur in new and modified lines, ensure that the NEW_FLAG and MOD_FLAG fields contain the value X, and the TRA_FLAG field is blank.

Split top text objects according to domain

If the worklist contains objects from collections belonging to different domains, we recommend that you create your top texts according to domain. If you leave the field NO_APPL blank, the system creates domain-specific top texts. For example, the system creates separate top text objects for the source texts in objects from Basis (domain BC) that match your selection criteria, and so on.

This allows translators to create application standards for the domain in question; in cases where it is not possible to create a system standard for the source text, but an application standard for domain BC is perfectly possible.

Split top text objects according to object type

If you have already decided to split the top texts according to domain, we recommend that you leave the value X entered in the NO_OBJT field; otherwise the system will create a large number of top text objects where the same source texts occur repeatedly.

However, you may want to split the top texts according to object type to see the object type in which the source texts occur. If so, leave the NO_OBJT field blank and enter an X in the NO_APPL field.

Include similar texts

If you leave the NO_NORM field blank, then the system scans for similar texts and groups them together in the top text objects (for example, Create Document, Create document, Create Document 2). This enables you to create consistent translations in the proposal pool.

The similar texts listed in the top texts do not necessarily match the other criteria you defined for top text creation. For example, the top texts could contain similar texts for which proposals already exist, even though your top text creation criteria specified otherwise.

If you enter the value X in the NO_NORM field, no scan for similar texts takes place.

Create object list

If you enter the value X in the CREA_OL field, the system creates an object list that contains top texts created in the run.

This enables you to create worklists for the top texts by evaluating this object list. To do this, you first need to create a graph for collection $TMP and then activate it for the target languages that will translate the top texts.

However, you are not obliged to create worklists for top texts. For other ways of accessing the top texts for processing, see Processing Top Texts.

Schedule top text job in the background

Ensure the BATCH field contains the value X so that the job to create the top texts runs in the background.