Scanning for a Specific Source/Target Text String

Prerequisites

See the Prerequisites section in DEMS Objects for Quality Assurance.

Context

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.

Procedure

Call transaction LXE_MASTER.
To scan for text strings in the objects in a specific object list, choose DEMS Objects Text Search According to Object List .

To scan for text strings in the entire proposal pool, choose DEMS Objects Text Search In Proposal Pool .

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 Language field, 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 .
Check existence of target text (Only available if you perform the Object List scan)	If you make an entry in the Source Text field, enter `` in the Target Text field and do not select the Check Target Text Exists (if Target Text = ) checkbox, the report finds every instance of the source text in the object list irrespective of whether a target text exists or not. If you select the check box, the report only finds instances of the source text in the object list for which a target text exists.
Case-sensitive source text scan	We recommend that you leave the Not Case-Sensitive (Source) 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 Source Text 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 Not Case-Sensitive (Target) 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 Target Text 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 texts that match your selection criteria, enter a suitably high number here.
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 domain standards and/or exceptions created in a specific domain. To do this, 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 Domain field contains 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. To exclude exceptions from the scan, make sure the Normal Proposals field contains the value X and the Exceptions field is blank. To scan exceptions only, make sure the Normal Proposals field is blank and the Exceptions field contains the value X.
Generate object list	If you enter the value `X` in the Create Object List field, the system creates an object list when you scan an object list or the proposal pool. However, the results are different: If you scan an object list, the system generates an object list containing the translation objects in which the texts were found. You can then use the generated object list to generate a worklist, or you can use it to call up an on-the-fly worklist in SE63. If you scan the proposal pool, the system generates an object list containing the DEMS objects. You can then use the generated object list to generate a worklist for the DEMS objects by evaluating this object list. To do this, you first need to create a graph for collection SAP_TRANSLATION_DEMS and then activate it for the target language that will process the DEMS objects.
Generate local list (Only available if you perform the Object List scan)	If you enter the value `X` in the Create Local List field, the system creates a local list that contains the translation objects in which the search strings were found. For more information, see the Local Lists documentation.

Schedule the job to run in the background.

Results

Irrespective of whether you scanned an object list or the proposal pool, the report creates DEMS objects that can be processed in transaction SE63.

If you scanned an object list, OL_SRC is included in the technical name of each DEMS object.

If you scanned the proposal pool, PP_SRC is included in the technical name of each DEMS object.

If you selected the Create Object List field, the report 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 Create Local List field, the report generates a local list containing translation objects. The objects in the local list can only be called up in an on-the-fly worklist for the specified target language, not for any other target languages in the system. To display the local list in transaction LXE_MASTER, choose Start of the navigation path Edit Next navigation step Local Lists Select Lists Edit Selection End of the navigation path ; it is displayed under the header SRCH Search List (Language-Specific).

Example

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 DEMS Objects Text Search In Proposal Pool .

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 the search string riteri which finds both criterion and criteria.
Target Text	ontract
Not Case-Sensitive (Source)	Leave blank
Not Case-Sensitive (Target)	Leave blank
Number of Texts	Enter a suitably high value to ensure that all instances are included in the DEMS objects
Domain	*
Normal Proposals	X
Exceptions	X
Create Object List	X

Schedule the job to run in the background.