Documentation Translation

Use

For your own definitions (extensions, views or basic types) you can also enter documentation with the development tools of the IDoc Interface (Segment- and IDoc type Editor). To translate this documentation into other languages, you must use the general translation transaction.

Prerequisites

  • You have authorization for the translation transaction SE63 (authorization object S_TRANSLAT).
  • You have your own extension, view or basic type which has been tested. For more information, see

Extending an IDoc Type

IDoc Views

Defining and Using a New Basic Type

  • You have a list which groups together the newly defined segments.
  • You have a corresponding list of data elements which you use for your newly defined segment fields and which are not yet translated.
  • For these data elements you have a list of stored domains, which have fixed values still to be translated.

Procedure

  1. Choose SAP Menu ® Tools ® ABAP Workbench, Utilities ® Translation ® Short and Long Texts.

    You go to the general translation transaction.

  2. Only if you used data elements which have not yet been translated for your segment fields: Choose Translation ® Short Texts ® ABAP Dictionary ® Data Elements. Enter a data element, source and target language and choose Environment with long texts. Translate your data elements (short texts) and documentation (long texts). Save your text. Proceed in this way for all the data elements in your list.

    Segment fields are documented using data elements. Therefore you must translate both the short and the long texts in the translation transaction.

  3. Only if you used fixed values which have not yet been translated for your segment fields: Choose Translation ® Short Texts ® ABAP Dictionary ® Values. Enter a domain, source and target language and choose Edit. Translate your fixed values (short texts) and save the text. Proceed in this way for all the domains in your list.
  4. Choose Translation ® Short texts ® ABAP Dictionary ® Table texts. Enter a segment, source and target language and choose Environment with long texts. Translate the short description and the documentation (the long text) of your "table". Save your text. Proceed in this way for all the segments in your list.

    Segment types are stored in the ABAP Dictionary as structures. As every table also has a structure, tables and structures are referred to as "tables" in the translation transaction. Documented short and long texts are created for structures and tables.

    You can also access translation in the Segment Editor: Here, choose Environment ® Translation.

  5. Choose Translation ® Logical objects ® Logical objects. Enter as object:

    · IDOC , if you have defined a basic type,

    · IEXT , if you have defined an extension

    · IDCV , if you have defined a view

    Enter a source and target language and choose Edit. Translate the short description and save the text.

    You can also access translation in the IDoc Type Editor or the IDoc Views: Here, choose Environment ® Translation.

  6. Only if you have defined a new logical message: Choose Translation ® Short Texts ® Table Contents. Enter EDIMSGT in the table and source and target language. Select Edit. Translate the description and save the text.
  7. Only if you have defined a new process code: Choose Translation ® Short Texts ® Table Entries. Enter as table:

· EDE1T , if you have defined a process code for outbound processing

· EDE2T , if you have defined a process code for inbound processing

Enter a source and target language and choose Edit. Translate the description and save the text.

Result

You have translated the documentation into your new definition. If you log on to the system in the target language, the documentation tools output the translated short and long texts. Your new logical messages and process codes are described in the target language in the IDoc Interface.