Show TOC

DEMS Objects for Quality AssuranceLocate this document in the navigation structure

Use

It is possible to create DEMS objects for quality assurance purposes. This means that you can schedule a job to scan all or part of the proposal pool according to specific criteria with the aim of checking or correcting proposals. The scan job creates DEMS objects containing the source texts that have proposals matching your selection criteria. You can then call up the DEMS objects in transaction SE63 to check or correct the proposals in question.

The following types of proposal pool scans are possible:

  • Find proposals created by a specific user/for a specific domain

    This scan finds all source texts that have proposals created by a specific user or all 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. For instance you could scan for all application standards and exceptions created by user X in 2006 in the domain BC.

    For more information, see Scanning for a Specific User/Domain

  • Find source texts with multiple proposals/exceptions

    This scan finds all source texts for which more than a specific number of proposals/exceptions exist.

    For more information, see Scanning for Multiple Proposals for the Same Source Text

  • Find source texts with duplicate proposals

    This scan finds all source texts for which more than a specific number of identical proposals exist.

    For more information, see Scanning for Duplicate Proposals for the Same Source Text .

  • Find a specific source text string and/or target text string

    This scan finds all entries in the proposal pool that contain a specific source text string and/or target text string. For example, you want to find all instances where the German string Vertrag is translated into English as Contract. You can scan either the entire proposal pool or only the source texts that are available in the objects in a specific object list.

    For more information, see Scanning for a Specific Source/Target Text String .

  • Find proposals that are identical to the source text

    This scan finds cases where the source and target text are identical. Finding such cases can have two uses:

    • The proposal is an excellent candidate for automatic distribution and should be assigned quality status A.

      Examples of such texts would be technical names that are not language-dependent, such as $USR$, 100%, company names, and so on.

    • The proposal is a result of the source text being copied by mistake.

      Pinpointing such cases would help you improve the quality of the translation.

    For more information, see Scanning for Cases of Identical Source and Target Texts .

Prerequisites
  • Authorization object S_ADMI_FCD with value TR N R must be assigned to your user.

  • Think carefully about the timing of a proposal pool cleanup. Changing translations in the proposal pool can cause modified lines. Do you have enough time to deal with them before the translation deadline?

  • To cut down on the number of modified lines caused by changing proposals, ensure that your distribution parameters are defined so that distribution takes place in modified lines for the target language in question. For more information, see Defining Distribution Parameters .

  • Make sure you have the necessary translation resources for processing the DEMS objects that result from the scan job. The translators also require a translator profile that allows them to assign quality status A to the new proposals that they create, to ensure that automatic distribution takes care of as many of the resulting modified lines as possible.

Process
  1. Run the necessary scan job to create DEMS objects that contain the source texts whose proposals require correction.

  2. Trigger processing of the resulting DEMS objects and tell the translators which objects need processing.

  3. Translators process the DEMS objects. For more information, see Processing DEMS Objects for Quality Assurance .

  4. As soon as the translators have finished processing the DEMS objects, run an evaluation with automatic distribution .

    This will help to reduce the number of modified lines caused by changing and deleting incorrect proposals. For more information, see the Example below.

Example

You run a scan to create DEMS objects that contain all instances where the German source text string Vertrag has been translated with the English string Contract.

The first line of the first DEMS object contains the source text Vertrag anlegen . One proposal exists in the proposal pool, and that is a system standard Create Contract . You delete this proposal and replace it with the system standard Create Policy. You assign quality status A to the new system standard.

As soon as a new evaluation runs, all lines containing the German source text Vertrag anlegen and the English translation Create Contract have status modified , because the match between translation and valid proposal no longer exists. For more information, see Translation Status .

However, if you ensure in transaction LXE_MASTER that status A proposals are distributed for all object types in modified lines for target language English, and run an evaluation with distribution, the system automatically replaces the incorrect translation Create Contract with the new, status A system standard Create Policy during the evaluation run. This saves translators from manually adapting the translations in modified lines after cleaning up the proposal pool.