An exception is a translation stored in the proposal pool. Exceptions are valid within one domain.

If you need to create a translation for a very specific context, you should define your translation as an exception.

The following English translations of German source texts are examples of exceptions.

Source Text

Usual Translation (System Standard)














Exceptions are never the best proposal. Exceptions therefore enable you to create context-specific translations in the proposal pool, without invalidating any existing translations. If an exception exists for your domain, you can still use the system standard or application standard, depending on which of the two is the best proposal for your domain.

Exceptions also enable you to use the system standard as a translation in domains for which a different translation has been defined as an application standard. To do this, create the system standard translation again as an exception for your domain.

The system standard for Auftrag is Order. Request is the application standard for the Basis (BC) domain.

This means Request is the best proposal when you translate objects belonging to the domain BC. However, you need to use Order as a translation of Auftrag in a few specific contexts in Basis objects.

The solution is to create Order as an exception for the domain BC. This retains Request as the best proposal for Auftrag in BC objects, but also enables you to save Order as a translation in BC objects. This ensures that there is a match between the translation line and proposal pool for both Request and Order in BC objects. It also ensures that the existing translation Request remains valid, so the status is still translated.


You cannot see exceptions in the short text editor, because they are never the best proposal.

To see if exceptions exist for a specific source text, you need to branch to the proposal pool from the short text editor. If an exception exists for the domain of the object you are currently translating, you can use it as your translation, providing that you are sure it is more suitable in this context than the system standard or application standard (if one exists.)

To use an exception as a translation for a short text, double-click the exception in the proposal pool. The system inserts the exception into your translation line and returns to the short text editor.


When you create an exception, the system does not prompt you to assign a quality status to it. The system automatically assigns a quality status of 0 to all exceptions.

It is not possible to create an abbreviation for an exception. If you need to create an abbreviated translation as an exception, you need to create it as an additional exception for the domain in question.

You can create as many exceptions as you like for a domain. However, you are advised to minimize the number of exceptions you create. If a source text has too many proposals, it may be because the source text is too vague. In such cases, you are advised to ask the developer to change the source text so that it is less ambiguous.

See also:

Proposal Pool Maintenance

Accessing the Proposal Pool

Creating Proposals in the Proposal Pool