Warning!
This functionality is not yet available in Basis Release 610.
We hope to deliver this functionality in one of the subsequent support packages for Basis Release 610. Please refer to note 0400197 in the SAP Online Service System. We will update this note as soon as the functionality is available again.
Use
This ensures that you continue to use the same translation memory in the new translation system, thus keeping your translations consistent.
It may be useful to import a proposal pool from a file to a local system for updating purposes, for instance, if you want to update a local system to the status of a more up-to-date system. You may need to import the proposal pool of another system, when a certain application area (which up till now was translated in a different system) moves into the local system.
Prerequisites
You need to make a number of settings to influence the way in which the proposal pool is imported from the file to the local system. The settings are as follows:
Import Locks
If you see the message Translation is active at present -> locks are required you need to set the parameter in the field next to this message. This parameter defines the locking logic during the import of the proposal pool.
Yes |
This means that import locks are set during the import, which prevents entries in the proposal pool from being altered if a translator is currently editing them (this applies to both the source and target language). |
No |
This means that no import locks are set during the import. Here you need to ensure that no translator is working in the proposal pool in either the source or target language involved in the import. |
Setting import locks increases performance and can lead to import termination. If you can ensure that nobody is working in the proposal pool, then you can improve performance considerably by choosing No.
Import Mode
Priority of proposal pool entries
This parameter decides which proposal pool has priority over the other.
Local entries have priority |
This means that the local proposal pool has priority in conflict cases. If you choose this option you need to make additional settings under Import conflicts. The local system standards and application standards are then handled according to the settings you make. |
Import entries have priority |
This means that the imported proposal pool has priority and overwrites the entries in the local proposal pool in cases of conflict. Exceptions in the local proposal pool are, however, retained. If you choose this option you need to make additional settings under Import conflicts. The local system standards and application standards are then handled according to the settings you make. |
Adjust PP based on usage counters |
If you choose this option, the system uses the where-used list as the basis for deciding which proposal 'wins' in cases of conflict. The proposal that has the highest usage counter will become the proposal in the target system. The where-used list data must be available in the system from which you have exported and the system to which you are importing a proposal pool. This means you need to select the option Write where-used list data when you run the evaluation in transaction SLWB in both systems. |
Local entries are replaced |
If you choose this option, entries in the local proposal pool are replaced by entries from the imported proposal pool. |
Local entries remain unchanged |
If you choose this option, entries in the local proposal pool are not replaced by entries from the imported proposal pool, and remain unchanged. |
Test mode (no insertions or changes)
If you choose this option, the import is performed in test mode and the local proposal pool is not altered. The system outputs a log to show what would have happened if an import had taken place with these settings.
Import of Application-Specific Entries
Application standards
This parameter influences the way in which the application standards are imported from the file to the local system.
Insert |
This means that the application standards from the imported proposal pool are inserted as application standards in the local proposal pool. |
Do not insert |
This means that the application standards from the imported proposal pool are not inserted and the local application standards are retained. |
Only insert as exception |
This means that the application standards from the imported proposal pool are inserted as exceptions in the local proposal pool. |
Exceptions
This parameter influences the way in which the application standards are imported from the file to the local system.
Insert |
This means that the exceptions from the imported proposal pool are inserted in the local proposal pool. |
Do not insert |
This means that the exceptions from the imported proposal pool are not inserted. |
In both cases, the exceptions in the local proposal pool are retained.
Import Conflicts
If you choose either Local entries have priority or Import entries have priority in the Priority of proposal pool entries under Import mode, then you need to set additional parameters under Import conflicts.
Different system standards
This parameter influences what happens when a system standard in the local proposal pool and its corresponding system standard in the imported proposal pool are not identical.
Do not insert in case of conflict |
This means that the system standard from the imported proposal pool is not inserted in cases where it is not identical to the system standard in the local proposal pool. |
Insert as application standard |
This means that the system standard from the imported proposal pool is inserted as an application standard in cases where it is not identical to the system standard in the local proposal pool. |
Insert as exception |
This means that the system standard from the imported proposal pool is inserted as an exception in cases where it is not identical to the system standard in the local proposal pool. |
If the local proposal pool has Exit as its system standard, and the imported proposal pool has Terminate as its system standard. The following would apply for the above settings:
Different application standards
This parameter influences what happens when an application standard in the local proposal pool and its corresponding application standard in the imported proposal pool are not identical.
Do not insert in case of conflict |
This means that an application standard from the imported proposal pool is not inserted in cases where it is not identical to the application standard in the local proposal pool, and the local application standard is retained. |
Insert as exception |
This means that in cases where an application standard from the imported proposal pool is not identical to the application standard in the local proposal pool, it is inserted as an exception for the application from which it originates (e.g. FI). |
Longer local node text
This parameter influences what happens when a node text in the local proposal pool is longer than the node text in the imported proposal pool, and the system recognizes them as having the same meaning.
Do not insert in case of conflict |
This means that the longer node text is not inserted in the proposal pool. |
Insert as length variant |
This means that the longer node text is inserted as a length variant. |
Insert as new node text |
This means that the longer node text is inserted as the new node text, and the shorter node text is defined as its length variant. |
Procedure
If the system displays the message Proposal pool can be imported from file, you can schedule the import run.
The system displays the dialog box Start Time, which offers you further selection options.
You can also schedule the run to start after a particular job or an event, by choosing After job or After event.
At operation mode refers to daytime or nighttime operation.
The system displays a dialog box in which you can enter a printer name.
The system displays a dialog box in which you can enter a background server on which you want the import to run.
The system asks you if you want to schedule the job. Choose Yes.
Result
The contents of the proposal pool are exported. You can view the status of the import run by choosing Run administration.
After you have executed the import, you can also view a log of the results of the import run. For more information, see
Export/Import Log.