Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_CMS_CORR_TRN_FM | Define Translation of Application Forms |
Transaction Code | S_PLN_62000534 | (empty) |
Created on | 20040429 | |
Customizing Attributes | SIMG_CMS_CORR_TRN_FM | Define Translation of Application Forms |
Customizing Activity | SIMG_CMS_CORR_TRN_FM | Define Translation of Application Forms |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CMS_CORR_TRN_FM |
Use
In this activity, you can trigger the translation of the application forms that you use.
Requirements
The application forms to be translated must be defined in an original language. If you have completed the maintenance of the application forms, the translation can be carried out.
Standard settings
SAP does not provide any default settings.
Activities
The following activities are required for the translation of application forms:
- Creation of Worklist
By entering the original and target language, you can create a list of objects relevant for translation. By saving this list, you convert it into a worklist. Worklists can be generated by an administrator or a translator.
- Individual Processing of Worklists
If a worklist has been generated, it can be processed by a translator.
- Mass Processing of Worklists
Using this function, you can manage the worklists that exist in the system. This means that you can update the status of views, or delete worklists.
- Language Settings for the Print Workbench (optional)
Here, you can define which languages can be used in which function (for example, primary maintenance language for forms). These settings are optional, but ensure a uniform procedure for maintenance and translation.
- Comparison of Languages for Application Forms
You can use this report to ensure that the languages implicitly defined in the application forms agree with the settings in the administration.
- Status of SAPScript Forms Not Used in the Print Workbench
(List of SAPScript forms not used in the print workbench).
If you use SAPScript forms that are not used in the print workbench, you can use this report to create a list of these forms, including the translation status.
Example
Your application forms are created and maintained in a specific language but you also want to create correspondence in other languages.
Recommendation
For more information about the translation transaction, read the application documentation on the translation of application forms. The forms can also be translated using the application form maintenance transaction (EFRM), but for handling reasons, SAP recommends using the tool described here.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_CMS_CORR_TRN_FM | 0 | ALN0000071 | Collateral Management System |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
EFTRADM | T - Individual transaction object | EFTRADM |
History
Last changed by/on | SAP | 20040429 |
SAP Release Created in | 500 |