Show TOC

DEMS Objects for Quality AssuranceLocate this document in the navigation structure

Use

You can create DEMS objects for quality assurance purposes by running a report that scans all or part of the proposal pool (or an object list) according to specific criteria with the aim of checking or correcting proposals. The report 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.

The following types of scan are possible:

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

    This scan finds all proposals created or last changed by a specific user and/or for a specific domain.

    You can scan according to both criteria at the same time. You can also restrict the scan to a specific date range, and to proposals with specific quality statuses. For instance you could scan for all domain standards with quality status B and S and exceptions created by user X in 2015 in the domain BC.

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

  • Find source texts with multiple proposals

    This scan finds all source texts for which a specified number of proposals is exceeded.

    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 a specified number of identical proposals is exceeded.

    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 or texts in an object list 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 the entire proposal pool or just the source and/or target texts that occur 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 instances where the source and target texts 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.

      Deleting such incorrect proposals helps you improve the quality of translation.

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

Prerequisites

  • If you intend to scan the proposal pool, run report RS_LXE_PP_CLEAN_UP_DUPLICATES to delete superfluous domain standards before you perform the scan. For more information, see Deleting Superfluous Domain Standards.

  • If you intend to scan an object list, then you must create an object list in transaction LXE_MASTER.

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

  • To reduce the number of modified lines caused by changing proposals, ensure that the 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 created by the scan job. The translators 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. You run one of the above reports to create DEMS objects that contain the source texts whose proposals require correction.

  2. You trigger processing of the resulting DEMS objects.

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

  4. After the translators have finished processing the DEMS objects, you run an evaluation with automatic distribution.

    Automatic distribution helps to reduce the number of modified lines caused by changing and deleting incorrect proposals.

Example

You run a report to create DEMS objects that contain all instances in the proposal pool where the German source text Vertrag has been translated with the English text 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.

If you now run an evaluation without automatic distribution, the translation status of all lines containing the German source text Vertrag anlegen and the English translation Create Contract changes to modified, because the old translation Create Contract in the translation lines no longer matches a proposal in the proposal pool. For more information, see Translation Status.

However, if you maintain the automatic distribution parameters in transaction LXE_MASTER and then run an evaluation with automatic 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 time and money because translators do not need to manually update the translations in modified lines after cleaning up the proposal pool.