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.
1. Call up transaction LXE_MASTER.
2. Choose Environment → DEMS Objects.
3. Choose the User / Domain pushbutton next to Selection via Proposal Pool.
4. Define the criteria for your scan as follows:
Source language |
In the S_LANG field, enter the required source language for the scan. |
Target language |
In the T_LANG field, enter the target language for the scan. |
Name of DEMS objects |
Enter a text string in the NAME field that will help you recognize the DEMS objects when you call them up in transaction SE63. |
Description of DEMS objects |
You can enter a description of up to 40 characters in the DESCRIPT field to document how you created the DEMS objects, for example. |
Maximum number of source texts |
In the NUMBER 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 DOMATYP contains the value *, and enter the 2-character ID of the domain in the DOMANAM field (e.g. BC for Basis). To search in all domains of the proposal pool, make sure the fields DOMATYP and DOMANAM 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 MIN_STAT and MAX_STAT unchanged. To restrict the scan to source texts with proposals of a specific quality status range, use the MIN_STAT and MAX_STAT fields to specify your lower and upper limits. For example, if you want to include only source texts with proposals of quality status B (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. |
Usage counters |
We recommend that you leave the default entries unchanged in the fields MIN_USAG and MAX_USAG. |
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: · To find proposals created by a specific user, enter his / her user name in the F_NAME field and leave the L_NAME field blank. · To find proposals created by a specific user, as well as proposals last changed by this user (these proposals may have a different creator), leave the F_NAME field blank and enter his / her user name in the L_NAME field. |
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: · To find proposals created within a specific date range, enter the start date in the MIN_F_DA field and the end date in the MAX_F_DA field and leave the default values unchanged in the MIN_L_DA and MAX_L_DA fields. · To find proposals created within a specific date range, as well as proposals last changed within a specific date range (these proposals may have been created outside the date range), leave the default values unchanged in the MIN_F_DA and MAX_F_DA fields and enter the start date in the MIN_L_DA field and the end date in the MAX_L_DA field. |
Types of proposals |
You can exclude
· To exclude exceptions from the scan, make sure the NORMAL field contains the value X and the EXCEPT field is blank. · To scan exceptions only, make sure the NORMAL field is blank and the EXCEPT field contains the value X. |
Create object list |
If you enter the value X in the CREA_OL field, the system creates an object list that contains DEMS objects created in the run. This enables you to create
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 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. |
5. Choose Execute (F8) and 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:
…
1. Call up transaction LXE_MASTER.
2. Choose Environment → DEMS Objects.
3. Choose the User / Domain pushbutton next to Selection via Proposal Pool.
4. Enter your selection criteria for the scan as follows:
Field |
Input |
S_LANG |
deDE |
T_LANG |
enUS |
NAME |
CRM_EN_DEC |
DESCRIPT |
User CRM_EN_02, status B+S, Dec 2006 |
NUMBER |
Enter a suitably high value to ensure that all instances are included in the DEMS objects |
DOMATYP |
* |
DOMANAM |
MM |
MIN_STAT |
40 (numeric lower limit for quality status B) |
MAX_STAT |
89 (numeric upper limit for quality status S) |
MIN_USAG |
Leave the default value unchanged |
MAX_USAG |
Leave the default value unchanged |
F_NAME |
Leave blank |
MIN_F_DA |
Leave the default value unchanged |
MAX_F_DA |
Leave the default value unchanged |
L_NAME |
CRM_EN_02 |
MIN_L_DA |
01.12.2006 |
MAX_L_DA |
31.12.2006 |
NORMAL |
X |
EXCEPT |
X |
CREA_OL |
Leave blank |
BATCH |
X |
5. Choose Execute (F8) and schedule the job to run in the background.