Creating Fingerprints for Translated Long Texts 
As of the following NetWeaver release levels, the translation status of long text objects created in transaction SE61 is determined by fingerprints:
7.30 (as of Support Package 8)
7.31 (as of Support Package 3)
7.32
When such long texts are evaluated to create worklists and statistics, their translation status is determined by fingerprints instead of the SE61 version number, which is how their translation status was determined in the past.
There are two main reasons why fingerprints have replaced the SE61 version number to determine the translation status of long text objects:
If you change the original language version of a long text object, its SE61 version number changes even if you have not changed the text. When the SE61 versioning logic is used to determine the status of long texts in the translation workflow, this can cause modified long text objects to appear unnecessarily in the worklist and statistics.
This is not the case with fingerprints, which ensure that long text objects only have modified status if the source text has changed and you need to update the translation.
The SE61 versioning logic is based solely on the version number of the original language text. This can cause problems if a long text object created in original language German, for example, is translated into English and then translated from English into another language, such as Japanese.
Fingerprints, on the other hand, are generated for a combination of source and target text and are not reliant on the status of the original language text.
You need to generate fingerprints if you have translated long text objects:
In another system where their status was determined by the SE61 version number, after which you transported the translations to this system where fingerprints are used instead
In this system before it was upgraded to one of the release and Support Package levels listed above
If you do not generate fingerprints, long text objects that used to have translated status (on the basis of the SE61 version number) will change to modified simply because the fingerprints are missing.
Prerequisites
Before you create fingerprints for long texts, ensure that the following criteria have been satisfied:
Your system is on one of the release and Support Package levels listed above
You have created a worklist that contains all translation-relevant long text objects
Procedure
Call transaction SE38.
Enter RS_LXE_CREATE_FIPR_FOR_SE61 in the Program field and choose
(Execute (F8)).In the Worklist ID field, enter the number of the worklist for which you want to create fingerprints.
In the Language field, specify the languages for which fingerprints are created.
Result
This creates fingerprints for long text objects in the specified worklist that used to have translated status in accordance with the old SE61 versioning logic.
After the report has finished, you can see how many fingerprints were created for each target language in the spool in transaction SM37. You can now: