Proposal Pool Concepts

Basic Concepts

Proposal

Each translation that you create for a source text in the proposal pool is a proposal. For example, the German source text Vorgang and its translations constitute one entry in the proposal pool for source language German and target language English. Each English translation of the source text Vorgang is a proposal.

Type of Proposal

You can create proposals as a system standard, application standard, or exception. The system standard is valid throughout the system. The application standard is valid for one domain, and overrides the system standard in this domain. The exception is valid for a specific context within one domain. Exceptions are never the best proposal, and are never automatically distributed. For more information, see System Standard , Application Standard , and Exception .

Abbreviation

You create a translation as an abbreviation if the translation line is too short for the full text. You assign the abbreviation to its full text in the proposal pool. You can create abbreviations for a system standard or an application standard, but not for an exception. For more information, see Abbreviation .

Best Proposal

The best proposal is the most suitable translation of a specific source text with regard to the domain and the space available in the translation line. If a best proposal exists, it is displayed in blue beneath the translation line of the source text in the short text editor. You can double-click the best proposal to copy it to the translation line. For more information, see Best Proposal .

Quality Status

When you create proposals, you must assign a quality status to them (unless you create an exception.) The translator profile determines which quality statuses translators are authorized to assign. If more than one application standard or system standard exists, the system uses the quality status to determine which proposal is the best proposal. The quality status is also used as a distribution criterion when automatic distribution takes place. For more information, see Quality Status .

Automatic Distribution

During an evaluation, automatic distribution reduces the manual translation workload by inserting best proposals into short text objects that need to be translated. Automatic distribution is based on the best proposal concept, and is controlled by the parameters that you maintain in the translation environment. For more information, see Automatic Distribution and Defining Distribution Parameters .

Usage Counters

The usage counter indicates how often a specific proposal has been used as a translation in the system. For more information, see Usage Counters .

Structure of the Proposal Pool

You can access proposals in the proposal pool from the short text editor, or by using transaction SLPP. For more information, see Accessing the Proposal Pool . The way proposals are displayed in the proposal pool depends on how you accessed it.

If you branch to the proposal pool from the short text editor, the system displays the contents of the proposal pool for the source text on which you placed your cursor in the short text editor. The contents are displayed in the following tree structure:

1. Domain-specific proposals for the domain of the object you are currently translating, that is, application standards, their abbreviations, and exceptions for this domain.

2. System standard, then its abbreviations.

3. Domain-specific proposals for all other domains in which proposals already exist.

If you branch to the proposal pool from transaction SLPP, the system standard appears first, followed by the domain-specific proposals for all domains in which proposals exist. The domains are displayed in alphabetical order. In both instances, the quality status of every proposal is displayed. Exceptions are flagged with the icon.

To enable you to create domain-specific proposals (that is, application standards ), the structure of the proposal pool reflects the first application level of the component hierarchy in ABAP systems. For example, it contains the following nodes: BC (Basis), CA (Cross-Application Components), LO (Logistics - General), and PY (Payroll). However, subnodes such as BC-DWB and LO-LIS are not available. These terminology areas, which are based on the component hierarchy, are called domains .

The domain-based structure of the proposal pool enables you to create proposals that are only valid within the domains for which they were created.

For example, you can create Procurement as your Logistics translation of Beschaffung , and Recruitment as your Human Resources translation of the same source text.

The following graphic is an example of a proposal pool entry accessed from the short text editor.