Scanning for a Specific User/Domain 
You can run a scan to create DEMS objects that contain source texts with proposals created by a specific user, or proposals created in a specific domain.
You can scan according to both criteria at the same time. You can also restrict it to a specific date range or a specific quality status of proposals. Here are just a few examples of how you can use this scan:
Scan for all application standards and exceptions created by user X in 2006 in the domain BC.
Scan for all status B proposals created in the last month.
Scan for all status A proposals created by user Y.
If you delete any proposals while processing the resulting DEMS objects, this can cause modified lines. Read the Process Flow and Example sections carefully in DEMS Objects for Quality Assurance before you begin.
See the Prerequisites section in DEMS Objects for Quality Assurance.
Call transaction LXE_MASTER.
Choose
Define the criteria for your scan as follows:
Source language |
In the Source Language field, enter the required source language for the scan. |
Target language |
In the Target Language field, enter the target language for the scan. |
Name of DEMS objects |
Enter a text string in the Object Name field that will help you recognize the DEMS objects when you call them in transaction SE63. |
Description of DEMS objects |
You can enter a description of up to 40 characters in the Description field to document how you created the DEMS objects, for example. |
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. |
Domain to be scanned |
You can restrict the scan to search only in the application standards / exceptions created in a specific domain. To do this, make sure the field Domain Type contains the value *, and enter the 2-character ID of the domain in the Domain field (for example, BC for Basis). To search in all domains of the proposal pool, make sure the fields Domain Type and Domain both contain the value *. |
Status of proposals |
If you want your scan to include source texts with proposals of all quality statuses, leave the default values in the fields Minimum Status and Maximum Status unchanged. To restrict the scan to source texts with proposals of a specific quality status range, use the Minimum Status and Maximum Status fields to specify your lower and upper limits. For example, if you only want to include source texts with proposals of quality status B (to check the work of beginner translators, for example), choose F4 on the Minimum Status field and select status B, then choose F4 on the Maximum Status field and select status B again. The system enters the lower and upper numeric values of quality status B respectively. |
Usage counters |
We recommend that you leave the default entries unchanged in the fields Usage Counter (From)and Usage Counter (To) |
User name |
If you want the DEMS objects to contain source texts with proposals created / changed by a specific user, you have the following options:
|
Date range |
If you want the DEMS objects to contain source texts with proposals created/changed within a specific date range, you have the following options:
|
Types of proposals |
You can exclude exceptions from your scan, or scan exceptions only.
|
Generate object list |
If you enter the value X in the Generate Object List field, the system creates an object list that contains DEMS objects created in the run. This enables you to create worklists 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 languages that will translate the DEMS objects. However, you are not obliged to create worklists for DEMS objects. For other ways of accessing the DEMS objects for processing, see Processing DEMS Objects for Quality Assurance. |
Schedule the job to run in the background.
The system scans the proposal pool and creates DEMS objects in accordance with your selection criteria. The DEMS objects contain source texts in the requested source language for which the scan job found proposals that match your selection criteria.
You can now trigger processing of these DEMS objects. For more information, see Processing DEMS Objects for Quality Assurance.
You want to find any source texts for which a proposal that satisfies all of the following criteria exists in the proposal pool for source language German and target language English:
Created or changed in December 2006
Created or changed by user CRM_EN_02
Has status B or S
Is either an application standard or exception for the domain Materials Management (MM)
You do not want to evaluate the DEMS objects to create worklists, so do not need to create an object list of the DEMS objects created by the scan.
To run the scan, proceed as follows:
Call transaction LXE_MASTER.
Choose .
Enter your selection criteria for the scan as follows:
Field |
Input |
Source Language |
deDE |
Target Language |
enUS |
Object Name |
CRM_EN_DEC |
Description |
User CRM_EN_02, status B+S, Dec 2006 |
Number of Texts |
Enter a suitably high value to ensure that all instances are included in the DEMS objects |
Domain Type |
* |
Domain |
MM |
Minimum Status |
40 (numeric lower limit for quality status B) |
Maximum Status |
89 (numeric upper limit for quality status S) |
Usage Counter (From) |
Leave the default value unchanged |
Usage Counter (To) |
Leave the default value unchanged |
Created By |
Leave blank |
Creation Date (From) |
Leave the default value unchanged |
Creation Date (To) |
Leave the default value unchanged |
Last Changed By |
CRM_EN_02 |
Change Date (From) |
01.12.2006 |
Change Date (To) |
31.12.2006 |
Normal Proposals |
X |
Exceptions |
X |
Generate Object Lists |
Leave blank |
Start in Background |
X |
Schedule the job to run in the background.