Scanning for a Specific Source/Target Text String 
You can perform a scan to find the following:
A specific source text string
For example, you want to check all instances of a specific source text string to verify that it has been translated correctly and consistently.
A specific target text string
For example, you want to find all instances where a specific translation has been used, regardless of what the source text is.
A specific source text and target text string
For example, you only want to find instances where a specific source text string has been translated in a particular way.
You can perform this scan in two different ways:
Scan the objects in a specific object list for a specific source and/or target text string.
Scan the entire proposal pool (or a domain in the proposal pool) for a specific language combination for a specific source and/or target text string.
See the Prerequisites section in DEMS Objects for Quality Assurance.
Call transaction LXE_MASTER.
To scan for text strings in the objects in a specific object list, choose .
To scan for text strings in the entire proposal pool, choose .
Enter your selection criteria for the scan as follows:
Name of DEMS objects |
In the Object Name field, enter a text string that will help you recognize the DEMS objects when you call them in transaction SE63. |
Description |
You can enter a description of up to 40 characters in the Description field to document how you created the DEMS objects, for example. |
Source language |
In the Source Language field, enter the required source language for the text scan. |
Target language |
In the Target Languagefield, enter the target language for the text scan. |
Object list (Only available if you perform the Object List scan) |
Choose F4 on the Object List field, and select the object list that contains the objects for which you want to perform the text scan. |
Source text |
In the Source Text field, enter the source text string that you want to find. To search generically, ensure that you enter a * at the start and end of the string. If you do not want to scan according to source text, ensure that this field contains the default value *. |
Target text |
In the Target Text field, enter the target text string that you want to find. To search generically, ensure that you enter a * at the start and end of the string. If you do not want to scan according to target text, ensure that this field contains the default value *. |
Case-sensitive source text scan |
We recommend that you leave the Ignore Upper-/Lowercase (Srce) field blank in order to perform a case-sensitive scan, which is less performance-intensive. You can still search in a case-sensitive manner, by leaving this field blank and entering the source text minus its first letter in the S_LANG field. For example *uftrag* would enable you to find all source texts that contain either the string Auftrag or the string auftrag. Similarly, *rder* would enable you to find all source texts that contained either the string Order or the string order. |
Case-sensitive target text scan |
We recommend that you leave the Ignore Upper-/Lowercase (Trgt)field blank in order to perform a case-sensitive scan, which is less performance-intensive. You can still search in a case-sensitive manner, by leaving this field blank and entering the target text minus its first letter in the T_LANG field. For example *uftrag* would enable you to find all target texts that have a proposal containing either the string Auftrag or the string auftrag. Similarly, *rder* would enable you to find all target texts that have a proposal containing either the string Order or the string order. |
Maximum number of source texts |
In the Number of Texts field, you can specify a limit to how many source texts are contained in the DEMS objects produced by the scan. If you want the scan to find all source texts with proposals that match your selection criteria, enter a suitably high number here. |
Generate object list |
If you enter the value X in the Generate Object List field, the system creates an object list when you scan an object list or the proposal pool. However, the results are different:
|
Generate local list (Only available if you perform the Object List scan) |
If you enter the value X in the Generate Local List field, the system creates a local list that contains the translation objects in which the search strings were found. For more information on accessing the local list, see the Local List documentation. |
Domain to be scanned (Only available if you perform the Proposal Pool scan) |
If you scan the proposal pool, you can restrict the scan to search only in the application standards and/or exceptions created in a specific domain. To do this, make sure the field Domain Type contains the value *, choose F4 on the Domain field, and double-click the domain in which you want to scan. To search in all domains of the proposal pool, make sure the fields Domain Type and Domain both contain the value *. |
Types of proposals (Only available if you perform the Proposal Pool scan) |
You can exclude exceptions from your scan, or scan exceptions only.
|
Schedule the job to run in the background.
Irrespective of whether you scanned an object list or the proposal pool, the system creates DEMS objects that can be processed in transaction SE63. If you selected the Generate Object List field, the system generates an object list containing:
Translation objects (if you scanned an object list)
DEMS objects (if you scanned the proposal pool)
If you scanned an object list and selected the Generate Local List field, the system generates a local list containing translation objects.
You have found out that since the start of the translation project, the German text Vertrag has been incorrectly translated into English as contract. In the context of your development, the correct English translation is policy. You want to clean up the entire proposal pool so that this problem is solved once and for all. The first step is to find all German source texts containing the string Vertrag or vertrag that have a proposal containing the string Contract or contract.
Call transaction LXE_MASTER.
Choose .
Enter your selection criteria for the scan as follows:
Field |
Input |
Object Name |
CONTRACT_EN |
Description |
DE *ertrag* EN *ontract* |
Source Language |
deDE |
Target Language |
enUS |
Source Text |
*ertr* Why only *ertr* as the search string and not *ertrag*? Don't forget that the plural of Vertrag is Verträge! A suitable example in English would be criterion and criteria. |
Target Text |
*ontract* |
Ignore Upper-/Lowercase (Srce) |
Leave blank |
Ignore Upper-Lowercase (Trgt) |
Leave blank |
Number of Texts |
Enter a suitably high value to ensure that all instances are included in the DEMS objects |
Domain Type |
* |
Domain |
* |
Normal Proposals |
X |
Exceptions |
X |
Generate Object List |
X |
Schedule the job to run in the background.