Show TOC

Proposal Pool Analysis Tool (PPAT)Locate this document in the navigation structure

Definition

The Proposal Pool Analysis Tool (transaction PPAT) enables you to analyze the contents of the proposal pool according to a variety of criteria for one or more combinations of source and target language. It is important to note that PPAT only provides you with numerical data about the proposal pool. It does not provide any information about the accuracy of the translations entered in the proposal pool, or whether proposals have been defined correctly as system standards, domain standards, abbreviations or exceptions, or whether translators assigned the correct quality statuses to proposals when they created them.

Prerequisites

Translators have created proposals in the proposal pool while translating short text objects in the short text editor.

Your translator profile in transaction LXE_MASTER includes authorization object PPAT Display Delete and Generate Proposal Pool Data. The value of authorization object PPAT determines what exactly you are authorized to do within the transaction.

Features

PPAT data can be generated for any combination of source and target language for which translators have created proposals in the proposal pool. It enables you to answer questions such as:

  • How many proposals exist in total?

  • How many of these proposals are system standards?

  • How many exceptions are there?

  • How many proposals have been deleted?

  • How many domain standards exist in each domain?

  • How many abbreviations have been created for system standards and domain standards?

  • How many proposals have quality status A, S, B, or X?

  • How many best proposals with quality status A were created during top text processing?

  • If the German to English proposal pool contains 618,095 proposals in total, and 35,387 of these proposals have quality status A, what percentage of the total has quality status A?

There are three different PPAT types:

  • PPAT runs of type AP contain data that was generated by analyzing All Proposals.

  • PPAT runs of type WL contain data that was generated on the basis of a WorkList. PPAT data of type WL can be generated:

    • For the best proposals that exist for source texts in the worklist.

    • For the proposals that give translated status to texts in the worklist.

  • PPAT runs of type OL contain data that was generated on the basis of an Object List. PPAT data of type OL can be generated:

    • For the best proposals that exist for source texts in the object list.

    • For the proposals that give translated status to texts in the object list.

    • With or without data on object types that are not defined for translation into a particular target language.

More Information