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
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.
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.
Choose
, .You branch to the general translation transaction.
Only if you have used data elements for your segment fields which have not yet been translated:
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.
Enter a data element, source and target language and chooseSegment fields are documented using data elements. Therefore you must translate both the short and the long texts in the translation transaction.
Only if you have used fixed values for your segment fields which have not yet been translated:
Choose
. Enter a domain, source and target language and choose . Translate your fixed values (short texts) and save the text. Proceed in this way for all the domains in your list.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.
. Enter a segment type, source and target language and chooseSegment 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.
There is also a link to the translation transaction in Defining Segments: From there, choose .
Choose
. 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 . Translate the short description and save the text.
There is also a link to the translation transaction in the IDoc Type Editor or the IDoc Views: From there, choose .
Only if you have defined a new logical message:
Choose Edit. Translate the description and save the text.
. Enter EDIMSGT in the table and the source and target language. ChooseOnly if you have defined a new process code:
Choose
. 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.
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.